December 2003 - cypherpunks-legacy

Re: Solution for US/Foreign Software?
by jim bell 17 Dec '03

17 Dec '03

At 06:28 PM 12/6/95 -0600, you wrote: > >Bill Stewart writes: > > I had interpreted the suggestion differently - rather than a system with > > user-accessible crypto hooks, the manufacturer could ship a binary patch > > upgrade for US customers to install. The internal design would presumably > > have crypto hooks (i.e. subroutine calls); they can't ban that. > >No, they can't *ban* it, but there's no reason to suspect that they >won't revoke the export license after the scheme becomes clear. And >of course the patch itself would not be exportable. If there's a >"wink wink nudge nudge" implication that the patch would make its way >overseas, I don't understand why that's really any more likely than >the US-only version getting out. It isn't that it's "more" likely. It's probably JUST AS likely. But remember, the goal is to allow the US company to actually MAKE MONEY, not to bootleg its products. The system I've described would be intended to allow a manufacturer to continue to sell its exportable product legally.

1 0

Re: Netscape gives in to key escrow
by James A. Donald 17 Dec '03

17 Dec '03

At 02:14 AM 12/6/95 -0800, Jeff Weinstein wrote: > Our representative at the NIST meeting said [GAK is evil] there today. > It should be up on the web site in a few days when he gets > back from DC. Dang, I was just working on my "death to netscape" page before I started reading my mail. I had done the text, and was going to start stripping background out of the dirty pictures, so that my server would not drop to its knees. The text is visible when viewed in netscape, but the pictures are not. Should have done the fun part first. Let us know when the position is put on the web. --------------------------------------------------------------------- | We have the right to defend ourselves | http://www.jim.com/jamesd/ and our property, because of the kind | of animals that we are. True law | James A. Donald derives from this right, not from the | arbitrary power of the state. | jamesd(a)echeque.com

1 0

Persona PCMCIA URL?
by Dave Del Torto 17 Dec '03

17 Dec '03

Does anyone have a URL for data sheets on the Persona cards?

1 0

Plea for information
by REES＠rmcs.cranfield.ac.uk 17 Dec '03

17 Dec '03

I would be interested in learning more about the politics and mathematics of cryptography, but my site does not have access to a newsreader. As I am new to the Net, I am not aware of any acceptable way around this, which will allow me to read and contribute to the cypherpunk and related newsgroups - please can you help me out on this matter. Also, I would like to know how best to understand cryptography - I have a textbook on the basic mathematical concepts underlying the techniques but it is too advanced for my current knowledge in this field (A-level - ie. end of high school), please can you suggest a good starting place for me. Thanks in advance for your assistance, Daniel Rees

1 0

(Fwd) General release of Open Encryptor interface for PGP
by Siberia 17 Dec '03

17 Dec '03

