- cypherpunks-legacy - lists.cpunks.org

CDR design document
by Adam Back 17 Dec '03

17 Dec '03

Here is a proposal for consideration for inclusion in the OpenPGP standard: http://www.dcs.ex.ac.uk/~aba/cdr/ (Also attached text version below [1]) It describes a mechanism for commercial data recovery which attempts to minimise the security risks inherent in allowing disaster recovery of stored encrypted documents. The CDR design also avoids the security risks in building systems which send recovery information over open communications networks, as the CMR proposal currently does. The CDR design offers the option of more ergonomic recovery from forgotten passphrase. CDR allows for more secure use to be made of the existing pgp5.0 key expiry functionality when applied to communications-only keys because they can be deleted with out loss of data-availability, providing a form of PFS which is backwards compatible with pgp5.0 and pgp5.5 clients. Comments? The only change addition to the standard required is to create a distinction between a storage only key and a communications only key. This distinction could be made via the use of an extra flag, ideally so that keyrings can remain standardised and interchangeable between different implementations. The document can also be viewed as a recommendation to implementors of how to avoid security risks (and related government abuse risks) in implementing data recovery systems. I would like to see the OpenPGP standard accomodate both the CMR and CDR design so that each can fly on it's technical merits. (And political merits, cryptography being a highly political field, a politically unpopular design may suffer for other than technical reasons). Adam [1] http://www.dcs.ex.ac.uk/~aba/cdr/ ==============================8<============================== Commercial Data Recovery This document describes a mechanism, Commercial Data Recovery (CDR), to allow companies to recover stored encrypted information as part of a disaster recovery plan. Introduction This document is centered around the OpenPGP standard, and therefore explores first what is possible within the existing standard. Several of the CDR variants presented can be achieved entirely within the pgp5.0 standard without adding any new functionality. Commercial disaster recovery requirement PGP is commonly used for two purposes: file encryption, and encryption of email communications. The situation arises in a commercial setting that individuals are protecting information which the company would like to be able to recover in the event of disaster: in the event of the user forgetting his passphrase, or in the event of the unexpected death of the employee. Stored files which the company may require the ability to recover include encrypted files stored in the files system, on backup tapes, or on floppy disks; and encrypted sent and recieved emails stored in mail client folders. Security vs Availability There is a security risk in adding data recovery mechanisms: the additional risk that recovery procedure is used by other than the owners of the data to recover plaintext. A central goal of the CDR design described in this document is to minimise this security risk. Keys used to encrypt email which is transmitted over the Internet are more valuable to an attacker than keys used to encrypt stored files because of the relative ease with which an attacker can obtain copies of emailed ciphertext. Stored encrypted files in contrast are protected by all the physical security systems the company is relying on to protect it's paper files, plaintext data stored on disks, and backup tapes. For this reason the CDR approach treats communications keys as more sensitive than keys used to encrypt locally stored information. Separate Signature and Encryption Keys added in pgp5.0 This section describes a feature added to PGP with the pgp5.0 release: separate signature and encryption keys. Readers familiar with pgp5.0 functionality may like to skip this section. pgp2.x RSA keys pgp2.x (and pgp1.x) only had direct support for one type of public key: the RSA public key. RSA public keys were used both as signature keys, and as encryption keys to transfer session keys. The ability to generate RSA keys, and to interoperate with pgp2.x is retained in pgp5.x. pgp5.x El Gamal (DH) encryption and DSA signature keys One reason for the introduction of separate key functionalities is the addition, starting with pgp5.0, of the DSA digital signature algorithm which can only function as a signature system. In addition the El Gamal (EG) public key system which was also added with pgp5.0 is used only as a public key encryption system. (There are some El Gamal variants which can be used to produce digital signatures, but these are not used in pgp5.0). (El Gamal is a Diffie-Hellman (DH) variant which is sometimes also referred to confusingly as DH.) The DSA is itself a DH signature variant. Patent issues Another significant reason for the adoption of EG and DSA in particular is the freedom from patent encumbrances these algorithms now enjoy. RSA by contrast is patented, and unpatented algorithms are generally preferred for internet standards. Key expiry feature added in pgp5.0 One general security principle is that keys used to protect communications should be replaced periodically to reduce the value to an attacker of an individual key. Migration path The pgp5.0 standard provides support for this functionality in terms of the ability to attach expiry dates to signature and encryption keys. (In the pgp5.0 and pgp5.5 clients the signature and encryption keys are treated as a pair, and are given the same expiry information, but both the pgp5.0 and pgp5.5 clients can already cope with signature-only keys and encryption-only keys with different expiry information.) Web of Trust In pgp5.0 with the EG public keys, the Web of Trust (WoT) is based on the signature keys only. The users signature key is authenticated in the web of trust. The user signs his own encryption key thereby transferring trust to it. This ensures that encryption keys can be expired and replaced without affecting the web of trust. Limited Perfect Forward Secrecy Perfect Forward Secrecy (PFS) refers the technique of destroying old communications keys to ensure that past traffic can not be compromised after the point of re-keying. One way to use the pgp5.0 key expiry facilities is to have signature and encryption keys with very different expiry periods. For example a signature key could be given no expiry period (the pgp5.0 standard supports expiry periods of `forever'), and encryption keys could be given an expiry period of 6 months. To obtain PFS, a more secure way of dealing with expired encryption keys is to actually irretrievably delete them. This then simulates PFS: an attacker is unable to decrypt traffic encrypted with old communications keys even if he is able to coerce co-operation from the recipient. No one can be coerced because the key has been deleted. It seems reasonable that some users may want to use key expiry for this purpose, and this does not require any modifications to the existing pgp5.0 standard. Key expiry problems for stored encrypted data One problem introduced by key expiry is that any stored data encrypted to the expired key becomes less available. For security reasons the expired key should ideally be deleted, and in this case access to the data is lost. Alternatives are to attempt to store the old keys more securely, this then presents the problem that some stored data is harder to access than other data, and presents additional key management problems for old keys which will be confusing for users. Re-encrypting after key expiry One method to solve this problem is to re-encrypt all of the encrypted files at the point of re-keying. However this method has disadvantages in that not all of the encrypted data may be easily available. Some of the encrypted data may be on backup tapes, on floppy disks, or stored inside `zip' or `tar' archives on the disk and hence may be missed. Separate storage keys The simplest solution to this problem seems to be to encrypt to a separate storage key. Within the pgp5.0 standard this storage key would be a separate El Gamal key with a long expiry date. With this system we then have three types of keys: signature-only keys, communications-only keys and storage-only keys. This could require minimal or even no modifications to the pgp5.0 standard, storage and encryption keys could be differentiated between by: * location storage-only key is stored in (for example a separate keyring) * application being configured to use a chosen encryption key as the storage-only key by giving a keyID * convention on expiry dates (expiry date `forever' could be storage key, other values could be communications keys) * extra flag to indicate a storage-only key Once the separation of key types is made, the security benefits of re-keying can be more fully obtained. Sent and recieved email folders To maintain availability after re-keying of encrypted sent and received emails archived in mail folders, the email plaintext would be encrypted with the storage-only key. This then means that data availability for encrypted files on disk, floppy disk, and backup tape is maintained; and that availability for archived sent and received emails is maintained. Storage Recovery If the system is being used in a commercial setting, disaster recovery can be provided by storing recovery information to allow recovery of the storage-only key. There is still some additional danger over the case where there is no recovery procedure: the risk that an attacker may be able to compromise the recovery information. However because the encrypted data is all protected by the companies existing physical security mechanisms the security risk is minimised. Another form of storage recovery would be to include recovery information with each file, and this would be a valid combination achieved by placing CMR-style requests for additional crypto-recipients on the CDR storage-only key. However this practice makes recovery from forgotten passphrase more problematic: to restore user access to the data after forgotten passphrase, the recovery agent would have to decrypt all stored files (be they on hard disk, backup tape, floppy disk, or stored inside `zip' or other archives), then the user would have to generate a new storage-only key, and re-encrypt all of the files. Given the frequency with which users are prone to forgetting passphrases implementors may decide to avoid this option for ergonomics reasons. CDR vs CMR PGP Inc has an alternative data recovery proposal called Commercial Message Recovery (CMR). The CMR proposal involves sending recovery information with the message in the form of a second crypto recipient. In addition mechanisms are provided in the form of a proposed CMR public key extension to the IETF OpenPGP standard which indicates a request to the sender to include this recovery information. In addition facilities are provided in the form of PGP Inc's SMTP policy enforcer to partially enforce the inclusion of this recovery information by bouncing mail which does not include it. Security comparison PGP Inc's CMR proposal makes re-keying problematic because data is archived in email folders still encrypted to the encryption key. This tends to encourage the practice of having very long term communication encryption keys. Indeed the beta pgp5.0 implementation the author tried makes the recommendation that most users would give keys an expiry period of `forever'. In addition a security risk with the CMR proposal is that an attacker is able to obtain via coercion, bribery or burglary the CMR key used to encrypt the traffic for this key. With a purloined CMR recovery key, and given the long life time encouraged for such keys the previously passive attacker may be able to recover years worth of old traffic. Another risk is that companies may for simplicity have only one CMR key, thereby putting at risk the entire companies secured communications over periods of years. This is naturally a bad practice, and one which is discouraged by PGP Inc also, but the author remains cynically confident that some corporate users will ignore such advice. Privacy Comparison PGP Inc proposese the CMR communications recovery mechanism as a privacy respecting method of achieving data recovery. The privacy features of the CMR proposal are that there are proposed flags which are attached to a public key to indicate statement of intent about plaintext handling to the sender who is about to use the public key. Three statements of intent are possible with the current CMR proposal: * personal key (no flags set) * company use key, company may read message, please encrypt to listed company CMR recovery key(s) (recovery flag set) * company may read message, encrypt to listed CMR recovery key(s) or the message will be bounced (strict recovery flag set) PGP Inc's statement of intent in plaintext handling is a useful concept, in that it explains explicitly to the sender who will be able to read the message, and how the plaintext will be handled. Statement of intents are always advisory, in that they are impossible to enforce; however they are useful in encouraging ethical behaviour in this regard. Statement of intent messages are independent of recovery mechanism, and apply equally to the CDR mechanism described in this document. In fact the author would like to encourage a fuller set of statement of intent flags for both sender and recipient, allowing keys to be marked with intents: * personal key, messages not archived * personal key, messages archived * key used for company business, messages not archived * key used for company business, messages archived * key used for company business, messages archived and recoverable And, in addition a similar privacy argument could be made to allow the sender to express his preferences with regard to plaintext handling on a per message basis. This could generalise the -m function of pgp2.x which instructs the recipient not to save to a file. (The -m flag is the sort of electronic version of `please burn this document after reading', this flag is mildly enforced by the pgp2.x command line application). These set of flags would allow a sender to send a `normal communication message', or a `official statement, please archive with recovery if available', or `sensitive do not archive' and so on. A privacy respecting implementation could provide support for these functionalities. Whilst obviously easy to over-ride, this is felt to be a useful exercise in encouraging respect for privacy. In addition the recipient should have ability where company policy allows to choose which messages to archive, and which to archive with company recovery information. >From a privacy perspective the CDR and CMR proposals are approximately equivalent; the statement of intent flags, and the social value of encouraging companies to respect privacy are useful in both. Government access to communication key politics Another aspect of the whole data recovery area is that the US government, French government, and UK government (as well as other governments) have expressed an unhealthy interest in obtaining private individuals, and companies communications keys. Many privacy advocates view this development with fear, as it seems to many a particularly Orwellian development. Usually the Government Access to Communication Key (GACK) attempts try to deflect criticism by focussing on unrelated issues as a vehicle to introducing GACK: * Terrorist attacks and requirement for emergency government access to communications traffic * Government assistance for companies to recover stored plaintext via key escrow infrastructure. * Assisting electronic commerce by helping put in place Certification Authorities and digital signature laws However readers who have followed GACK politics will recognise the above for what they are: attempts to put in place GACK via indirect routes (respectively: the four horsemen of the infocalypse argument (the fallacy that terrorists will obey laws and use encryption systems which have government backdoors), the Clipper I, II and III attemps (various attempts by the US government to bribe and bully companies into building a GACK architecture), and the UK TTP (Trusted Third Party) proposal where `TTPs' are a euphamism for a Certification Authority (CA) which has been coerced by law to keep individuals private keys). Scenarios governments might shortly try this to request master keys for communications might be France, where the government is changing from a position of no encryption software without license, to a position of unlicensed encryption software being allowed provided that the governments has a back door into the communications. Other examples being perhaps the UK (with it's highly controversial TTP licensing proposals), or the US with the administration and law enforcement community pushing hard for access to communications keys. It is likely, particularly in the UK, and US in the authors opinion, that government backdoors would be demanded in carefully orchestrated stages, designed to minimise public opposition. There might be trials where the traditionally more regulated financial organisations were required to comply, next perhaps government funded research labs, and business organisations accustomed to large amounts of government regulation Only towards the end would people using government funded networks (academics), Internet services providers (ISPs) and individuals be regulated. The final phases may use a terrorist activity, or national emergency, or other scandal as justification for increasing the requirements. It is likely also that the justification will be in terms of wholesome sounding public safety safeguards. Political Comparison PGP Inc's CMR proposal loses heavily in the political argument in the author's opinion because the protocol design supports the practice of allowing third and fourth party access to communications traffic. Particularly with the multiple CMR key requests per key which are rumored to be coming in the next version of PGP, it will be easy technically for a government to request that one of the recovery keys belong to the government. Governments already have the political will to have access to communications; the barriers are technical, and individual's resistance to the notion. The danger with the CMR proposal is that it could become the enabling technology for push button suveillance, the enabling technology for wide scale secret service signals intelligence keyword scanning. This probably not what it's proposers intend, however the danger is there in building the technology. The CDR proposal on the other hand focusses on recovery information of stored information only, and as a design principle avoids sending recovery information over open networks. Whislt governments may be interested to obtain storage keys, they have much less value, because the ciphertext is much harder to obtain. Also non-compliance is much harder to detect: a government law enforcement agency would not know if an individual was actually using storage software with government backdoor key access without physically obtaining the storage media. For most individuals the point at which governments executes a dawn raid is a point at which the individual is already in trouble. The CDR proposal is much closer to the status quo in political terms.

