1997-09-15 - The great GAK crack (making GAK economically impossible)

Header Data

From: nospam-seesignature@ceddec.com
To: cypherpunks <cypherpunks@cyberpass.net>
Message Hash: 83af933e11a1442c4a783d83b281f2a3afcc39f5df4a5c00674035e922886d74
Message ID: <97Sep15.114111edt.32260@brickwall.ceddec.com>
Reply To: <v03110715b042cf58c0a2@[139.167.130.248]>
UTC Datetime: 1997-09-15 15:56:21 UTC
Raw Date: Mon, 15 Sep 1997 23:56:21 +0800

Raw message

From: nospam-seesignature@ceddec.com
Date: Mon, 15 Sep 1997 23:56:21 +0800
To: cypherpunks <cypherpunks@cyberpass.net>
Subject: The great GAK crack (making GAK economically impossible)
In-Reply-To: <v03110715b042cf58c0a2@[139.167.130.248]>
Message-ID: <97Sep15.114111edt.32260@brickwall.ceddec.com>
MIME-Version: 1.0
Content-Type: text/plain




If I have to GAK my keys, and there then exists a pgp-gak, then we simply
recruit the same CPU power that generated the millions of DES keys to just
run pgpk-gak with the shortest keylength and send billions of keys to the
GAKserver each week.  Many from out of the US if pgp-gak becomes available
there.

My test software uses a loop that generates a new pair every few seconds
on a pentium (and found some very obscure bugs).  I would be required to
send all those to the gak.gov.  If they really want them...

What it probably means is the govenrment will issue keys or have to
license people to create them.







Thread