------- Forwarded Message Follows ------- Priority: normal Date: Fri, 8 Dec 1995 00:08:30 +1200 Reply-to: Pegasus Mail Announcments <PM-NEWS(a)UA1VM.UA.EDU> From: John Navas <JNavas(a)aimnet.com> Organization: The Navas Group, Dublin, CA, USA Subject: General release of Open Encryptor interface for PGP To: Multiple recipients of list PM-NEWS <PM-NEWS(a)UA1VM.UA.EDU> -----BEGIN PGP SIGNED MESSAGE----- Release 1.0 of my Open Encryptor interface for PGP has been posted on my anonymous FTP server <ftp://ftp.aimnet.com/users/jnavas/winpmail/> PGP information is available at http://www.mantis.co.uk/pgp/pgp.html The MIT distribution of PGP is at ftp://net-dist.mit.edu:/pub/PGP/ ViaCrypt (commercial version of PGP) is at http://www.viacrypt.com/ The International PGP Home Page is at http://www.ifi.uio.no/~staalesc/PGP/ Release notes for PGP Open Encryptor Interface version 1.0: 1. Only public key cryptography is supported in this release, NOT conventional cryptography. 2. Basic Key Management functions are implemented: a. To add a public key block contained in a message to your Key Ring, either Open or select the message before invoking Key Management. (If a public key block is placed in a digitally signed and/or encrypted message, it will not be recognized automatically by this interface.) You can also invoke Key Management and paste a public key block into the dialog from the Windows Clipboard (which does of course work with a signed and/or encrypted message). b. You can check to see if a given email address is on your Key Ring -- just paste the email address (without the name) into the dialog box control. No other Key Management functions are implemented at this time. 3. Both digital signing and signature verification are implemented: a. If a secret pass phrase is needed (and not provided in the PGPPASS environment variable), it MUST be provided each time in the WinPMail Password field. b. Please note that signature verification is a strictly *manual* process -- you must expliticly use the WinPMail menu. This is a characteristic of WinPMail, NOT this interface. 4. When encrypting: a. The recipient email address (e.g., jnavas(a)navasgrp.com) will normally select the appropriate public key automatically, but it may be overridden with an entry in the WinPMail Password field. b. Your recipient may need to add also-known-as entries to his/her public key to ensure that you match on various forms of email addresses (e.g., also known as jnavas(a)mailhost.aimnet.com) c. The WinPMail Password will NOT be used for encryption of a digitally signed message, since the Password is then reserved for the secret pass phrase (whether one is needed or not). 5. If encryption or signing fails (e.g., because the recipient is not on your key ring, or because your secret pass phrase was incorrect), an empty message will be sent. This is a characteristic of WinPMail, NOT this interface. 6. Copies to self of encrypted and/or signed messages are NOT encrypted and/or signed. This is a characteristic of WinPMail, NOT this interface. (If you want an encrypted and/or signed copy, BCC yourself.) 7. It is normally NOT possible for you to decrypt message that you have encrypted for someone else (since you do not have that person's secret key). However, you can establish a master decryption key by setting the PGPJNKEY environment variable to a string needed to select the appropriate public key (yours or not). TEST FOR PROPER OPERATION (BY DECRYPTING A MESSAGE ENCRYPTED FOR SOMEONE ELSE) BEFORE YOU DEPEND ON IT! It may be a good idea to add an also-known-as alias just for this purpose. 8. The Cancel button does not work on the Decryption dialog box. This is a characteristic of WinPMail, NOT this interface. 9. When you do a Find on a folder, WinPMail puts up the Decryption key dialog for every encrypted message, even when you are only searching headers, which can make the process painful. This is a characteristic of WinPMail, NOT this interface. 10. Attachments to encrypted messages are NOT supported. (Outgoing attachments to encrypted messages are NOT encrypted, and incoming binary attachments are corrupted.) This is a characteristic of WinPMail, NOT this interface. 11. Windows 3.10, Windows for Workgroups 3.11, and Windows 95 are supported. Windows NT and OS/2 have NOT been tested and are NOT currently supported. USE THEM AT YOUR OWN RISK. 12. MIT PGP 2.6.2 is supported in this release. Other versions of PGP have NOT been tested and are NOT currently supported. ViaCrypt PGP has NOT been tested for this release, but is expected to be supported in a subsequent release. USE THEM AT YOUR OWN RISK. 13. Reassembly and decryption of multiple-part PGP messages is NOT supported. 14. PGP messages sent by other WinPMail Open Encryptor PGP interfaces may not trigger this interface. (Other PGP sources should not be a problem.) This is a characteristic of WinPMail, NOT this interface. To install the PGP Open Encryptor Interface: 1. UnZIP in a subdirectory of FORMS called PGPJN (e.g., \PMAIL\FORMS\PGPJN). 2. Copy the PGPJNP.FFF file up to your WinPMail directory (e.g., \PMAIL). 3. Make sure that PGP is installed correctly, and that the PGPPATH environment variable is set correctly. (If PGPPATH is set, PGP does not need to be in your PATH.) 4. Encrypt and send a message to yourself to test operation. John Navas <JNavas(a)NavasGrp.com> -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQBVAwUBMMbC7O5ya4p8vxAtAQHO7wH/atOJoEbrUX2G/Zzr3jZCvblQZXBWzlv6 KTNraPxaui8jtw83U+pZYWV/jNVJ48Fw4Fy6XeQrtdzXJsi0tKJZtg== =jZvU -----END PGP SIGNATURE-----

1 0

(Fwd) General release of Open Encryptor interface for PGP
by Jeff Hupp 17 Dec '03

17 Dec '03

