unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: 18967@debbugs.gnu.org
Subject: bug#18967: Tramp disables important SSH security features
Date: Thu, 06 Nov 2014 07:05:40 -0500	[thread overview]
Message-ID: <874muczg8b.fsf@lifelogs.com> (raw)
In-Reply-To: <545AC52C.1090807@dancol.org> (Daniel Colascione's message of "Thu, 06 Nov 2014 00:47:40 +0000")

On Thu, 06 Nov 2014 00:47:40 +0000 Daniel Colascione <dancol@dancol.org> wrote: 

DC> Tramp disables SSH host key checks by setting
DC> GlobalKnownHostsFile=/dev/null, UserKnownHostsFile=/dev/null, and
DC> StrictHostKeyChecking=no in its default method configuration. These
DC> settings allow attackers to intercept connections to remote hosts, sniff
DC> passwords, and cause other mischief. I don't think we should ship an
DC> insecure configuration.

I think the alternatives are something like what Ansible does:
http://www.ansible.com/blog/2014/01/15/ssh-connection-upgrades-coming-in-ansible-1-5
or a SSH client library as a FFI. SSH, when called externally, has many
failure modes without those options.

Ted





  reply	other threads:[~2014-11-06 12:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06  0:47 bug#18967: Tramp disables important SSH security features Daniel Colascione
2014-11-06 12:05 ` Ted Zlatanov [this message]
2014-11-06 16:58   ` Daniel Colascione
2014-11-06 20:59     ` Ted Zlatanov
2014-11-06 23:39     ` Stefan Monnier
2014-11-07  7:56       ` Michael Albinus
2016-12-13  1:12         ` Glenn Morris
2016-12-13  8:36           ` Michael Albinus
2016-12-13 20:04             ` Glenn Morris
2016-12-18  8:51               ` Michael Albinus
2016-12-19 17:02                 ` Glenn Morris
2016-12-19 18:37                   ` Michael Albinus
2016-12-21 11:44                     ` Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874muczg8b.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=18967@debbugs.gnu.org \
    --cc=dancol@dancol.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).