From: Amir Herzberg [EMAIL PROTECTED]
So, if anyone has a reliable ftp server where I could post the lectures
(and update them via ftp), please let me know.
You might also want to look into installing a tracker and sharing them with
BitTorrent http://bitconjurer.org/BitTorrent/ - it should
From: Marcel Popescu [EMAIL PROTECTED]
Hence my question: is there some approximate hash function (which I
could
use instead of SHA-1) which can verify that a text hashes very close to
a
value? So that if I change, say, tabs into spaces, I won't get exactly the
same value, but I would get
From: Hal Finney [EMAIL PROTECTED]
As you are probably aware, existing hashcash implementations do not base
the stamp on the message content. Instead they only lock the stamp to
the receiver's email address. Then the receiver keeps a list of the
hashcash stamps he has seen recently, to
From: [EMAIL PROTECTED] [mailto:owner-
[EMAIL PROTECTED] On Behalf Of Adam Back
Sent: Wednesday, December 22, 2004 11:48 PM
I would think the simplest canonical counter-attack would be to make a
p2p app that compares diffs in the binary output (efficiently rsync
style) accumulates enough
From: [EMAIL PROTECTED] [mailto:owner-
[EMAIL PROTECTED] On Behalf Of Rich Salz
The other day I sent Amir Herzberg a private note saying I thought his
new tool was pretty neat, and though I'm sure he's heard it a lot,
thanks. He said nope, nobody else has said it, and I was stunned.
My
From: [EMAIL PROTECTED] [mailto:owner-
[EMAIL PROTECTED] On Behalf Of Peter Gutmann
I can't understand why they didn't just use TLS for the handshake (maybe
YASSL) and IPsec sliding-window + ESP for the transport (there's a free
minimal implementation of this whose name escapes me for use by
Do you have some articles about these protocols?
The authoritative reference for TLS is the TLS RFC
(http://www.ietf.org/rfc/rfc2246.txt). The authoritative reference for IPsec
is of course the IPsec RFC (http://www.ietf.org/rfc/rfc2401.txt). As to why
they wouldn't use these as they stand,