2 2

re: index.html
by Anonymous 17 Dec '03

17 Dec '03

> U.S. SAID VULNERABLE TO COMPUTER ATTACK > > "Today, the right command sent over the Internet to a power > generating station's control computer could be just as effective as > a backpack full of explosives and the perpetrator would be harder to > identify and apprehend," the panel wrote in its executive summary to > the report. "Today, we decided to hook up the computer that controls the power supply of several states to the most hostile WAN in history. OMIGOD, THERE'S AN INSECURE POWER GENERATION CONTROL COMPUTER HOOKED UP TO THE INTERNET! Everyone in the US, $2 please, so we can fix it." > > The report recommends stepping up research and establishing a > nationwide program to educate people on the scope of the problem. It > also recommends revising existing laws to ensure protection against > electronic attacks through the Internet. > This sounds like a bad cyberpunk novel. Two crackers in some hotel room in a hyper-crowded city in Japan, hacking the "power control network". Suddenly, one of them stops and says, "Shit." The other looks up, startled. The first says, "I forgot. This is against the law." A pause. Then they both start rolling around a floor covered with anti- static bags, polystyrene, and fast-food cartons laughing until they turn blue. > > "Law has failed to keep pace with technology. Some laws capable of > promoting assurance are not as clear or effective as they could be," > the panel wrote. > When I hear the "Law has failed to keep pace with technology" mantra, I get the feeling that lawmakers want license to pretend that Moore's Law applies to them, as well. Double the amount of criminal laws and regs every 18-24 months. > "We identified existing laws that could help the government take the > lead and serve as a model of standards and practices for the private > sector," it wrote. "We identified other areas of law that can enable > infrastructure owners and operators to take precautions > proportionate to the threat." "We think we can do what we want with what we already have. Give us the money anyway." Nuke them from orbit. It's the only way to be sure. Golem

