From: Alan Pugh Area: Public Key Encryption To: Shawn McMahon 5 Feb 95 10:00:50 Subject: inquiry UpdReq -=> Shawn McMahon was saying something about inquiry SM> Despite the stern warnings of the tribal elders, Alan Pugh said this SM> to DONALD ROSE: AP> i like to send random messages across the internet with zero content AP> to give the spooks in the nsa something to do. SM> Our custom is to give innocuous messages, even trivial ones like "gee, SM> Mr. G-Man, you decrypted this! I feel safer already!" subject lines SM> like "cocaine shipment schedules" or "that package for Saddam" or "the SM> crow flies by moonlight." SM> If both sides were running the proper software, I'd encrypt my AREAFIX SM> messages. :-) neat idea. i also like sending copies of the 1st ten amendments to the us constitution, (otherwise known as the bill of rights), as well as the declaration of independance and whole constitution. i figure they need to read these documents occasionally. one could also put a _real_ message buried somewhere within the text. the spook would see the beginning of, say, the constitution and say "oh, that rag again" and delete it. amp <0003701548@mcimail.com> February 5, 1995 10:0 ... Were you standing at the shallow end of the gene pool? 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Christopher Baker 5 Feb 95 19:15:00 Subject: Re: PassPhrase UpdReq -----BEGIN PGP SIGNED MESSAGE----- CB>> JB> comment=" YOUR COMMENT HERE " CB>> JB> The comment must be in quotes, and I'm not sure of the specifics CB>> quotes are not required unless you want quote marks to appear in your CB>> comment. Yes and no... I suppose we should BOTH double check ourselves before posting so-called "expert" information. The quotes aren't necessary unless you want to "right justify" your comment like I do. Without them, the leading spaces are ignored and the comment is justified one space to the right of the "Comment:" string. The quote marks do not show in the appended quote though... 'least not with my copy. :) -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: -=[ Privacy Through Random Acts Of Encryption ]=- iQCVAwUBLzVqBOkStfMM4BMZAQEESgP/RL8zm9782XzJHqtZvFwfcd+u0MdLlFHh O1agdEeFtIvPDdjW1JRnV36gqurSdUvYV1s+T4ZPBwcKQulvij2j4TJQpRCxxFZX 6EFcFMOfIIjs9WN6SKUo47YxRiJ+7KeemPBO25Fn2nOMV2kNsXCj6RHH1oWaeZZz 5zlOBfAa0s4= =K+09 -----END PGP SIGNATURE----- jbloss@meadville.com -=- 1:2601/551.0 -=- ->5317 PGP v2.6.2 public encryption key available by request. 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Jim Bell 5 Feb 95 19:10:00 Subject: Pgp news UpdReq -----BEGIN PGP SIGNED MESSAGE----- JB>> everything to happen to you and everybody else, hoping the bad wolves JB>> will leave you alone and go away. And mostly they do, although JB>> occasionally they eat one of your flock. Bummer. And occasionally one of the "flock" does something to provoke the wolves... like wandering ignorantly into the wolves' territory thinking he's invincible. He may even get away with it, but a fellow flock member may eaten by the spiteful wolf when he follows the silly sheep back to the pasture... even if the wolf AIN'T all that hungry. A sheep just caused the demise of a flock member... all the while claiming he's trying to support and defend the dead sheep. :(( Bummer... You wanna write nasty letters?? Go for it... But don't expect your fellow flock members to respect you, or think you're a "man". Don't even expect them to admit you're one of the hypothetical flock. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: -=[ Privacy Through Random Acts Of Encryption ]=- iQCVAwUBLzVovOkStfMM4BMZAQHePQP6AkVIkiqPBObxpfihnKo0LbAq9CGOL4Vy wEKJUzE9LICBvSz+14EhCvwOt8JRNnr1jcaXx/cYv+7mXOaLyoWwEGixvQ8N794F qSnO+DNTS7DxRLiQc3hQfLAVGeAtA3PlC2xb55UWDMlY1P5RdWXsLLY4KMZ24yx+ ECp3Atrzjbg= =FPj2 -----END PGP SIGNATURE----- jbloss@meadville.com -=- 1:2601/551.0 -=- ->5317 PGP v2.6.2 public encryption key available by request. 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Christopher Baker 5 Feb 95 15:25:00 Subject: Re: PassPhrase UpdReq -----BEGIN PGP MESSAGE----- Version: 2.6.2 Comment: -=[ Privacy Through Random Acts Of Encryption ]=- owEBqQBW/4kAlQMFAC81NC7pErXzDOATGQEBTocD/1B+aJHd7ics3mSPPHADes46 arfvlzpE+P4hCTh0qlmhR6LKy+V2xpedqZwg8uV2AGOqwfzB8gPb2ONdppsgCQ+p LG6a8Xw1p4y0SHlvgmyyduvvcDEJ9NUiUofjT6PfWZRTEDj+UwMPAnpv3XN5HTws i89lfJxrqXqmWAiyYLo+rA9iCXJlcGx5Lm1zZwAAAAA= =qVL7 -----END PGP MESSAGE----- 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Christopher Baker 5 Feb 95 15:28:00 Subject: Re: PassPhrase UpdReq -----BEGIN PGP SIGNED MESSAGE----- JB> The comment must be in quotes, and I'm not sure of the specifics of quotes are not required unless you want quote marks to appear in your comment. Yes and no. :) I have mine in quotes and they don't show in the added comment. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: -=[ Privacy Through Random Acts Of Encryption ]=- iQCVAwUBLzU06ukStfMM4BMZAQFKwAP/Zc7siCnG4aB6zhJ3RFgTxXkX/54UuUAe itOpUg4nUn4hXxAhvsEKAlCZEb4j+H2ksPaP/OssAOONJWh9vP3s8oSuUAU0C5sM zDwkZiLoLqu0d5zD+vOn9xaV7NLEEi0rKe0rrbHtqS449Q9kDLfeVCiyZnyAOtAu ZAP4Vm/SWe0= =pnWN -----END PGP SIGNATURE----- jbloss@meadville.com -=- 1:2601/551.0 -=- ->5317 PGP v2.6.2 public encryption key available by request. 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Christopher Baker 5 Feb 95 15:35:00 Subject: Re: PassPhrase UpdReq -----BEGIN PGP SIGNED MESSAGE----- JB> comment=" YOUR COMMENT HERE " JB> The comment must be in quotes, and I'm not sure of the specifics of quotes are not required unless you want quote marks to appear in your comment. Yes and no... we should BOTH double check ourselves before posting so-called "expert" information. The quotes aren't necessary unless you want to "right justify" your comment like I do. Without them, the leading spaces are ignored and the comment is justified one space to the right of the "Comment:" string. The quote marks do not show in the appended quote though... -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: -=[ Privacy Through Random Acts Of Encryption ]=- iQCVAwUBLzU2eekStfMM4BMZAQFnMwP9GVa3t343gcbzX4tZSAhhr1VjNPCWI/uY NXfVKSKPtUrLfVMnBTArO2vTnSoTxX4mGKbOwdwFKhvlXZTJmdSaYuN/id14sT2c 839g9D6VjSMB4HkhDEp5L84lIToULNgPUnYec/Orqv8I/l+siMwvLH7n0OVgJshF SUwNWIRZFXI= =0AJU -----END PGP SIGNATURE----- jbloss@meadville.com -=- 1:2601/551.0 -=- ->5317 PGP v2.6.2 public encryption key available by request. 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Christopher Baker 5 Feb 95 15:39:00 Subject: Re: PassPhrase UpdReq -----BEGIN PGP SIGNED MESSAGE----- CB>> JB> comment=" YOUR COMMENT HERE " CB>> JB> The comment must be in quotes, and I'm not sure of the specifics CB>> quotes are not required unless you want quote marks to appear in your CB>> comment. Yes and no... we should BOTH double check ourselves before posting so-called "expert" information. The quotes aren't necessary unless you want to "right justify" your comment like I do. Without them, the leading spaces are ignored and the comment is justified one space to the right of the "Comment:" string. The quote marks do not show in the appended quote though... -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: -=[ Privacy Through Random Acts Of Encryption ]=- iQCVAwUBLzU3WukStfMM4BMZAQE1TAP/ZO051ZqgEX2eYc+bTwQqe5p0OoOrNmtY ppk8qHqutvLCeBFyDdlHo3W+I9sQKvJKwkAxCAuAyZ/trONRlj5oMfRUW87SWkmU KqkDY0PBuTgETVgPuHqehJBMT0YbxGua7cVpaacrIbHkkTbWw7kdRBcPUTwWQeJm ShpFKmVIScM= =LFCn -----END PGP SIGNATURE----- jbloss@meadville.com -=- 1:2601/551.0 -=- ->5317 PGP v2.6.2 public encryption key available by request. 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Jim Bell 5 Feb 95 15:58:00 Subject: Pgp news UpdReq -----BEGIN PGP SIGNED MESSAGE----- JB>> DC> going to pay any attention to you. But if his mailbox fills up with JB>> DC> nastygrams or worse, he may take it out on Phil just to spite you. JB>> Then maybe we'll just have to return the favor! Nobody needs help from a wannabe toughguy... JB>> everything to happen to you and everybody else, hoping the bad wolves JB>> will leave you alone and go away. And mostly they do, although JB>> occasionally they eat one of your flock. Bummer. And occasionally one of the "flock" does something to provoke the wolves... like wandering ignorantly into the wolves' territory thinking he's invincible. He may even get away with it, but a fellow flock member may eaten by the spiteful when he follows the silly sheep back to the pasture... even if the wolf AIN'T all that hungry. :( An arrogant sheep just caused the demise of a flock member... all the while claiming he's trying to support and defend the dead sheep. :(( Bummer... You wanna write nasty letters?? Go for it... But don't expect your fellow flock members to respect you, or think you're a "man". Don't even expect them to admit you're one of the hypothetical flock. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: -=[ Privacy Through Random Acts Of Encryption ]=- iQCVAwUBLzU78OkStfMM4BMZAQE4/wP/YbNNtrI9PvK7/XoCdV4TV0wcEqAQfY8K hXPlXn1RGPpGlHSLuhFmG8m5JdxIqgpUVx3hHDIzn5Lff6CgzcfsoDcOWNlxiQgr 1HzYwACDnsRvD216SNkRuzOFaTnH9KGH3wpomHczaLLl9+d2yGsdHggw8Vaa7jIH I7FFBFWyz2E= =wW7K -----END PGP SIGNATURE----- jbloss@meadville.com -=- 1:2601/551.0 -=- ->5317 PGP v2.6.2 public encryption key available by request. 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Jim Bell 5 Feb 95 19:08:00 Subject: Pgp news UpdReq JB>> everything to happen to you and everybody else, hoping the bad wolves JB>> will leave you alone and go away. And mostly they do, although JB>> occasionally they eat one of your flock. Bummer. And occasionally one of the "flock" does something to provoke the wolves... like wandering ignorantly into the wolves' territory thinking he's invincible. He may even get away with it, but a fellow flock member may eaten by the spiteful wolf when he follows the silly sheep back to the pasture... even if the wolf AIN'T all that hungry. A sheep just caused the demise of a flock member... all the while claiming he's trying to support and defend the dead sheep. :(( Bummer... You wanna write nasty letters?? Go for it... But don't expect your fellow flock members to respect you, or think you're a "man". Don't even expect them to admit you're one of the hypothetical flock. 201434369420143436942014343694201434369420143436942014343694718 From: Jeffrey Bloss Area: Public Key Encryption To: Christopher Baker 5 Feb 95 19:13:00 Subject: Re: PassPhrase UpdReq CB>> JB> comment=" YOUR COMMENT HERE " CB>> JB> The comment must be in quotes, and I'm not sure of the specifics CB>> quotes are not required unless you want quote marks to appear in your CB>> comment. Yes and no... I suppose we should BOTH double check ourselves before posting so-called "expert" information. The quotes aren't necessary unless you want to "right justify" your comment like I do. Without them, the leading spaces are ignored and the comment is justified one space to the right of the "Comment:" string. The quote marks do not show in the appended quote though... 'least not with my copy. :) 201434369420143436942014343694201434369420143436942014343694718 From: Gordon Campbell Area: Public Key Encryption To: Mark Drew 7 Feb 95 10:47:30 Subject: Edit Trust UpdReq -----BEGIN PGP SIGNED MESSAGE----- On (05 Feb 95) Mark Drew wrote to All... MD> The DOCs say to execute 'PGP -ke useid ' but that asks for MD> the userid's pass phase as if they were were going to edit their own That's thr correct command, you're just using it incorrectly. Let's say you have my key on your ring and you've decided that you _do_ know that it's my key and I'm trustworthy. You enter 'PGP -ke campbell' (you only need to enter the keyring name if you have more than one). Follow the prompts and you're done. MD> public/secure key (which I have done for myself). PGP -h gives the MD> exact same command line for both editing key name and/or pass MD> phase and trust level. How can this be, and if so, what am I MD> missing here? By any chance does the person whose key you want to edit have the same last name as you? When you -ke your own key, the program thinks you want to either change your passphrase or add a userid to your key. Cheers, .....G -----BEGIN PGP SIGNATURE----- Version: 2.6.i Comment: Help! Help! The paranoids are after me! iQCVAwUBLzeXF4omCDt60qk9AQHLuQP/VUnMqzSh2d8o3BSvSMOjJgR2G5aZAtxc kFn8FfYyBSzpew+R1+qMTth/UlIqTRCODwQBipBdqYYkabl+GomLMdkDqKwEtxO3 hUo7VCNRy1h4ptQPwOmvm3gLogZzL4UzzpVjAW/LdOL7DSNKwmO6gB/sWUp5dqmd QZqphv2a0ko= =zSnJ -----END PGP SIGNATURE----- ... Key fingerprint = FD E8 27 CA 15 6C 4A 4F 09 1E B5 B0 7B 09 6E 50 201434369420143436942014343694201434369420143436942014343694718 From: Christopher Baker Area: Public Key Encryption To: Armando Ortiz 7 Feb 95 20:10:46 Subject: unauthorized info gathering instead? [Was: Unauthorized Entry]UpdReq -----BEGIN PGP SIGNED MESSAGE----- In a message dated: 23 Jan 95, Armando Ortiz was quoted as saying: AO> UNAUTHORIZED ENTRY, A NEW PGP-SHELL FOR WINDOWS V3.1 or WIN32s! AO> Unauthorized Entry will be the next generation of shells! AO> Scheduled for release by the end of the year, we at SDT hope that is this a vaporware announcement? the end of what year? AO> Currently under development, the BETA release of UE-PGP v1.0 will AO> be out soon, how soon? thru what channels? AO> however, we are going to send the B-Release to only those who send AO> mail with the following information, and keep in mind, only 25 will AO> be selected from a pool of those who want to apply: so you will have only 25 people testing the 'next generation of shells'? doesn't seem like much of test bed. AO> o - Your FULL NAME (F, M, & L) okay. why the middle? rarely does anyone use the middle in e-mail. AO> o - Your mailing address AO> (Sorry, no P.O. Boxes accepted, please include City, AO> State, Zip, and if any, Apartment #'s) why is that? AO> o - Your home phone number (Car phones or pagers not accepted) where will this info be kept? AO> o - Your birthday what has that got to do with it? how will you verify it? AO> o - Current job description AO> o - Internet mail address AO> o - Your public key AO> o - How long you've been using PGP with or without an AO> interface sounds normal. AO> If you feel that you would like to try out for beta testing this AO> software, please send the above information to the following AO> Internet address only: dyvs79a@prodigy.com sort of an audition? AO> Sorry, only residents that have lived in the Continental United AO> States for 21 consecutive years or more, including Alaska and AO> Hawaii, may apply. Those living in Canada and Mexico may not AO> participate. why is that? AO> Beta testers will be chosen on July 4, 1995. pardon any skepticism. [grin] TTFN. Chris -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP 2.6.2 is LEGAL in Zone 1! So USE it! [grin] iQCVAwUBLzgaGssQPBL4miT5AQFFSQP/S7D9X4gPEoKnmdvs4efxgENYmhhcvTXk kOcIB3YFJN7zG5cvKNi4UvzYtpdS1xR4OJS+erF5ClscOUp4wEsUdEDE0PMEO1M7 YHc6BOX6XioY0il5pds5gMpXDpMLwlUc8qlp4PMkHK4XRK7/L8RItRMpM9/COB6W e16yZKqEQXM= =qHwg -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718 From: Christopher Baker Area: Public Key Encryption To: Alan Pugh 7 Feb 95 20:12:28 Subject: Re: Re: Can I Freq Pgp? UpdReq -----BEGIN PGP SIGNED MESSAGE----- In a message dated: 03 Feb 95, Alan Pugh was quoted as saying: AP> i still post there, but more and more am tending to abandoning its AP> echo. i get better info elsewhere these days. i got both of your sends on the list. thanks. the ASCII list is now available here as PGPFIND [FINDPGP.LST] for freq or download. TTFN. Chris -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP 2.6.2 is LEGAL in Zone 1! So USE it! [grin] iQCVAwUBLzgagcsQPBL4miT5AQGc/gP/aTa/bWOYzQiD+Ua5zmYGX5HRCiM+w5wj eGJRjidz5chMJYpsyb2esq7QALIUI7UJEecimyD+a9F3NLrhxG9w+5oGRCZIiU+9 gYsv2nCVEEDXB773LTA4edTSxn0RWnXChdPM3ei2TcDj21IiMs8Hti/46rHkxL/o 7VO5DEa1qeE= =Dfw4 -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718 From: DAVID BROOKS Area: Public Key Encryption To: Jerome Greene 2 Feb 95 02:42:00 Subject: Re: PassPhrase UpdReq -----BEGIN PGP SIGNED MESSAGE----- Thus spake Jerome Greene on the subject of Re: PassPhrase: JG> DB> So tell me, how did you get the comment added to your sig? JG>It's in the CHANGES.DOC of the original archive. Here's what it JG>says: If the line JG> comment= JG>appears in the config file, the line "Comment: " appears in JG>ASCII armor output. Of course, you can also use this from the JG>command line, e.g. to include a filename in the ASCII armor, do JG>"pgp -eat +comment=filename filename recipient". Well, somehow I missed that. Thanks for cluing me in! -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Welcome, ball fans, to the World Series of Darkness. iQEVAwUBLzB8lvKizMjmJn6JAQFalgf/WyIf2mrngSXqDqV1BxcFSIEEpQVu+nkO 4lRBQsRM0PFDotaWr1hQb/v2rGsyXyTA4gdtr+U5k/5kAC5u+LyHxnDZYD+7UWZ8 4Wy59htoD7S1sn0+PEpoIrkrShjpnBXB6qB2Vb2qNnGxOFsr7yMOf6LJ8PyC5obq F3fIBJVaIka4ZyjxrXj+L+6nSzjf6acsjOqcEitDPROoP6/7vxwhDKv/wtu3pL+H QYmRWLw4a80PTNSTLuv9T+ITrvmZOFjAw1/N635WE68WJtUzYV3sFVcO38uE1Cza f7JGgzfSj0g9yMpb7ZC4bTjkR/X1MpKJBBdeOvhyd836J1L904aM9Q== =7SPq -----END PGP SIGNATURE----- David J Brooks <\ /> ( . . ) Have you hugged a coyote today? {^} U ___ CMPQwk #1.42-18 UNREGISTERED EVALUATION COPY 201434369420143436942014343694201434369420143436942014343694718 From: Nolan Lee Area: Public Key Encryption To: Richard Dale 8 Feb 95 07:59:28 Subject: Unauthorized Entry UpdReq On Feb 07 12:06 95, Richard Dale of 1:280/333@fidonet.org wrote: AO>>* o - Your FULL NAME (F, M, & L) AO>>* o - Your mailing address AO>>* (Sorry, no P.O. Boxes accepted, please include AO>>City, * State, Zip, and if any, Apartment #'s) AO>>* o - Your home phone number (Car phones or pagers not AO>>accepted) * o - Your birthday AO>>* o - Current job description AO>>* o - Internet mail address AO>>* o - Your public key AO>>* o - How long you've been using PGP with or without an AO>>interface RD> Sounds interesting, but what does some of this stuff have RD> to do with the price of beans in China? I use a PO Box, RD> period. This may put me out of the running, but that's the RD> way it is. Sounds a wee bit fishy to me. Could be spies for the gov't trying to compile statistics. :-) I've beta tested a lot of software and never had to answer any *any* of those questions, other than a voice phone number. later, Nolan 201434369420143436942014343694201434369420143436942014343694718 From: jason carr Area: Public Key Encryption To: David McIntyre 8 Feb 95 19:06:34 Subject: Re: PGP and BWave UpdReq -----BEGIN PGP SIGNED MESSAGE----- David McIntyre wrote in a message to Bruce Davis: DM> messages. So I just use EZ-PGP. But for another odd DM> reason, QEdit loses its cursor if I just go from Blue Wave DM> to the editor, so I use PGPBlue to edit the message. Go DM> figger. :) I suspect there's more than one QEDIT.CFG floating around with different cursor definitions. Maybe one in the dir where QEDIT itself is, and another in the PATH, or in the BW/PGP dirs... jason ... Avoid clichs like the Plague. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP_ECHO: CypherEcho to the gods... iQCVAwUBLzmHlkjhGzlN9lCZAQERMQP/b7/gJirmLElqC33gDTUdBWE1vwIlE6iy xaHj3M28FZPIQD6g3nh/J0bKj31OoTTsB8vEI+ahKE/wcPl/8ojloPGA173Xpc/z 8sRzW0ohqfSBzodNwgYRSSQ02vi29GZaMECOMw+62NUQ8+Ke01Boq8ooDcbyfxrQ x4KUjsi0djA= =XcvL -----END PGP SIGNATURE----- ... Key fingerprint = 60 97 B2 AE 7D 90 11 2F 05 1C 35 98 E9 B9 83 61 201434369420143436942014343694201434369420143436942014343694718 From: Glen Todd Area: Public Key Encryption To: William Hattenhauer 8 Feb 95 18:57:18 Subject: PGP Forever!!! UpdReq -----BEGIN PGP SIGNED MESSAGE----- Bright the day, William! Monday February 06 1995 16:22, William Hattenhauer wrote to Glen Todd: WH> Nice comment on my original outrage burst! Thanks. Nice to know one's efforts are appreciated. Next time, how about quoting, though.{g} I had to dig back quite a ways in my message base to find what you were referring to. Wind to thy wings, Glen ... You did WHAT in my name?!? -Jesus - --- GoldED/386 2.50.B1016+ Gamma -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Joe McCarthy would have loved the Clipper chip. iQEVAwUBLzl3HUsDfAvy+TXBAQHNtQf9E2kaXwureHutdLDZpul968f6ejeXvmMd B0mIruz8ELtlsO+7XcvM+29RCyGCk9KWoQB58Jx0vuHSBVL8FBevqVC2erB4Unb9 WyQR6m0ioAq3BKrc2KCuPk93iN4Kz1qF/Du6EmmptL5SBLlEnmZmyw2I1ukanwH7 leVI1LeXQ756eNtUzj1P3r9sw3m/NE0eME2AgqM+Q6vfI5V5CiiNx5+tmhCceozg +gnbdsyeSkHTXOr60dlWij2svKuBlI5ki5I9P0M6FVICedhVEpm34YPRqxfg3vx/ gEdVa1iZUysXc/qSycx1zf+Jt5LDNuygyZ9KhUfGdDXwqrxjxrE9sQ== =cLKK -----END PGP SIGNATURE----- 201434369420143436942014343694201434369420143436942014343694718 From: David Chessler Area: Public Key Encryption To: Jim Bell 6 Feb 95 09:31:00 Subject: Quotes as passphrase UpdReq On 02-02-95 (14:29), Jim Bell, in a message to David Chessler about "QUOTES AS PASSPHRASE", stated the following: JB>I think that these days, it would be almost impossible to recover >once-overwritten data. (Even using "analog" techniques.) That's >because disk-drive progress has been defined by dramatically increasing >the data storage capacity, and one of the main things you do to >accomplish this is to increase the data rate. JB>Due to the physical limitations of the heads, this means that you must >design the read-system to be more tolerant of "sloppy" signals. This is >certainly do-able, of course, but it means that it'll be that much >harder to distinguish between the renants old data and various >limitations of the system. Some of the authors of secure erasing utilities make similar claims. However, no one seems to know for sure. You may take the risk you prefer. However, if you are relying on technical difficulty, what is difficult now may be easy in a few years--and that might still embarrass you. JB>But the "problem" (for the snoops, at least) is that the moment disk >drive manufacturers start using PRML, they take advantage of its >superior characteristics and increase by 30-40% the number of bits (and, >thus, data rate) that can be put on the track. One way of looking at >this would be to say that in development, they "red-line" the drive to >see just how much faster the data rate can be set before it fails, and >then when it does they back off the rate somewhat and put the drive into >mass production. JB>The result is a read-data stream which is as close as practicable to an >unreadable set of data, but not quite getting there! You can well >imagine that if even the most recently written data is so close to the >limit, getting back previously-recorded data would be damn near >hopeless. And the point is, in 2 or 3 or 4 years, when the next technique is used, with yet narrower heads, and yet more sophisticated algorithms, your data is again readible. Moreover, and this is an important moreover, there are statistical techniques to analyse signals (which is what your disk-read amounts to) which are far slower than would be practical for any disk controller you would put in a practical computer, but which are far more powerful. Thus, the use of some simple statistical analysis for ordinary disk reads does not preclude more complex analysis making possible disk reads when the data is actually garbled. JB>Another problem for the snoops is that there are so many different >types hard-disk drives sold, it would be almost impossible for any >organization (like the NSA or CIA) to justify the kind of investment >needed to engineer a straightforward ability to recover old data from Funny, the disk recovery services seem able to keep up. >each of them, except on a case-by-case basis. Floppies would probably >be a different story, I suppose. This is putting your trust in obscurity. There are fewer types of disk being sold than you think, at the mechanical level, and you may be sure that any police agency that wants to read your disk will get all the support it requires from the manufacturer. Most of the differences are in encoding schemes, in the electronics. The requirements of the agency are for very narrow read heads, which are subject to partial stepping, and for software which will enable it to analyse and decode the bit stream it recovers. This is a trivial decryption task, since they are trying to read the plain text, and it might not be worth the agency's time to try to obtain specs it doesn't have and then code them into its disk controllers (which are probably software controlled). Instead, the agency may just run a general decryption program and recover the data in minutes or a few hours. But, as I said, the disk recovery companies have no problem keeping up with all the disks out there, so there's no reason the FBI or NSA can't as well. -- ___ __ david.chessler@neteast.com d_)--/d chessler@capaccess.org chessler@trinitydc.edu * SLMR 2.1b * E-mail: ->132 1:109/459 david.chessler@neteast.com 201434369420143436942014343694201434369420143436942014343694718 From: David Chessler Area: Public Key Encryption To: Jim Bell 7 Feb 95 00:26:00 Subject: Pgp news UpdReq On 02-02-95 (09:03), Jim Bell, in a message to David Chessler about "PGP NEWS", stated the following: JB> DC> It's still a dumb idea. Nothing like mailbombing literally or > DC> figuratively a prosecutor to get him really pissed off. And then >he ^^^^ > DC> can prosecute even if he thinks he doesn't have a case. JB>"then"? What do you mean, "then"? JB>He can do this _already_. And he will, if he thinks he can get away >with it. But he won't think he can get away with it if he is aware he's >been located and a substantial fraction of the population are pissed of >at what he's doing. Bull. Sheer, unadulterated Bull! Right now he will prosecute only if he thinks he has a case, or if the case is so political that he or his superiors think there is an advantage to doing so, even if it is likely to result in a loss (which would be a damaging precedent). However, you get him pissed, and he'll go after Zimmermann anyhow, *and* he'll go after *you*. Threatening a prosecutor or judge is a felony. Have you ever wondered why drug dealers threaten and kill witnesses, but never threaten and kill judges and prosecutors and cops in this country? Because it is *very*, ***very*** dangerous! JB>In Zimmermans's case, I don't think "being a lawyer" changes anything. >Even lawyers who have no reason to be biased one way or another are >mystified as to what justification the prosecutor could use to harass >Phil, let alone proceed with the case. Ummmmm. That's not true. They're blazing new ground, expanding the reach of ITAR, but they don't quite know what to make of the net. The case is novel, but that does not mean it is weak. JB> DC> So the prosecutor isn't > DC> going to pay any attention to you. But if his mailbox fills up >with > DC> nastygrams or worse, he may take it out on Phil just to spite you. JB>Then maybe we'll just have to return the favor! CRAP. Just think about why this doesn't happen. JB>See, being a "sheeple" is so "comfortable", isn't it?!? You just allow >everything to happen to you and everybody else, hoping the bad wolves >will leave you alone and go away. And mostly they do, although >occasionally they eat one of your flock. Bummer. Look, you don't really have the resources to threaten the prosecutor and you know it. None of us do. But you send nastygrams or worse, and the prosecutor has the means to go against you for some very serious offenses. The Mafia does not go against the prosecutors. The Columbian drug dealers in NY will wipe out the whole family of someone who crosses them, but they won't touch a prosecutor. You are being romantic, but silly. And if you did do what you recommend, it is certain that things would go much worse for Zimmermann--and for you. -- ___ __ david.chessler@neteast.com d_)--/d chessler@capaccess.org chessler@trinitydc.edu * SLMR 2.1b * E-mail: ->132 1:109/459 david.chessler@neteast.com 201434369420143436942014343694201434369420143436942014343694718