December 2003 - cypherpunks-legacy

PINESIGN 2.0: A simple script for PGP signing Pine mail
by Robert A. Hayden 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- After a couple of comments, I've updated Pinesign to a new version. This new version adds the ability to choose whether your ascii signature (ie $HOME/.signature) is added. Some mail servers get confused by extra text, so the ability to make sure nothing extra is added was requested. Basically, if you want to sign the message both digitally and asciilly (is that a word :-), just press return twice after you exit your composing editor. Otherwise, make the selections you want specific to the type of message you are sending. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= #!/bin/sh # PINESIGN v2.0 # Written by: Robert A. Hayden <hayden(a)krypton.mankato.msus.edu> # PINESIGN is a simple program that will allow you to automatically sign # your email and news messages composed with the Pine 3.89 mail reader. It # may also work with other mail and news programs, but it has not been # tested. # INSTRUCTIONS FOR CONFIGURING PINE # # You need to define the following options in Pine. This can be done # either via the SETUP options in the main menu of Pine, or via editing # the .pinerc. # # A) signature-file=" " (an empty space) # B) enable-alternate-editor-cmd # C) enable-alternate-editor-implicitly (optional but recommended) # D) signature-at-bottom # E) editor=<exact path to this script> # INSTRUCTIONS FOR CONFIGURING PINESIGN # # The PGP program must be in your path, and the PGPPATH environment # variable must be defined. See the PGP documentation for details. # # Double check that the first line of this program points to sh. # # Edit the SIGPATH and PINEEDITOR variables to point at your signature # (if any) and the editor you wish to use for your Pine mail. Default # signature will be the file .signature in your $HOME directory. # Default editor is pico -z -t. SIGPATH=$HOME/.signature-pine PINEEDITOR='pico -z -t' # INSTRUCTIONS FOR USING PINESIGN # # When you compose a message, you will compose your message as normal. # # When you exit your editor (control-X in Pico), you will receive a prompt # asking if you wish to add your signature file to the message. If you # respond with y, Y or just press return, your text signature file (often # $HOME/.signature) will be appended to your message. If you type # anything else, your message will not have your signature added. # # Next, you will be prompted as to whether you wish to PGP sign your # message. If you answer with y, Y or return, you will be prompted for your # PGP passphrase and then dumped back to the address/subject section of # Pine. If you type anything else, your message will not be signed. # # If you selected it to be added, your .signature file will be appended # AFTER your digital signature. # # If you have not defined your alternate editor to be run implicitly, you # will need to start it manually. If you do not run the alternate editor, # your .signature file will not be appended and you will also have to do # that manually. It is highly recommended that your define your alternate # editor to run implicitly. ### DO NOT EDIT ANYTHING BELOW THIS LINE UNLESS YOU KNOW WHAT YOU ARE DOING ### $PINEEDITOR $1 clear echo -n "Would you like to add your ASCII signature to this message? [y] " read SIG echo " " echo -n "Would you like to sign this message with your PGP signature? [y] " read PGP if [ "$PGP" = "y" ] then pgp -sat +comment="PGP Signed with PineSign 2.0" $1 mv $1.asc $1 fi if [ "$PGP" = "Y" ] then pgp -sat +comment="PGP Signed with PineSign 2.0" $1 mv $1.asc $1 fi if [ "$PGP" = "" ] then pgp -sat +comment="PGP Signed with PineSign 2.0" $1 mv $1.asc $1 fi if [ "$SIG" = "y" ] then echo " " >> $1 cat $SIGPATH >> $1 fi if [ "$SIG" = "Y" ] then echo " " >> $1 cat $SIGPATH >> $1 fi if [ "$SIG" = "" ] then echo " " >> $1 cat $SIGPATH >> $1 fi -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP Signed with PineSign 2.0 iQCVAwUBMAvz9DokqlyVGmCFAQHq6QP9FztYKCL9lV16HWwY3E6bRzyfpqwoqCag o7hvWivmc81uocYzo54fR5sz0pLCOAIAJL6f0ST+cRM/epdfgn/eEovCDQFZXelB 0I9mmhaUVpUdHFGfw8UD0XhuBuPWbsaNbMfYr07IVEddH8zqOKHANG0QLBmc8aVm 6btQbK8/MWE= =wfGX -----END PGP SIGNATURE----- ____ Robert A. Hayden <=> Cthulhu Matata \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> hayden(a)krypton.mankato.msus.edu \/ Finger for PGP Public Key <=> http://att2.cs.mankato.msus.edu/~hayden

