From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] IP geolocation bug
Date: Tue, 3 Apr 2007 00:35:12 -0700 [thread overview]
Message-ID: <27B24027-7E3A-4C6C-89B0-D190E0C58D11@orthanc.ca> (raw)
In-Reply-To: <775b8d190704022329x6d893632i207fb904946a2609@mail.gmail.com>
On Apr 2, 2007, at 11:29 PM, Bruce Ellis wrote:
> the code is very cool. presto wrote it. not sure if it's public
> tho i have a limbo version.
I guess I'm more curious about how to validate the database of source
IP addresses in the face of tunneling. The Nanog crowd simply foams
at the mouth when this subject comes up.
Has someone come up with a way to characterize packet flows through
tunnels in a way that makes it possible to fingerprint the origin?
That can fingerprint the client on the far end of Tor a pipe?
--lyndon
next prev parent reply other threads:[~2007-04-03 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 3:47 Alex Kritikos
2007-04-03 4:00 ` Russ Cox
2007-04-03 5:29 ` Lyndon Nerenberg
2007-04-03 6:29 ` Bruce Ellis
2007-04-03 7:35 ` Lyndon Nerenberg [this message]
2007-04-03 7:41 ` Bruce Ellis
2007-04-03 8:23 ` Lyndon Nerenberg
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=27B24027-7E3A-4C6C-89B0-D190E0C58D11@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).