1 0

None
by Anonymous 17 Dec '03

17 Dec '03

Everyone has a "right" to speak to the government on any subject whatsoever, which cannot be abrogated by contracts, agreements or willful desire. A populace that holds no secrets is a safe populace. This is why we are officially announcing the formation of a federal agency, the Government Agency of Knowledge. Its role will be to obtain - by whatever means necessary - any and all knowledge of all actions, desires, means and ways of everything transpiring on US soil. Duties will include holding cryptographic keys in escrow, monitoring and assuring the wholesomeness of private and encrypted data traffic, and analyzing all available "knowledge patterns" of US citizens. Since honest, good citizens have nothing to hide, GAK will be a major advance toward protecting American citizenry from crime, terrorism and other human-meditated harm. After all, your government has a right and duty to protect you.

1 0

wanted dead or alive: pgp5.5 key pair
by Adam Back 17 Dec '03

17 Dec '03

Could some kind soul who has downloaded pgp5.5 for business (I think it is available in the US from www.pgp.com) create a key with a CMR key extension. I guess this means generating two keys: XYZ Corp recovery key <snoopy(a)xyz.com> and then: XYZ Corp Sales <sales(a)xyz.com> with the sales person's key set up to have a strict requirement to encrypt to the XYZ "message recovery" key. Could this kind soul then mail me, (or post here I guess would be even more useful) both the private and public keys of both of them. Enciphering minds want to find out how pgp5.0 reacts to this key :-) (The question is really does pgp5.0 encrypt to the CMR key). (btw for the curious as to why my previous message was had a date of 22nd Feb ... I had to set my clock back to get pgp5.0 beta to function as the one I have had expired, and I forgot to set the clock forward again). Adam -- Now officially an EAR violation... Have *you* exported RSA today? --> http://www.dcs.ex.ac.uk/~aba/rsa/ print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",<> )]}\EsMsKsN0[lN*1lK[d2%Sa2/d0<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<J]dsJxp"|dc`

