1994-12-05 - autosign designs

Header Data

From: Alan Pugh <0003701548@mcimail.com>
To: cypherpunks <cypherpunks@toad.com>
Message Hash: d02c2f5536ad5dc3f3f3a65c7f4e7f3d1e62492f53fe5ff1a1708b0fcb5745d4
Message ID: <73941205062037/0003701548PJ3EM@MCIMAIL.COM>
Reply To: N/A
UTC Datetime: 1994-12-05 06:21:46 UTC
Raw Date: Sun, 4 Dec 94 22:21:46 PST

Raw message

From: Alan Pugh <0003701548@mcimail.com>
Date: Sun, 4 Dec 94 22:21:46 PST
To: cypherpunks <cypherpunks@toad.com>
Subject: autosign designs
Message-ID: <73941205062037/0003701548PJ3EM@MCIMAIL.COM>
MIME-Version: 1.0
Content-Type: text/plain


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

>The point is that if Eric insists on arbitrary rules that
>threaten the list, some bright c'punk will "write code" to circumvent
>the assinine rule. Use technology to solve problems...

TM> Not exactly;  that's how the thought train began, but something that was
TM> just for circumventing the rule would have a slightly different solution:
TM> generate a new key for each post, sign with the key, and throw it away
TM> (so that no information would be contained in the signature).  The
TM> signatures from the current system does contain some information.

TM> I might yet still implement something that does the above: at this point,
TM> it's pretty trivial, aside from hacking PGP to generate a key with a
smaller
TM> than 384-bit modulus (to conserve computrons).

You might also want to check for low computron usage if you can and
generate a bunch of keys for later use when the machine is fairly
idle. (if it's ever in such a state - don't know if you are on a
multiuser system or not). that way, during peak times, you aren't 
burning big-time cycles generating keys. 

TM> As an aside, this is my general approach to things: I'll start off in
TM> a particular direction and then vary it as I think of new things.  I
TM> only mention it here because I often state that I'm going to do something
TM> and then the result is somewhat different than my original summary. 
TM> I've done this a couple times here, and I'm hoping that explaining this
TM> will make me appear, well, less flakey.

the above is how i code. of course, i'm not a professional - just
having a good time.

=snip=

amp
<0003701548@mcimail.com>
December 5, 1995   1:4
 

-----BEGIN PGP SIGNATURE-----
Version: 2.61

iQEVAwUBMMO2/ygP1O9KJoPBAQF6Ggf8CG6vLPnxKLB0LKa8rwq9exCvju1HJled
xzovmn+nb3XqyRVllrwhSdSWTVaQrFbT0tv+9HxZRUC/vywp3b+qA4cY338vqZMo
KdP7vi6MtFNFNUCk9uiYesoi0jC5bB2Nzraxx0ETwulCR31QP/MRtT/s3asoNU+/
MCCydAIbcPFGjjNAoFvsJLdpNJjhT4yWkSv4NcnhnzbqqKgo/ZvrzRczZUnKGPTT
BrIBn5DJ4juJn0FUCd3GSFhNGnVnDFewFpQe9Rkpr6Pk1uyLou5FjXwhFx7iAJHV
9DApIJqkmYe583cPsCuKZyHA87mgfcNlp4L785GWks56+hFQ4TygAQ==
=xNlv
-----END PGP SIGNATURE-----






Thread