unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org, Manuel Giraud <manuel@ledu-giraud.fr>
Subject: Re: Dired command on same host
Date: Wed, 05 Jan 2022 20:55:56 +0100	[thread overview]
Message-ID: <87pmp6c5lt.fsf@gnu.org> (raw)
In-Reply-To: <87zgoa5uth.fsf@gmx.de>

Michael Albinus <michael.albinus@gmx.de> writes:

>> To adress Tassilo remark, maybe it should make a hash of «some known»
>> file too to ensure that this is the correct host B. Or maybe this is
>> too much.
>
> Well, a better check would be whether a given host name resolves to
> the same IP address, taking into account also ssh's config via the
> "Host" option. Don't know how hard this is.
>
> And even this isn't bullet-proof. Due to network configuration, hostB
> could resolve to different addresses on my local machine and on hostA,
> although it is still the same machine.

That's exactly a common usage pattern for me.  I frequently connect to
customer machines that some network VPN magic makes accessible as if
they were in our local network, so hostA and hostB are 192.168.233.1 and
192.168.233.2 from my POV although in that customer's network their IPs
are different.

Bye,
Tassilo



      parent reply	other threads:[~2022-01-05 19:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 10:24 Dired command on same host Manuel Giraud
2022-01-04 12:56 ` Michael Albinus
2022-01-04 16:25   ` Manuel Giraud
2022-01-04 18:33     ` Michael Albinus
2022-01-04 19:35       ` Tassilo Horn
2022-01-05  9:35         ` Manuel Giraud
2022-01-05 21:07           ` Tomas Hlavaty
2022-01-06 11:01             ` Michael Albinus
2022-01-07 15:50               ` Michael Albinus
2022-01-10  9:33                 ` Manuel Giraud
2022-01-10 12:56                   ` Michael Albinus
2022-01-10 14:07                     ` Manuel Giraud
2022-01-10 15:00                       ` Michael Albinus
2022-01-10 16:16                         ` Manuel Giraud
2022-01-11  8:25                           ` Michael Albinus
2022-01-11  8:59                             ` Manuel Giraud
2022-01-11  9:10                               ` Michael Albinus
2022-01-10 17:21                         ` Yuri Khan
2022-01-11  8:29                           ` Michael Albinus
2022-01-05 10:34         ` Michael Albinus
2022-01-05 13:02           ` Manuel Giraud
2022-01-05 14:37             ` Michael Albinus
2022-01-05 18:23               ` Manuel Giraud
2022-01-05  9:44       ` Manuel Giraud
2022-01-05 10:40         ` Michael Albinus
2022-01-05 11:08           ` Yuri Khan
2022-01-05 11:46             ` Michael Albinus
2022-01-05 19:55           ` Tassilo Horn [this message]

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=87pmp6c5lt.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --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.
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).