3 2

[Fwd: Horsemen] Horsemen
by TruthMonger 17 Dec '03

17 Dec '03

1 0

Government goons force Goddard to recant
by nobody＠REPLAY.COM 17 Dec '03

17 Dec '03

Time to add a new horseman: "conspiracy theory-spreading libertarians" ... CNN logo [ISMAP]-Navigation Infoseek/Big Yellow Pathfinder/Warner Bros Barnes and Noble Main banner Weird guy. Cool phone. Click here. rule TWA missile theory co-author apologizes Salinger Says report was 'reckless' From Correspondent Christine Negroni November 5, 1997 Web posted at: 2:05 p.m. EST (1905 GMT) NEW YORK (CNN) -- Ian Goddard, co-author of a report that claimed the U.S. Navy shot down TWA Flight 800, has told CNN that those charges were "reckless and a mistake." In a written statement to CNN, Goddard apologized to "all those in the Navy I have wrongfully accused" and to "those who believed in my efforts and who are now upset with me for my change of mind." Goddard co-authored the report with former ABC news reporter Pierre Salinger and a third man, Mike Sommers. Ian Goddard's statement to CNN: "While many witness accounts remain a mystery to me, I believe that my effort to pin the crash of TWA 800 on the Navy was reckless and a mistake. I apologize to all those in the Navy I have wrongfully accused. I also apologize to those who believed in my efforts and who are now upset with me for my change of mind. "We all need to put our support behind the families of the victims of TWA 800. Many who died left children behind who now need your support... Please give." National Transportation Safety Board spokesman Peter Goelz, on learning of the Goddard apology, said that Goddard had done real damage, particularly to the victims' families, by promoting charges that the Navy's "friendly fire" caused the July 1996 crash. "He has caused innumerable people great agony," Goelz said, adding that both the FBI and the NTSB had to spend time responding to what were basically groundless accusations. Joe Lychner of Houston, who lost his wife and two daughters in the crash, told CNN that Goddard and Salinger owe an explanation to the American public. The so-called Salinger report laid out an elaborate conspiracy theory that alleged a huge government cover-up following the TWA crash. Goddard had kept the theory alive on a Web site he created, which now appears to have been discontinued. "I just wanted to give the government a black eye by any means that looked opportune. TWA 800 was just a vehicle for my larger agenda."  Ian Goddard Goddard has recently E-mailed associates about his report. In those messages, Goddard called his support of the conspiracy theory "a big mistake," and said he only pursued the charges because he "wanted to give the government a black eye by any means that looked opportune." Goddard says he wanted to promote libertarian ideology by encouraging distrust of the government. CNN's Christine Negroni reports on the admission: icon 2 min. 30 sec. VXtreme video When contacted by CNN about Goddard's statement, Salinger said that he is moving on from his investigation into the TWA crash, although he did not retract any of his charges that a Navy missile brought down the 747. Salinger called FBI Deputy Director James Kallstrom last week and told him that he was giving up his probe. In his statement to CNN, Goddard asked that the public support the families of the victims of TWA 800 and that donations be made to the Flight 800 Family Relief Fund. TWA Flight 800 crashed off Long Island, killing all 230 people on board. The FBI and NTSB have not yet named an official cause of the accident. ______________________________________________________________ © 1997 Cable News Network, Inc. All Rights Reserved.

