1997-11-12 - No Subject

Header Data

From: Anonymous <nobody@REPLAY.COM>
To: cypherpunks@cyberpass.net
Message Hash: a7f471817581f79b830941d7a13917b18c78916435de287900609ec8ea89970d
Message ID: <199711121125.MAA21236@basement.replay.com>
Reply To: <199711112333.RAA02693@dfw-ix3.ix.netcom.com>
UTC Datetime: 1997-11-12 11:47:09 UTC
Raw Date: Wed, 12 Nov 1997 19:47:09 +0800

Raw message

From: Anonymous <nobody@REPLAY.COM>
Date: Wed, 12 Nov 1997 19:47:09 +0800
To: cypherpunks@cyberpass.net
Subject: No Subject
In-Reply-To: <199711112333.RAA02693@dfw-ix3.ix.netcom.com>
Message-ID: <199711121125.MAA21236@basement.replay.com>
MIME-Version: 1.0
Content-Type: text/plain



-----BEGIN PGP SIGNED MESSAGE-----

Try this Monty:

The new owner of the Monty persona is defined to be the first public
key which is signed by Monty's private key and posted to this forum.

So the buyer sends Monty a public key, and Monty signs it and posts it
to the list.  (Optionally via a trusted third party to ensure fair
play.  There is a race condition in the making there but it's not too
bad, we could fix it if we were bothered.)

So Monty can cheat and post one he signed earlier selling to a
different key, but we will ignore those because we base it on first
posted.

Buyers will no longer be interested in buying Monty's persona after
they have seen it sold, because they know it is no longer his.

The person who buys Monty's persona could resell it.  Using the same
protocol.

Amad3us

(As there seems to be some confusion about my public key block, here
it is again with Version field and blank line; I surmise that the
problem Bill Stewart encountered was that pgp5.0 can't handle armor
without blank lines (or maybe without blank lines and Version))

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i

iQCVAwUBNGmOY/KMuKFNFivhAQGtYQQAiuHfEmQsxdyymteBsXFbPjReG8UdUemo
rBAextXL8cwohQ20ub1w/Icn+r6zSDE7qHz7nCDaUS/0lUTTVHv5W47RyEf1vvwn
U6bEf84frSKwbmAghvb6jMMKY3qPVu/UBrVtof3cryKoNxQXxwDdOA6nyYHngdp0
3D/WZmMDUfc=
=y2jn
-----END PGP SIGNATURE-----
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3i

mQCNAzRbd7MAAAEEAONwsEpUgiezyfP6lxBzM5SfHJS6MK12JyR09KBZp2rrW680
4vbKAO/oteftRRM1jYYaQM6pUd2Tbb9z+cSuQGr2GH9kQ0Y7bllh89E1PItj7frG
ARSCbt1gbbXDXEICY8Ne1zZB7FfMt2qGVBdrKG/i2vfdZa5+n/KMuKFNFivhAAUR
tCNBbWFkM3VzIDxjeXBoZXJwdW5rc0BjeWJlcnBhc3MubmV0PokAlQMFEDRbjMPy
jLihTRYr4QEB38ED/1P9L2yLURl5B2GJok3eIf6EnF1ahFxSK7wuK++YfKRKb3Ku
oPTzwSXH+92PZX28dpC+aYu8Qb0dMSCk4Cadn9cxz4n42u509JU4z0o897lB4u2I
TxV3YKbBAQSv/jZ/Gq8drdFtemQXUPigNL6IjDAPc/REiHv7IZNKAniSBo1P
=N8Gg
-----END PGP PUBLIC KEY BLOCK-----






Thread