From: Michael Albinus <michael.albinus@gmx.de>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Manuel Giraud <manuel@ledu-giraud.fr>
Subject: Re: Dired command on same host
Date: Wed, 05 Jan 2022 12:46:49 +0100 [thread overview]
Message-ID: <87v8yy5rrq.fsf@gmx.de> (raw)
In-Reply-To: <CAP_d_8VhS7a=6yThWB9Av-XwB_Qn00eReKWi9_h440M4MeM6dw@mail.gmail.com> (Yuri Khan's message of "Wed, 5 Jan 2022 18:08:44 +0700")
Yuri Khan <yuri.v.khan@gmail.com> writes:
Hi Yuri,
>> 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.
>
> Additionally, the reverse is also possible: 192.168.0.1 when accessed
> from local machine and 192.168.0.1 when accessed from hostA could be
> two completely different hostsB.
>
> A somewhat reliable way to detect if two jump paths resolve to the
> same host would be:
>
> 1. Through one path, perform some (small) file system modification.
> Like, create a uniquely named file at a known location, and write some
> unique content.
> 2. Through the other path, observe that modification. If successful,
> assume identity.
>
> (Various TLS certificate issuers do this to check that the user who
> requests a certificate for a domain name actually controls the host
> that the domain name resolves to.)
Might be feasible, thanks!
Best regards, Michael.
next prev parent reply other threads:[~2022-01-05 11:46 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 [this message]
2022-01-05 19:55 ` Tassilo Horn
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=87v8yy5rrq.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=yuri.v.khan@gmail.com \
/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).