RProcess <nobody@invalid.org> wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Apologies for Jack B Nymble
>
Not this shit again.

Listen up good.  This is not RProcess. It's not even a good forgery.

user1@home:~$ gpg --list-keys rprocess
pub   2048R/9310EE89 1997-11-05
uid                  RProcess <rprocess@nym.alias.net>

user1@home:~$ gpg --fingerprint --verbose --list-sigs rprocess gpg: using PG
P trust model
pub   2048R/9310EE89 1997-11-05
Key fingerprint = 97 AE F5 64 61 F0 D9 28  13 33 DE A5 06 7E 8E B4
uid                  RProcess <rprocess@nym.alias.net>
sig          9310EE89 1998-03-20  RProcess <rprocess@nym.alias.net>
sig          A428D689 1999-04-02  [User id not found]
sig          C19E5B2F 2000-07-27  [User id not found]
sig          3AC2839F 2001-05-21  [User id not found]
rev          C19E5B2F 2001-05-31  [User id not found]
sig          2EE9F536 1999-04-02  [User id not found]
sig          40D8EDF8 1999-12-25  [User id not found]

As you can see above, Rprocess used a pgp 2.6.x key
that was created on Nov 05, 1997

The forger's key is not available from keyservers and the original is
and the Key-Id of the forgery does not match either.

user1@home:~$ gpg --verify alleged-rprocess-post.asc
gpg: Signature made Wed 14 Sep 2005 06:29:56 PM CDT using RSA key ID 33723AB
9
gpg: requesting key 33723AB9 from ldap server keyserver.pgp.com
Host:           keyserver.pgp.com
Command:        GET
Server:         PGP Universal Server
Version:        2.0.4
gpgkeys: key FA53E5A133723AB9 not found on keyserver
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: Can't check signature: public key not found

Finally, everybody knows that RProcess cannot possibly make any posts at all
since He is dead.  Please note that his dissapearance coincides with the dea
th
of Disastry.

Disastry was RProcess.

[ Post a follow-up to this message ]

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

Borked Pseudo Mailed schreef:
[snip]
> pub   2048R/9310EE89 1997-11-05
>       Key fingerprint = 97 AE F5 64 61 F0 D9 28  13 33 DE A5 06 7E 8E B4

That is the key.

> Disastry was RProcess.

Then there should be code similaries between the mixmaster parts he did
for windows and Reliable/JBN2. I think this is not true. RProcess used
insecure random numbers, Disastry did the entropy gathering for
mixmaster under windows. I think it was pretty good.

Thomas
- --
Robert Heinlein: "When in danger or in doubt, run in circles, scream and
shout"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQB5AwUBRHrIfwEP2l8iXKAJAQEr/QMfVLcPSV8XRGXBZPMMOAZrADQbuiJJKX8u
xxtveKMMlprDRs/iWsOPAawDh6ntcFpjtEF3W3dz/gfLzddrJMOcQTY6mN/kJw7w
 ADqEdGI7nf40OKnI9rdR+tWxZvagp+L6DXZ0Sg==

=jFbD
-----END PGP SIGNATURE-----

[ Post a follow-up to this message ]