all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 30946@debbugs.gnu.org
Subject: bug#30946: 26.0.90; TRAMP cannot access some files when using hops
Date: Tue, 1 Jan 2019 01:40:54 +1300	[thread overview]
Message-ID: <e6ae8f59-24aa-613f-ed38-1f5c310275b1@orcon.net.nz> (raw)
In-Reply-To: <877efqdjtn.fsf@gmx.de>

> Ad-hoc proxy definitions are removed by
> "M-x tramp-cleanup-all-connections".
> I've added a respective hint to the manual.

Right; but given that there is now some form of error detection in the
case when a clearly-incorrect hostname is given for the sudo/su methods,
would it not be very sensible to also ensure that a proxy matching the
incorrect hostname is not added?

As it is, the error is 'caught' but the unwanted behaviour silently
happens anyway, which seems bad to me; especially when any subsequent
use of that proxy is likely to be pretty confounding.  In the worst
case someone can end up unwittingly connecting to a different machine
than the one they intended, at which point they could inadvertently
cause themselves real problems.

Sure, it's ultimately their mistake; but when that mistake was actually
detected at the outset, it seems a shame not to deal with it then.


-Phil






  reply	other threads:[~2018-12-31 12:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26  8:42 bug#30946: 26.0.90; TRAMP cannot access some files when using hops Nicolas Petton
2018-03-29 14:11 ` Michael Albinus
2018-04-03 12:02   ` Nicolas Petton
     [not found] ` <6e181a50-452c-0e8b-ae5a-0746f64a6dfb@orcon.net.nz>
2018-12-30 22:01   ` Phil Sainty
2018-12-31 11:20     ` Michael Albinus
2018-12-31 12:40       ` Phil Sainty [this message]
2018-12-31 14:13         ` Michael Albinus
2018-12-31 21:48           ` Phil Sainty
2019-01-01 11:54             ` 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

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

  git send-email \
    --in-reply-to=e6ae8f59-24aa-613f-ed38-1f5c310275b1@orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=30946@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.