1 0

Re: "Judgement Proof" and Putting Up or Shutting Up
by terrell＠sam.neosoft.com 17 Dec '03

17 Dec '03

> >>> >and, conspiracy theories non-withstanding, we the people do not govern >>> >America --we are only given a short list of politicians who have sold >>> >their soul to CFR's satanist inner circle. >>> >>> What's CFR? >>> >> >>Council on Foreign Relations. > >or Code of Federal Regulations. > or Cupherpunks Fuming and Ranting --buford

2 1

Re: A Chronology on crypto bans
by Duncan Frissell 17 Dec '03

17 Dec '03

At 04:08 PM 7/16/95 -0400, Dave Banisar wrote: >Attempts to ban encryption 1977-1995 > >1977-1980 NSA Director Inman calls crypto born secret. Should be restricted. >Attempts to use Invention Secrecy Act of 1951 to patent inventions by >academic researchers. Attempts to use export control laws to limit >scientific discussion. >NSA Threatens NSF over grants for crypto studies. I hope that you emphasize the big impact of the IEEE/MIT/Scientific American/NSA/"A Proposal for a Public Key Encryption System" flap of 1978(?). An awful lot of people first learned about public-key/private-key algorithms because of that fight. DCF "You men can't fight in here. This is the War Room." -- Dr. Strangelove (or How I Learned to Stop Worrying and Love the Bomb).

1 0

Re: NRC panel wants questions for Law Enforcement on crypto policy
by wb8foz＠nrk.com 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- In April, gnu asked: > Herb Lin called today to ask if the Cypherpunks could come up with a > list of questions for their panel to ask the law enforcement community > about crypto policy. They will be meeting with senior law enforcement > officials like FBI Director Freeh a week or so from now. Did we ever get any feedback on this? - -- A host is a host from coast to coast.................wb8foz(a)nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433 -----BEGIN PGP SIGNATURE----- Version: 2.6 iQCVAgUBMAw6JRqU5+N/mI7JAQEWQQP/UCKWs1m8cMbbG7pAk7CKPjKSAP9yJLvw m+vBFcC+TuFPrQSEjhK7s4qJnck3IzIXl7AmV70NFkr9Dc1Wni7YHkrfhx0nnRRe 7F131pKMNlgypyX/u3FaEHXtCxQV9R5IpYzBAGpvQ++3dzR7LdXcvS2I7kvcWf2G 6knV4KwHvp4= =9+ER -----END PGP SIGNATURE-----

1 0

Re: SurfWatch for employees (ugh)
by sbryan＠maroon.tc.umn.edu 17 Dec '03

17 Dec '03

At 11:36 pm 7/17/95, Greg Broiles wrote: [snip] >(Pedants need not point out that personal choice (and personal filtering) >are always appropriate, and indeed empowering. Neither WebTrack nor >NetSurf are marketed to help people subject themselves to a regime >of repression - they are intended and sold to allow the purchaser to >control what others (perceived as having fewer or no rights) will read [snip] There doesn't seem to be any suggestion that an employer will attempt to control net access that you pay and use yourself with your own equipment. What's the problem? As far as net access from work, that will naturally sort itself out. If unfettered access is beneficial to an enterprise then that will become apparent as "repressive" companies prove incapable of competing with "permissive" companies. +---------------------------------------------------------------------- |Steve Bryan Internet: sbryan(a)maroon.tc.umn.edu |Sexton Software CompuServe: 76545,527 |Minneapolis, MN 55415 Fax: (612) 929-1799 |PGP key fingerprint: B4 C6 E2 A6 5F 87 57 7D E1 8C A6 9B A9 BE 96 CB +----------------------------------------------------------------------

1 0

Re: Re: Root Causes Roots
by Michael Froomkin 17 Dec '03

17 Dec '03

The ported URL of my clipper piece seems to have gone spare. He's another try: www-swiss.ai.mit.edu/6095/articles/froomkin-metaphor/text.html -- Michael Froomkin until Aug 6: michael(a)umlaw.demon.co.uk U.Miami School of Law London, England mfroomki(a)umiami.ir.miami.edu <-- this will still find me PO Box 248087 Coral Gables, FL 33124-8087 Rain. Sun. Rain. Sun. Rain.

1 0

Re: RC4 crack
by shamrock＠netcom.com 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- In article <21076.9507180656(a)exe.dcs.exeter.ac.uk>, aba(a)atlas.ex.ac.uk wrote: >> Is there an easy way to integrate machines who are not on-net 24-7 >> into this protocol? Not all of us have dedicated lines.:) > >Well you could run a local master, ... or as you are using NT right? >you could use Andy's code when he adds socket support to interface to >masters. > >As to the problem of not having 24-7 connectivity, you could either >use the WWW page, or the server (it will do this anyway) will keep >re-trying to get a socket connect to the master until it suceeds, so >when you next go on-line ... wham it gets through again as >connectivity is resumed and says whatever it has been trying to say. >We need it to retry in case of network out (or horror) big master >falling over, until it gets resumed. On many machines that will mean that it will try to initiate a connection to the host. Please allow for a manual connect option. - -- - -- Lucky Green <mailto:shamrock@netcom.com> PGP encrypted mail preferred. - --- [This message has been signed by an auto-signing service. A valid signature means only that it has been received at the address corresponding to the signature and forwarded.] -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Gratis auto-signing service iQBFAwUBMAwdryoZzwIn1bdtAQHrDwGArifMl83/simhOGutmo8FhYgtCMZ+9g5E stSoeOysXuLCvv3EK3PTTUO4LdtPbhnn =rq/L -----END PGP SIGNATURE-----

