- cypherpunks-legacy - lists.cpunks.org

None
by None 11 Apr '94

11 Apr '94

1 0

None
by None 11 Apr '94

11 Apr '94

1 0

None
by None 11 Apr '94

11 Apr '94

1 0

None
by None 11 Apr '94

11 Apr '94

1 0

None
by None 03 Apr '94

03 Apr '94

1 0

Encryption Privacy for Digitized Money
by Jeff Davis 30 Mar '94

30 Mar '94

Howdy Stanton, I'm going to see Thomas M. Hoenig, Federal Reserve Bankf Kansas City President, (1 of 12 in the US), in a public forum Tuesday, 5 April. I need a crash course in encryption privacy for credit card use and digitized financial transactions. Given the opportunity to ask a pointed question or two in a room full of people, I'll have about 3 minutes to gain a room full of converts, and perhaps Hoenig. I have to be polished and precise. Please help. -- PGP PUBLIC KEY available via finger- don't email home without it! * eagle(a)deeptht.armory.com email info(a)eff.org * *** O U T L A W S On The E L E C T R O N I C F R O N T I E R **** ***** Committed to Free Public Internet Access for World Peace ***** -- Stanton McCandlish * mech(a)eff.org * Electronic Frontier Found. OnlineActivist "In a Time/CNN poll of 1,000 Americans conducted last week by Yankelovich Partners, two-thirds said it was more important to protect the privacy of phone calls than to preserve the ability of police to conduct wiretaps. When informed about the Clipper Chip, 80% said they opposed it." - Philip Elmer-Dewitt, "Who Should Keep the Keys", TIME, Mar. 14 1994

1 0

Summit Coordinates are Coming
by Richard Civille 28 Mar '94

28 Mar '94

Good Morning! Please repost on other lists/online communities/community networks you participate in if they are not receiving these announcements. Here's the wave building around the Summit. More coming soon. Stay tuned: * The Summit will take place Tuesday, March 29th from 8:30AM to 5:00 at the Hyatt Regency on Capitol Hill. * Attendance in DC is now over 600 people. We can take no further registrations. * Hundreds email messages and net postings have been generated around the issues the Summit will address, and that's only the materials we've seen on the few lists we can monitor with extremely limited resources. We've heard from teachers in Columbia, network managers in Singapore, Free-Nets in Canada, rural librarians, and citizen advisory groups to state telecommunications initiatives to mention only a few. * About 40 people around the country offered to help organize offline discussion groups. To date, we've received reports from about a dozen so far. At least one group now plans to conduct further NII organizing activities in their state. * Portions of the Summit will be broadcast live in 20 radio markets around the country including major metropolitan areas. We will list the participating radio stations sometime on Monday when the full list is compiled. * Nine foundations and the Administration's Information Infrastructure Taskforce have directly contributed to the event. * There is space on C-Span's Tuesday broadcast schedule for a "public policy conference" but no commitment yet. This is not unusual for C-Span. Please note that there is not a specific commitment from C-Span to carry this event live. This is their normal way of handling events. * The Summit gopher will be announced tomorrow. We are VERY interested in having your organization's gopher server establish a pointer to the Summit gopher. Please let us know if you would like to do this. We will announce the Summit gopher coordinates sometime on Monday. * The Summit Mosaic server will also be announced. * The Summit panels and proceedings will be quickly summarized and posted throughout the day to the Nets, to the Summit gopher and Mosaic servers. We urge you to respond to these summaries with SPECIFIC questions addressed to SPECIFIC panelists. We will do our best to forward several questions per panel into the live discussions. Send you questions and ongoing comments to the Summit at: <summit(a)tmn.com> * Followup activities and organizing efforts have already begun. Please let us know how you would like to get involved. Remember: The public doesn't get the chance to design new infrastructure very often. ----------------------------------------------------------------------- Center for Civic Networking Richard Civille P.O. Box 65272 Washington Director Washington, DC 20035 rciville(a)civicnet.org (202) 362-3831 ------------------------------------------------------------------------ -- Stanton McCandlish * mech(a)eff.org * Electronic Frontier Found. OnlineActivist "In a Time/CN poll of 1,000 Americans conducted last week by Yankelovich Partners, two-thirds said it was more important to protect the privacy of phone calls than to preserve the ability of police to conduct wiretaps. When informed about the Clipper Chip, 80% said they opposed it." - Philip Elmer-Dewitt, "Who Should Keep the Keys", TIME, Mar. 14 1994

1 0

Re: Senator Leahy's hearing
by cspanviewr＠aol.com 17 Mar '94

17 Mar '94

We've had quite a bit of interest and e-mail regarding the Clipper chip hearings and we passed it all on to our programming department for consideration at today's shoot meeting. Unfortunately, we will not be covering this hearing. Thanks for your interest in C-SPAN and please feel free to write again when an event of interest comes up.

1 0

Re: (forward message on privacy) (fwd)
by tomj 08 Mar '94

08 Mar '94

> Today I ran into a situation that made me completely nausiated and feel like > my privacy had been completely invaded... It involves a chip which is > implanted in animals and used for identification... Humans are worth more money, and genotyping will do the same thing, for cheaper, and with little outcry. Implanted chips means at least a doctors visit for every humasn in the country; genotyping only happens like fingerprinting, when you get a drivers license or soemthing. I think the underlying concern is OK, but misplaced worrying about kitty-cats. Cats can certainly be violated, but usually aren't aware of it ahead of time, and there's not much they can do about it :-) Consider also they generally *kill* cats they can't return. A chip implant under these circumstances seems not a problem. -- Tom Jennings -- tomj(a)wps.com -- World Power Systems -- San Francisco, Calif.

1 0

Re: Standard for Stenography?
by Jef Poskanzer 03 Mar '94

03 Mar '94

>I think it is great that Jef is working on a steganography implementation, >but IMO the notion of "random offsets" is so fundamentally misguided that I >hope he will reconsider. I already did - the offsets idea was my second thought, permutation is third. I'm a big fan of the rigidly separated software tools approach. Just look at the pbmplus tookkit. But I also think it's perfectly ok to combine functions when there's a good enough reason. I think this is such a case. The problem is the length field - you've got to have it, and it's recognizable because it begins with a run of 0s. So the stego program should hide it. Mac Stego hides it by XORing with the 2nd-to-lsb of the following 32 bytes - that's a hack, and it won't slow an attacker down for a microsecond. jsteg, if I remember right, does some variable field width encoding - better, but it also remains recognizable to some extent. My solution is to store the file's bits in a specified pseudorandom permutation of the image's available bit positions. It's kind of like the frequency hopping of spread spectrum radio. This hides the length field very thoroughly. It also happens to hide anything else recognizable about the original file. Yes, you should use Stealth PGP for complete security, and my man page will tell you this. However, even with regular PGP the permutation will give you good security against casual attacks, perhaps even commercial attacks. Now, if you can think of a natural, simple interface for a standalone file permutation generator, I'll be happy to separate that part out, and make pnmstego just read bits and stick them in the image in order. The problem with separating it is the bits you want to leave alone. Either the file permutation generator has to generate *trinary* output, which seems gross, or the stego pipeline will have to include an initial DEstego step to extract the unmodified bits from the image. Either of those possibilities is more complicated than just building the permuter into pnmstego. --- Jef

2 1