1 0

Re: Taxing Churches for their views? Bad idea. (fwd)
by nobody＠REPLAY.COM 17 Dec '03

17 Dec '03

Jim Burnes wrote: > On Wed, 5 Nov 1997, Anonymous wrote: > > Churches, like governments, corporations, or any other organized > > entity, have some wonderful people in them, doing wonderful things. > > The problem, as always, is what our founding fathers realized--these > > types of organizations/structures tend to grow and attain power which > > is then used for the purpose of self-sustained growth (survival). > > Humanity tends to evolve, while organized humanity tends to de-volve. > > Biped humans, walking upright, form organizations which move toward > > becoming quadrapeds dragging large clubs. > Ha! This is pretty interesting. Rather than the typical cypherpunk > approach of eliminating such inefficient and corrupting methods as > income taxation and tax exemption we are playing by their game. Taxation and exemptions are, conceptually, no different than a tribal agreement that those who bring home the deer will share with those who guard the campsite, and that the shaman who keeps the evil spirits at bay has to do neither. When one strips the semantics from various cypherpunks posts, there is usually an underlying agreement that there should be no 'free rides' and no 'oppressive burdens.' <-- generality> > The whole of HG Wells warning to society was that by systematically > altering the language, you alter the things that can be discussed. I believe that half of the disagreements on the cypherpunks list, and the vast majority of disagreements in the world in general, are the result of disputes over semantics, rather than beliefs. > rather than bitch and moan about how the Churches are exempt, why > not rejoice in the fact that at least the churches are free from > taxation. We are part of the way there. Revolutionary idea! Instead of calling for Churches to be subject to the same oppressive taxation as the rest of us, call for the rest of us to be given the same exemptions as Churches. I vote Jim Burnes the honorary title of 'CypherPunks Chief Taxation Spokesperson' (Norman Vincent Peale Chapter). > Or start your own church. ;-) I agree. TruthPastor "CypherPunks Church of One" (All donations declared by myself to be tax deductible--check with the authorities in *your* jail cell (*after* sending me money) as to their views in this regard.)