2 1

Re: SurfWatch for employees (ugh)
by stewarts＠ix.netcom.com 17 Dec '03

17 Dec '03

At 11:36 PM 7/17/95 -0700, Greg Broiles wrote: >Consistent with the trend towards treating employees like children, I'm not surprised someone sees a market for this. I've worked at a number of customer sites that block access to 900 numbers and local pay-per-call numbers, which also blocks access to Time-of-day and some vendors' customer-support numbers. >Webster Network Strategies has announced (but apparently has not >shipped) a product similar to SurfWatch but aimed at an employment >environment. The product is called "WebTrack" and supposedly supports >access lists of URLs, where access can be allowed to "all but these sites" >or "only to these sites". The product also can be configured to log all >Web usage by users subjected to its reign of terror. :) WebTrack >is priced at $7,500 with an annual subscription to I assume for that price that it's a gateway product, rather than a site license for a censored client (which would require sysadmins to go hunt down everybody's copy of netscape...) If so, I hope the system at least offers caching (to save on outside bandwidth requirements and download time), and has a fair amount of security so it doesn't become a hole in the firewall. >its list of interesting (err, forbidden) sites priced at $1,500. Wow! Folks have finally found a way to get paid for looking for porn on the net! :-) Surfwatch doesn't make it's censored list easily available (otherwise it'd probably get pirated, or used as an "interesting sites" index...), but apparently it blocks access to things other than just pornography - does Webster indicate what categories of stuff they're blocking? # Thanks; Bill # Bill Stewart, Freelance Information Architect, stewarts(a)ix.netcom.com

3 2

Re: Is it legal for commercial companies to use PGP?
by stewarts＠ix.netcom.com 17 Dec '03

17 Dec '03

At 09:36 AM 7/18/95 EDT, Jim Grubs, W8GRT wrote: >In practice, I'd probably buy Viacrypt for legal reasons but use PGP anyway. That doesn't help anything - folks asked Bidzos about that one. Of course, if your PGP version happens to output "2.7.1" as a version number, it's not abusing any trademarks.... # Thanks; Bill # Bill Stewart, Freelance Information Architect, stewarts(a)ix.netcom.com

1 0

[shofar@Rt66.com: LEGISLATIVE WATCH AD]
by David Taffs 17 Dec '03

17 Dec '03

fyi... Date: Tue, 18 Jul 1995 08:35:45 -0600 (MDT) From: DJABS <shofar(a)Rt66.com> To: apologia-l(a)netcom.com Subject: LEGISLATIVE WATCH AD _/ _/ _/ _/ _/ _/ _/ _/ _/_/ _/ _/_/_/_/ _/ _/ LEGISLATIVE WATCH ___________________________________________________________ Subscribe Direct >>>>>>>>>>>>>>>>>>>>>>>> shofar(a)RT66.com Interested in catching the political wave? "Legislative Watch" is an electronic newsletter with a focus on First Amendment concerns, religious liberty and other Constitutional issues. Subscribe direct at: shofar(a)RT66.com subject line: <subscribe LW> message line: <email address> <name> ____________________________________________________________________ -- david taffs <dat(a)ebt.com>

1 0