I believe this may be of intrest to those on this list. Pegasus is available at <ftp://risc.ua.edu/pub/network/pegasus/winpm223.zip> Enjoy. ------- Forwarded Message Follows ------- Priority: normal Date: Fri, 8 Dec 1995 00:08:30 +1200 Reply-to: Pegasus Mail Announcments <PM-NEWS(a)UA1VM.UA.EDU> From: John Navas <JNavas(a)aimnet.com> Organization: The Navas Group, Dublin, CA, USA Subject: General release of Open Encryptor interface for PGP To: Multiple recipients of list PM-NEWS <PM-NEWS(a)UA1VM.UA.EDU> -----BEGIN PGP SIGNED MESSAGE----- Release 1.0 of my Open Encryptor interface for PGP has been posted on my anonymous FTP server <ftp://ftp.aimnet.com/users/jnavas/winpmail/> PGP information is available at http://www.mantis.co.uk/pgp/pgp.html The MIT distribution of PGP is at ftp://net-dist.mit.edu:/pub/PGP/ ViaCrypt (commercial version of PGP) is at http://www.viacrypt.com/ The International PGP Home Page is at http://www.ifi.uio.no/~staalesc/PGP/ Release notes for PGP Open Encryptor Interface version 1.0: 1. Only public key cryptography is supported in this release, NOT conventional cryptography. 2. Basic Key Management functions are implemented: a. To add a public key block contained in a message to your Key Ring, either Open or select the message before invoking Key Management. (If a public key block is placed in a digitally signed and/or encrypted message, it will not be recognized automatically by this interface.) You can also invoke Key Management and paste a public key block into the dialog from the Windows Clipboard (which does of course work with a signed and/or encrypted message). b. You can check to see if a given email address is on your Key Ring -- just paste the email address (without the name) into the dialog box control. No other Key Management functions are implemented at this time. 3. Both digital signing and signature verification are implemented: a. If a secret pass phrase is needed (and not provided in the PGPPASS environment variable), it MUST be provided each time in the WinPMail Password field. b. Please note that signature verification is a strictly *manual* process -- you must expliticly use the WinPMail menu. This is a characteristic of WinPMail, NOT this interface. 4. When encrypting: a. The recipient email address (e.g., jnavas(a)navasgrp.com) will normally select the appropriate public key automatically, but it may be overridden with an entry in the WinPMail Password field. b. Your recipient may need to add also-known-as entries to his/her public key to ensure that you match on various forms of email addresses (e.g., also known as jnavas(a)mailhost.aimnet.com) c. The WinPMail Password will NOT be used for encryption of a digitally signed message, since the Password is then reserved for the secret pass phrase (whether one is needed or not). 5. If encryption or signing fails (e.g., because the recipient is not on your key ring, or because your secret pass phrase was incorrect), an empty message will be sent. This is a characteristic of WinPMail, NOT this interface. 6. Copies to self of encrypted and/or signed messages are NOT encrypted and/or signed. This is a characteristic of WinPMail, NOT this interface. (If you want an encrypted and/or signed copy, BCC yourself.) 7. It is normally NOT possible for you to decrypt message that you have encrypted for someone else (since you do not have that person's secret key). However, you can establish a master decryption key by setting the PGPJNKEY environment variable to a string needed to select the appropriate public key (yours or not). TEST FOR PROPER OPERATION (BY DECRYPTING A MESSAGE ENCRYPTED FOR SOMEONE ELSE) BEFORE YOU DEPEND ON IT! It may be a good idea to add an also-known-as alias just for this purpose. 8. The Cancel button does not work on the Decryption dialog box. This is a characteristic of WinPMail, NOT this interface. 9. When you do a Find on a folder, WinPMail puts up the Decryption key dialog for every encrypted message, even when you are only searching headers, which can make the process painful. This is a characteristic of WinPMail, NOT this interface. 10. Attachments to encrypted messages are NOT supported. (Outgoing attachments to encrypted messages are NOT encrypted, and incoming binary attachments are corrupted.) This is a characteristic of WinPMail, NOT this interface. 11. Windows 3.10, Windows for Workgroups 3.11, and Windows 95 are supported. Windows NT and OS/2 have NOT been tested and are NOT currently supported. USE THEM AT YOUR OWN RISK. 12. MIT PGP 2.6.2 is supported in this release. Other versions of PGP have NOT been tested and are NOT currently supported. ViaCrypt PGP has NOT been tested for this release, but is expected to be supported in a subsequent release. USE THEM AT YOUR OWN RISK. 13. Reassembly and decryption of multiple-part PGP messages is NOT supported. 14. PGP messages sent by other WinPMail Open Encryptor PGP interfaces may not trigger this interface. (Other PGP sources should not be a problem.) This is a characteristic of WinPMail, NOT this interface. To install the PGP Open Encryptor Interface: 1. UnZIP in a subdirectory of FORMS called PGPJN (e.g., \PMAIL\FORMS\PGPJN). 2. Copy the PGPJNP.FFF file up to your WinPMail directory (e.g., \PMAIL). 3. Make sure that PGP is installed correctly, and that the PGPPATH environment variable is set correctly. (If PGPPATH is set, PGP does not need to be in your PATH.) 4. Encrypt and send a message to yourself to test operation. John Navas <JNavas(a)NavasGrp.com> -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQBVAwUBMMbC7O5ya4p8vxAtAQHO7wH/atOJoEbrUX2G/Zzr3jZCvblQZXBWzlv6 KTNraPxaui8jtw83U+pZYWV/jNVJ48Fw4Fy6XeQrtdzXJsi0tKJZtg== =jZvU -----END PGP SIGNATURE----- -- JHupp(a)gensys.com |For PGP Public Key: http://gensys.com |finger jhupp(a)gensys.com Expertise in one field does not carry over into other fields. But experts often think so. The narrower their field of knowledge the more likely they are to think so.