2 2

PGP 5.5 CMR key examples, mini-review
by Greg Broiles 17 Dec '03

17 Dec '03

An acqaintance of mine received an evaluation copy of the new PGP For Business Security 5.5 suite, and I was able to generate some test keys to play with the message recovery features. I've uploaded them to the cert servers so folks with the 5.0 client software can experiment with them for interoperability, etc. The recovery key is "Little Brother <snoop@localhost>", fingerprint 26A5 667A 97D4 7018 1B18 2B15 D631 4776 B670 E1D0; a test user whose incoming and outgoing mail is forced to include the recovery key is "CMR User <snooped@localhost>, fingerprint EC79 A170 8BAE 60A1 3CAC C517 34A4 6056 EE42 30E3. Both keys are 768-bit DH keys, as I don't expect that anyone will use them for anything other than testing. Installation of the package involves multiple steps - there's an "administrator install package" (my term, not theirs), which installs a version 5.5 of PGP, including the PGPTools, PGPKeys and PGPTray apps, as well as a PGPAdmin program. To implement CMR, the ordinary PGPKeys app is used to create an otherwise ordinary PGP key pair; the administrator then runs the PGPAdmin app, which asks questions about security/recovery policy. The admin can force incoming messages to use a recovery key, can force outgoing messages to use a recovery key, can enable/disable conventional encryption, can enable/disable key generation (and RSA key generation), can force a key to be trusted and to act as a trusted meta-introducer. The admin can also force the user to use a strong passphrase. (PGP 5.5 includes a neat passphrase-strength-meter which changes depending on the length and apparent alphabet-space used in the passphrase for user keys.) Finally, the admin can force the user to sign/trust a designated Corporate Signing Key. After the administrator sets those policy choices, the PGPAdmin tool can be used to generate a customized installer application for distribution to users. That installer creates a local copy of PGP, which will enforce the policy choices made by the administrator. The user is warned upon key generation that a message recovery key will be used (if the app is thus configured) and that the behavior isn't optional. The recovery key ID is displayed but not modifiable. The user interface for 5.5 is much improved over that in 5.0, which was a big improvement over the command line. There's an indicator (initially preferenced to OFF, along with other information) in the PGPKeys application which marks CMR'd keys with a red button; the interface between PGPKeys and the key server is much improved. It's now possible to mark & retrieve many unknown keys, then approve adding them to the local keyring in one step, instead of approving the addition of each additional key. The icons & screen design have been updated and are now more colorful and easier to decipher. When a user with CMR-only client software encrypts data, the ID of the recovery key appears in the "encrypt to" box, and cannot be dragged out. A CMR-client will (apparently) still do conventional encryption with no recovery key if the admin allows this. -- Greg Broiles | US crypto export control policy in a nutshell: gbroiles(a)netbox.com | Export jobs, not crypto. http://www.io.com/~gbroiles | http://www.parrhesia.com

