From: jason carr Area: Public Key Encryption To: Shawn McMahon 4 Oct 94 08:57:50 Subject: Re: PGP Signatures UpdReq Shawn McMahon wrote in a message to jason carr: jc> Well, yeah. But that's the purpose. Maybe someone could code in jc> a switch that would hide the sig in a FTN msg. ??? SM> I understand that that's the purpose, Jason, but it's still SM> too Fidonet-specific. Should PGP incorporate kludges for SM> every other network system in which PGP happens to enjoy SM> widespread use? No, I'm saying there should be a msg-reader hack that would pull out the info. SM> If Fidonet wants to work something out external to PGP, SM> that's fine; but PGP shouldn't be changed in a way that has SM> such tremendous potential for abuse. That's what I meant. SM> Remember, the instant you stick a ^A at the beginning of SM> that line, it becomes fair game for Fidonet mail tossers to SM> yank that line out, modify it, and stick it back in (or SM> not!) anywhere in the message they like, without regard for SM> the order in which that line originally came. Maybe it could be generated as a detached sig, but pasted back into the kludgeline. That way it's physical location wouldn't matter? jason ... Never believe anything until it's been officially denied. 201434369420143436942014343694201434369420143436942014343694718 From: David Chessler Area: Public Key Encryption To: Shawn Mcmahon 2 Oct 94 18:50:00 Subject: Secdev, sfs, etc. UpdReq On 09-29-94 (13:46), Shawn Mcmahon, in a message to All about "SECDEV, SFS, ETC.", stated the following: SM>Is there an OS/2-based counterpart to any of the secure drive programs? >SecDrv, SecDev, SFS, anything? SM>I know there's no OS/2 version of SFS yet, but is there anything along >these lines available other than custom programming jobs from the >consultants? Source to SFS is, I think, available from Peter Gutmann. However, since OS/2 can read and write a DOS (FAT) partition, the only thing you lose is the High Performance File System (HPFS). Thus, SFS should be perfectly usable with OS/2 (the DOS in OS/2 is supposed to be the best DOS, anyhow). ___ __ chessler@trinitydc.edu d_)--/d chessler@cap.gwu.edu * SLMR 2.1b * E-mail: ->132 1:109/459 david.chessler@neteast.com 201434369420143436942014343694201434369420143436942014343694718 From: Carl Hudkins Area: Public Key Encryption To: John Schofield 3 Oct 94 22:27:00 Subject: Source for PGPsort UpdReq 28 Sep 94 10:09, John Schofield wrote to Tim Bradley: TB>> Speaking of PGPSort -- is the source code available? JS> In the version I have, Pascal source is included in the archive. Silly me... it's in my archive, too! Didn't even think to look in there, as source isn't usually included with many programs, and Pascal source doesn't do me much good anyway. :) carl Boca Chica, Florida carl.hudkins@lunatic.com RIME ->1282 PGP: 2D1E1E39 Fido: 1:135/808.1 201434369420143436942014343694201434369420143436942014343694718 From: Christopher Baker Area: Public Key Encryption To: Mike Deaton 3 Oct 94 23:24:14 Subject: keys go in PKEY_DROP Echo [Was: The Public Key of: Mike Deaton]UpdReq -----BEGIN PGP SIGNED MESSAGE----- In a message dated: 01 Oct 94, Mike Deaton was quoted as saying: MD> -----BEGIN PGP PUBLIC KEY BLOCK----- MD> Version: 2.3a MD> -----END PGP PUBLIC KEY BLOCK----- which is where i just saw this so you must have access to that Echo. thanks. TTFN. Chris -----BEGIN PGP SIGNATURE----- Version: 2.61 Comment: PGP 2.6.1 is LEGAL in Zone 1! So USE it! [grin] iQCVAwUBLpDK4csQPBL4miT5AQGN4AQAiASMbaupUDSh8AbdP6pGo3lq5TunHkax TaCa7Qb2Zm7JsNRhimnrWVbHj7Gi7lxFsNam0/SWicyW5jieVivFzx6b00ziW95y QdjvNyGAfMiu2KUn3LCgM07Vu+HFNg8xrONytlQkH9NRdAg8dUzs5yEl18C5ypK1 TjchIk+HweM= =cweS -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718 From: Randy Edwards Area: Public Key Encryption To: All 4 Oct 94 15:47:48 Subject: [1 of 3] ACTION: FBI wiretap bills (SB 2375UpdReq * Original Message Posted via CIVLIB * Date: 03 Oct 94 18:29:06 * From: Randy Edwards @ 1:325/805 * To: All * Forwarded by: Christopher Baker @ 1:374/14 * Message text was not edited! @MSGID: 1:325/805 175be290 ********************************************************************* DISTRIBUTE WIDELY (though no later than October 15, 1994) ********************************************************************* [If you've only got 2 minutes, skip down to the "What You Can Do" section.] Both the House and the Senate Judiciary Committees have reported the bills out of committee. The Senate version was slightly amended to address some issues of cost, but not significantly enough to change the inherently bad nature of the bill. Although there is only a little bit of time left in the session, there is a move afoot to end-run the normal judicial process. Because of the subtlety and speed with which the FBI's Louis Freeh and the bills' sponsors are working, it may already be too late by the time you read this. Waste no time in acting. Backers of the bill are frantically trying to get unanimous approval in the Senate so they won't have to bring the bill before a normal floor debate. This would allow it to be passed quickly and without meaningful debate. This would be akin to a "midnight passage". The FBI has not yet made public their case data explaining why they need this bill. Furthermore, the bill has been rushed through the process so quickly that adequate public debate has not taken place. VTW appreciates the FBI's sense of duty which impels them to urgency in this matter, but we cannot condone the significant impinging of privacy this bill mandates without having the appropriate public debate. Furthermore, the FBI has refused to make public the case data which they claim might prove their case. The public needs to weigh both sides of this. We need to see this data. This is not an issue to be taken lightly. ----------------------------------------------------------------------------- WHAT YOU CAN DO Unless this bill is stopped in the House or Senate, it will become law since President Clinton is certain to sign it. Don't let this bill pass the Senate without adequate debate. Contact your Senators and Representative and ask them to oppose the bill because there has not been adequate public debate. Faxes are best, phone calls are second best; email is probably not the greatest method of contacting them. Congress just doesn't handle email well yet. Step 1. Conclude which state you're in. :-) Find your two Senators on the lists appended. Step 2. Pick up the phone or type up your letter. Step 3. Express your opinion. If you're at a loss for words, use our sample communique below: SAMPLE PHONE CALL The FBI is trying to rush through its wiretap bill (SB 2375 & HR 4922) much too quickly. Without the FBI's case evidence to prove the need for this bill, the public cannot adequately assess the balance between law enforcement needs and the sacrifice of the public's privacy. Please oppose SB 2375/HR 4922. Thank you, ___________________ SAMPLE FAX Dear Honorable _______________, The FBI's Digital Telephony bills (SB 2375/HR 4922) are being rushed through Congress much too quickly. Without the FBI making available the data to support these bills, we the public cannot adequately assess whether or not this bill is an acceptable balance between privacy and law enforcement's need to wiretap. I feel that I have done my part to be fair with the FBI. I have long traded some of my privacy in return for giving them the tools they find useful and expedient in performing their duties. However they need to be fair to me as well, and allow for there to be public debate and their evidence presented, so I can assess whether I agree with this new balance they are asking for. This bill expands the law enforcement's powers. No longer does the FBI have the *right* to attempt wiretapping, but they would (under this bill) have that ability built into every communications system. I urge you to oppose the FBI's Wiretapping bills (SB 2375/HR 4922). Sincerely, ___________________ Step 4. Feel good about yourself. You've just participated in democracy without leaving your seat. Step 5. [Extra special bonus step for activists :-] Before you hang up, ask your legislator's staff member what their position is on SB 2375/HR 4922. It's not an unreasonable question, they were elected to represent people like you. Mail @PATH: 325/805 3615/50 374/1 98 14 201434369420143436942014343694201434369420143436942014343694718 From: Randy Edwards Area: Public Key Encryption To: All 4 Oct 94 15:48:02 Subject: [2 of 3] ACTION: FBI wiretap bills (SB 2375UpdReq * Original Message Posted via CIVLIB * Date: 03 Oct 94 18:29:06 * From: Randy Edwards @ 1:325/805 * To: All * Forwarded by: Christopher Baker @ 1:374/14 * Message text was not edited! @MSGID: 1:325/805 175be291 the answer to vtw@vtw.org. * NOTE * We'll be handing out awards to the legislator who "ducks" this issue the worst this session. Help keep your legislator from receiving this award; pressure them to give you a position today! For more information about the Digital Telephony bills, check the Voters Telecomm Watch gopher site (gopher.panix.com) or contact Steven Cherry, VTW Press Contact at (718) 596-2851 or stc@vtw.org. VTW posts a Digital Telephony FAQ monthly to several Usenet newsgroups including comp.org.cpsr.talk and comp.org.eff.talk. Look for it or contact us at vtw@vtw.org for a copy. Complete list of Senators: p st name phone fax = == ======================== ============== ============== R AK Murkowski, Frank H. 1-202-224-6665 1-202-224-5301 R AK Stevens, Ted 1-202-224-3004 1-202-224-1044 D AL Heflin, Howell T. 1-202-224-4124 1-202-224-3149 D AL Shelby, Richard C. 1-202-224-5744 1-202-224-3416 D AR Bumpers, Dale 1-202-224-4843 1-202-224-6435 D AR Pryor, David 1-202-224-2353 na D AZ DeConcini, Dennis 1-202-224-4521 1-202-224-2302 R AZ McCain, John 1-202-224-2235 na D CA Boxer, Barbara 1-202-224-3553 na D CA Feinstein, Diane 1-202-224-3841 na D CO Campbell, Ben N. 1-202-225-4761 1-202-225-0228 R CO Brown, Henry 1-202-224-5941 na D CT Dodd, Christopher J. 1-202-224-2823 na D CT Lieberman, Joseph I. 1-202-224-4041 1-202-224-9750 D DE Biden Jr., Joseph R. 1-202-224-5042 na Note: Sen. Biden is a co-sponsor of the bill R DE Roth Jr., William V. 1-202-224-2441 1-202-224-2805 D FL Graham, Robert 1-202-224-3041 na R FL Mack, Connie 1-202-224-5274 1-202-224-8022 D GA Nunn, Samuel 1-202-224-3521 1-202-224-0072 R GA Coverdell, Paul 1-202-224-3643 na D HI Akaka, Daniel K. 1-202-224-6361 1-202-224-2126 D HI Inouye, Daniel K. 1-202-224-3934 1-202-224-6747 D IA Harkin, Thomas 1-202-224-3254 1-202-224-7431 R IA Grassley, Charles E. 1-202-224-3744 na R ID Craig, Larry E. 1-202-224-2752 1-202-224-2573 R ID Kempthorne, Dirk 1-202-224-6142 1-202-224-5893 D IL Moseley-Braun, Carol 1-202-224-2854 na D IL Simon, Paul 1-202-224-2152 1-202-224-0868 R IN Coats, Daniel R. 1-202-224-5623 1-202-224-8964 R IN Lugar, Richard G. 1-202-224-4814 na R KS Dole, Robert 1-202-224-6521 1-202-224-8952 R KS Kassebaum, Nancy L. 1-202-224-4774 1-202-224-3514 D KY Ford, Wendell H. 1-202-224-4343 na R KY McConnell, Mitch 1-202-224-2541 1-202-224-2499 D LA Breaux, John B. 1-202-224-4623 na D LA Johnston, J. Bennett 1-202-224-5824 na D MA Kennedy, Edward M. 1-202-224-4543 1-202-224-2417 D MA Kerry, John F. 1-202-224-2742 na D MD Mikulski, Barbara A. 1-202-224-4654 1-202-224-8858 D MD Sarbanes, Paul S. 1-202-224-4524 1-202-224-1651 D ME Mitchell, George J. 1-202-224-5344 na R ME Cohen, William S. 1-202-224-2523 1-202-224-2693 D MI Levin, Carl 1-202-224-6221 na D MI Riegle Jr., Donald 1-202-224-4822 1-202-224-8834 D MN Wellstone, Paul 1-202-224-5641 1-202-224-8438 R MN Durenberger, David 1-202-224-3244 na R MO Bond, Christopher S. 1-202-224-5721 1-202-224-8149 R MO Danforth, John C. 1-202-224-6154 na R MS Cochran, Thad 1-202-224-5054 na R MS Lott, Trent 1-202-224-6253 1-202-224-2262 D MT Baucus, Max 1-202-224-2651 na R MT Burns, Conrad R. 1-202-224-2644 1-202-224-8594 R NC Faircloth, D. M. 1-202-224-3154 1-202-224-7406 R NC Helms, Jesse 1-202-224-6342 na D ND Conrad, Kent 1-202-224-2043 na D ND Dorgan, Byron L. 1-202-225-2611 1-202-225-9436 D NE Exon, J. J. 1-202-224-4224 na D NE Kerrey, Joseph R. 1-202-224-6551 1-202-224-7645 R NH Gregg, Judd 1-202-224-3324 na R NH Smith, Robert 1-202-224-2841 1-202-224-1353 D NJ Bradley, William 1-202-224-3224 1-202-224-8567 D NJ Lautenberg, Frank R. 1-202-224-4744 1-202-224-9707 D NM Bingaman, Jeff 1-202-224-5521 na R NM Domenici, Pete V. 1-202-224-6621 1-202-224-7371 D NV Bryan, Richard H. 1-202-224-6244 na D NV Reid, Harry 1-202-224-3542 1-202-224-7327 @PATH: 325/805 3615/50 374/1 98 14 201434369420143436942014343694201434369420143436942014343694718 From: Randy Edwards Area: Public Key Encryption To: All 4 Oct 94 15:48:14 Subject: [3 of 3] ACTION: FBI wiretap bills (SB 2375UpdReq * Original Message Posted via CIVLIB * Date: 03 Oct 94 18:29:06 * From: Randy Edwards @ 1:325/805 * To: All * Forwarded by: Christopher Baker @ 1:374/14 * Message text was not edited! @MSGID: 1:325/805 175be2cd D NY Moynihan, Daniel P. 1-202-224-4451 1-202-224-9293 R NY D'Amato, Alfonse M. 1-202-224-6542 1-202-224-5871 D OH Glenn, John 1-202-224-3353 na D OH Metzenbaum, Howard 1-202-224-2315 1-202-224-6519 D OK Boren, David L. 1-202-224-4721 na R OK Nickles, Donald 1-202-224-5754 1-202-224-6008 R OR Hatfield, Mark O. 1-202-224-3753 na R OR Packwood, Robert 1-202-224-5244 na D PA Wofford, Harris 1-202-224-6324 1-202-224-4161 R PA Specter, Arlen 1-202-224-4254 na D RI Pell, Claiborne 1-202-224-4642 1-202-224-4680 R RI Chafee, John H. 1-202-224-2921 na D SC Hollings, Ernest F. 1-202-224-6121 na R SC Thurmond, Strom 1-202-224-5972 1-202-224-1300 D SD Daschle, Thomas A. 1-202-224-2321 1-202-224-2047 R SD Pressler, Larry 1-202-224-5842 1-202-224-1630 D TN Mathews, Harlan 1-202-224-1036 1-202-228-3679 D TN Sasser, James 1-202-224-3344 na R TX Hutchison, Kay Bailey 1-202-224-5922 1-202-224-0776 R TX Gramm, Phil 1-202-224-2934 na R UT Bennett, Robert 1-202-224-5444 na R UT Hatch, Orrin G. 1-202-224-5251 1-202-224-6331 D VA Robb, Charles S. 1-202-224-4024 1-202-224-8689 R VA Warner, John W. 1-202-224-2023 1-202-224-6295 D VT Leahy, Patrick J. 1-202-224-4242 na Note: Sen. Leahy is the sponsor of the bill R VT Jeffords, James M. 1-202-224-5141 na D WA Murray, Patty 1-202-224-2621 1-202-224-0238 R WA Gorton, Slade 1-202-224-3441 1-202-224-9393 D WI Feingold, Russell 1-202-224-5323 na D WI Kohl, Herbert H. 1-202-224-5653 na D WV Byrd, Robert C. 1-202-224-3954 1-202-224-4025 D WV Rockefeller, John D. 1-202-224-6472 1-202-224-1689 R WY Simpson, Alan K. 1-202-224-3424 1-202-224-1315 R WY Wallop, Malcolm 1-202-224-6441 1-202-224-3230 ------------------------------------------------------------------------------- STATUS OF THE BILLS Sep 29, 94 HR 4922 marked up and reported out of the Hse. Jud. Comm to the full House (call your Representative) Sep 28, 94 SB 2375 amended, marked up, and reported out of the Sen. Jud. Comm. to the full Senate (call your Senator) Sep 15, 94 HR 4922 hearing held in the Telecommunications Comm. Aug 18, 94 HR 4922 reported back to committee (write to Rep. Jack Brooks!) Aug 11, 94 Sen. Leahy & Rep. Edwards hold a joint hearing on the bills in Wash. DC at 1pm in Rayburn 2237. Aug 10, 94 HR 4922 referred to Subcomm. on Civil and Constitutional Rights Aug 10, 94 SB 2375 referred to Subcomm. on Technology and the Law Aug 9, 94 Rep. Hyde officially cosponsors HR 4922 Aug 9, 94 HR 4922 referred to House Judiciary Committee Aug 9, 94 SB 2375 referred to Senate Judiciary Committee Aug 9, 94 Identical House and Senate bills are announced by their respective sponsors, Rep. Don Edwards (D-CA) and Sen. Patrick Leahy (D-VT) EFF states the legislation is "not necessary". ------------------------------------------------------------------------------- WHAT ARE THE FBI'S WIRETAPPING BILLS? The FBI's Wiretap bills (also known as the DT - Digital Telephony bills) mandate that *all* communications carriers must provide wiretap-ready equipment so that the FBI can more easily implement their court-ordered wiretaps. The costs of re-engineering all communications equipment will be borne by the government, industry and consumers. The bill is vague and the standards defining "wiretap ready" do not exist. Furthermore, the FBI has yet to make a case which demonstrates that they have been unable to implement a single wiretap. Although we as a society have accepted law enforcement's need to perform wiretaps, it is not reasonable to mandate this functionality as a part of the design. In itself, that would be an important balance. However without any proof that this is indeed a realistic and present problem, it is unacceptable and premature to pass this legislation today. The Voters Telecomm Watch (VTW) does not believe the FBI has made a compelling case to justify that all Americans give up their privacy. Furthermore, the VTW does not believe the case has been made to justify spending 500 million Federal dollars over the next 4 years to re-engineer equipment to compromise privacy, interfere with telecommunications privacy, and fulfill an unproven government need. @PATH: 325/805 3615/50 374/1 98 14 201434369420143436942014343694201434369420143436942014343694718 From: Christopher Baker Area: Public Key Encryption To: Charles Senescall 4 Oct 94 15:51:36 Subject: Re: SecureMail Routing Mission statementUpdReq -----BEGIN PGP SIGNED MESSAGE----- In a message dated: 30 Sep 94, Charles Senescall was quoted as saying: CS> > Those engaged in SecureMail Routing are constrained by CS> > the ECPA [Electronic Communication Protection Act] and CS> > FidoNet Policy in their ultimate handling of In-Transit CS> > E-Mail in regard to disclosure. CS> Could this paragraph be amended to the effect that nodes will be CS> constrained by ECPA, where applicable, (say in the US or whatever) CS> and other relevant legislation as may apply from time to time in CS> respect of relevant participating nodes in other jurisdictions? sure could. [Jim? you got that?] CS> Regards.......Charles (FidoNet 3:640/217.111) thanks. when we started it, we didn't have any other considerations. [grin] TTFN. Chris -----BEGIN PGP SIGNATURE----- Version: 2.61 Comment: PGP 2.6.1 is LEGAL in Zone 1! So USE it! [grin] iQCVAwUBLpGyTMsQPBL4miT5AQFz2gQAhNr2DDsUPeZgYIQVo4Vy7A0iAh4QKBgH iiPzK0TuNymfpzQWM797RSn+gRvcbq3t+utE0D3qVPiTAAnRsLM9DGqwaaX08G8z 257BTZLP3UO92BX2xi/iFmkM95TG/r5tABMJVjrJqvoLKO2QVyAjYcIaxQsZ3ga0 fozY2pXoZGo= =zK36 -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718