1 0

Re: GAK
by Daniel Miskell 17 Dec '03

17 Dec '03

Scott Binkley writes: >I heard a while back about being able to "split" up a PGP key. What >about >splitting up the key into many parts, and giving them out to multiple >INDEPENDANT >agencies. ie: One piece goes to the FBI, one to the NSA, one to some >other committee, and >so on. That way, no goverment body could just tap your conversations >without getting >approval from others, and gaining the pieces of your key. > >just a thought Why give them your key in the first place? Personally, I wouldnt trust any government agency with even a fraction of my key - what makes you think they arent *allready* working together? Then you have effectively given your key, and all of your private mail, to the government, no restrictions. --- _________________________________ *!Cheese Doctrine:!* Though cultured over time, and aged to perfection, one must not yield to produce mold. One must also not belittle themselves by conforming to the "whiz", but melt over the unprocessed ideas of Ghuda. _________________________________

1 0

Re: Responding to Exon -- technology is not enough
by Daniel Miskell 17 Dec '03

17 Dec '03

Bill Humphries writes: >Instead of figuring out how to build a new treehouse that excludes Exon and >Hyde, how about fighting the damned bill in the courts? Possibly because a) it is allready being faught, and b) court battles cost money which most folks dont have. If people are unfamilliar with encryptation, they should do a web search and find out what they can, then use it. What you are saying (as far as encryptation not being an answer because so few know how to use it) feels like "lets not use a gun to defend our home from intrusion because so few know how to handle them. You dont just assume that bewcause you dont know how that you give up. You learn how. That is how i found this list - because i did a little running around. Munster --- _________________________________ *!Cheese Doctrine:!* Though cultured over time, and aged to perfection, one must not yield to produce mold. One must also not belittle themselves by conforming to the "whiz", but melt over the unprocessed ideas of Ghuda. _________________________________

1 0

Prayers Pay
by nobody＠REPLAY.COM 17 Dec '03

17 Dec '03

The raiders hit early this morning, banging the door about 4 AM, me groggily peeking out, a subpoena wadded into my shirt, then the bastards barged in. My ex-wife holding back, grinning like shit, saying you're fucked this time Johnny wee-dick. The black suits took all of it, computers, backup disks and tapes, printers, scanners, plotters, fuck, even the phones and message box -- jeez, why those? Harassment, teaching you a lesson, Bess my shark phoned just now, they shut your business down, take weeks to rummage the equipment and data, give it back slowly, one at a time, no hurry, wanting you to ache in case they find nothing. Swift justice, she hisses, even if you're innocent, cause nobody really is, they want you to scream, use you to broadcast a scare. Fuckups are getting gutted all over that Net Playboytoy. Six others this week, Bess coughs on, dragging deep, it's gonna rain even heavier in Exon's maelstrom, sweet darling maryjesus, prayers pay.

1 0

Plea for information
by John Young 17 Dec '03

17 Dec '03

Daniel, During a year in this penitentiary, here's five I heard the older cons mutter: 1. "Applied Cryptography," Second edition just out, Bruce Schneier, Wiley, 1996. Flip through it and stare in disbelief and awe. Enjoy 2-5 and return, anxious. 2. "The Codebreakers," David Kahn, Macmillan, 1967. Crypto- biblical tales of lying and cheating via momentarily secret tricks. Continued in 3. 3. "Cyphernomicon," Tim May et al, 1006-Far Future. A wad of inspiring sci-non-fi of miscreating, eluding hard-bars and regaling in off-shore soft-bars. Also, C4. 4. "Cypherpunks archives," All Wholesomes, <www.hks.net>, Infinite. The stingers honey pot for luring beekeepers into berzerk swarms. Wear 5 for protection. 5. "PGP." Download it somewhere somewhat legally while you can, practice picking this sitar. And heave some brick- bucks at benefactor Phil for malefactor dues.

1 0