1 0

See the Seasons's Hottest Video Games on VideoGameSpot!
by announce＠lists.zdnet.com 17 Dec '03

17 Dec '03

----------------------------------------------------------------- ZDNET ANNOUNCEMENT 10/22/97 ----------------------------------------------------------------- Video games are going to be on everyone's Christmas list this year, and there are so many hot titles coming out, it'll make your head spin. If you need help finding something for yourself or the right gift for someone special, there is one site that will be your guide to the best games of the season - VideoGameSpot: http://www.zdnet.com/chkpt/zdna971022001/www.videogamespot.com/ VideoGameSpot is the leading video game information site on the Web. With the largest editorial staff in the business, you'll find everything you need to be in the know this holiday season. VideoGameSpot gives you: * Hard-hitting, critical reviews of the latest games played on the Sony PlayStation, Nintendo 64 and Sega Saturn console systems * Previews of games you've been waiting for and other new releases * Hints and strategy guides to help you play better and win * Custom Quick Time trailers so you can see games before you buy them * Monthly contests and promotions with thousands of dollars in prizes given out each month If you like video games (or know someone that does) and want to buy smarter and play better, then click on the URL listed below (or enter it into your browser): http://www.zdnet.com/chkpt/zdna971022002/www.videogamespot.com/ You'll also find us on the Games Channel at ZD Net: http://www.zdnet.com/chkpt/zdna971022003/www.zdnet.com/games _________________________________________________________________ ZDNet Announcements are periodic notices of new features, special events and free offers available to members of ZDNet. --To subscribe to ZDNet Announcements, please send mail to: announce-on(a)lists.zdnet.com You can leave the subject and body blank. --To unsubscribe to ZDNet Announcements, please send mail to: announce-off(a)lists.zdnet.com You can leave the subject and body blank. _________________________________________________________________ Powered by InfoBeat: http://www.infobeat.com

1 0

Re: the migration path (was Re: Your "RIGHT" to Speak to Big Brother)
by Blanc 17 Dec '03

17 Dec '03

Adam Back wrote: >Perhaps this is what they are busy building at their top-sikrit crypto >software development/research center at Cambridge, UK under the >guidance of new head of research cryptographer Roger Needham. >Looks like an export embargo end-run by Bill Gates. > >Maybe Bill Gates is a cypherpunk after all, well we can live in hope, >anyway. ................................................................. He's no anarcho-cypherpunk: he and his father just contributed a great amount of money to support a gun-law initiative which would place all sorts of requirements on gun-owners (mandatory licensing, mandatory training, mandatory gun-locks, and many privacy-intrusive reductions of personal authority, etc.) in Washington state. I don't precisely know where he stands regarding crypto, but I know that he puts business requirements and customer acceptance above the arguments of GAK advocates, as do the VIPs who work in encryption and who totally reject the idea of Big Brother. .. Blanc

1 0