- cypherpunks-legacy - lists.cpunks.org

Re: Secrecy: My life as a nym. (Was: nym blown?)
by Hal Finney 17 Dec '03

17 Dec '03

Black Unicorn makes a lot of good points regarding privacy. One thing I wanted to follow up on: > Unfortunately, in the United States most citizens only become interested > in privacy in their 20s or so. By this time it is difficult to overcome > the mass of information which has been stored up. (Pseudocide can be an > attractive option for some perhaps). I have two kids entering their teens, and I'm sure other list members are parents as well. What can we do for our children to help them enter their adult lives with better chances to retain privacy? Unicorn mentions keeping them absent from school on picture day, although I'm not sure how much this helps. I suppose it makes it harder for an investigator to find out what they look(ed) like. Then when they get old enough to drive you have a new problem avoiding the photo (and thumbprint) on the license. Are there other measures which parents could take while their children are young to get them off to a good start, privacy-wise? Hal

9 14

DC Net-politics reporter needed
by Declan McCullagh 17 Dec '03

17 Dec '03

A political publication is looking for an experienced journalist to cover Net-happenings on Capitol Hill, in the White House, and in Federal agencies. Let me know if you're interested and I'll forward your contact info and clips to the right people. -Declan

2 1

Why Cryptography is Harder than it Looks (LONG)
by Bruce Schneier 17 Dec '03

17 Dec '03

WHY CRYPTOGRAPHY IS HARDER THAN IT LOOKS Bruce Schneier, Counterpane Systems ................................................................................ Copyright Nov 1996 by Bruce Schneier. All rights reserved. Permission is given to distribute this essay, providing that it is distributed in its entirety (including this copyright notice). For more information on Counterpane Systems's cryptography and security consulting, see http://www.counterpane.com. ................................................................................ >From e-mail to cellular communications, from secure Web access to digital cash, cryptography is an essential part of today's information systems. Cryptography helps provide accountability, fairness, accuracy, and confidentiality. It can prevent fraud in electronic commerce and assure the validity of financial transactions. It can prove your identity or protect your anonymity. It can keep vandals from altering your Web page and prevent industrial competitors from reading your confidential documents. And in the future, as commerce and communications continue to move to computer networks, cryptography will become more and more vital. But the cryptography now on the market doesn't provide the level of security it advertises. Most systems are not designed and implemented in concert with cryptographers, but by engineers who thought of cryptography as just another component. It's not. You can't make systems secure by tacking on cryptography as an afterthought. You have to know what you are doing every step of the way, from conception through installation. Billions of dollars are spent on computer security, and most of it is wasted on insecure products. After all, weak cryptography looks the same on the shelf as strong cryptography. Two e-mail encryption products may have almost the same user interface, yet one is secure while the other permits eavesdropping. A comparison chart may suggest that two programs have similar features, although one has gaping security holes that the other doesn't. An experienced cryptographer can tell the difference. So can a thief. Present-day computer security is a house of cards; it may stand for now, but it can't last. Many insecure products have not yet been broken because they are still in their infancy. But when these products are widely used, they will become tempting targets for criminals. The press will publicize the attacks, undermining public confidence in these systems. Ultimately, products will win or lose in the marketplace depending on the strength of their security. THREATS TO COMPUTER SYSTEMS Every form of commerce ever invented has been subject to fraud, from rigged scales in a farmers' market to counterfeit currency to phony invoices. Electronic commerce schemes will also face fraud, through forgery, misrepresentation, denial of service, and cheating. In fact, computerization makes the risks even greater, by allowing attacks that are impossible against non-automated systems. A thief can make a living skimming a penny from every Visa cardholder. You can't walk the streets wearing a mask of someone else's face, but in the digital world it is easy to impersonate others. Only strong cryptography can protect against these attacks. Privacy violations are another threat. Some attacks on privacy are targeted: a member of the press tries to read a public figure's e-mail, or a company tries to intercept a competitor's communications. Others are broad data-harvesting attacks, searching a sea of data for interesting information: a list of rich widows, AZT users, or people who view a particular Web page. Electronic vandalism is an increasingly serious problem. Computer vandals have already graffitied the CIA's web page, mail-bombed Internet providers, and canceled thousands of newsgroup messages. And of course, vandals and thieves routinely break into networked computer systems. When security safeguards aren't adequate, trespassers run little risk of getting caught. Attackers don't follow rules; they cheat. They can attack a system using techniques the designers never thought of. Art thieves have burgled homes by cutting through the walls with a chain saw. Home security systems, no matter how expensive and sophisticated, won't stand a chance against this attack. Computer thieves come through the walls too. They steal technical data, bribe insiders, modify software, and collude. They take advantage of technologies newer than the system, and even invent new mathematics to attack the system with. The odds favor the attacker. Bad guys have more to gain by examining a system than good guys. Defenders have to protect against every possible vulnerability, but an attacker only has to find one security flaw to compromise the whole system. WHAT CRYPTOGRAPHY CAN AND CAN'T DO No one can guarantee 100% security. But we can work toward 100% risk acceptance. Fraud exists in current commerce systems: cash can be counterfeited, checks altered, credit card numbers stolen. Yet these systems are still successful because the benefits and conveniences outweigh the losses. Privacy systems -- wall safes, door locks, curtains -- are not perfect, but they're often good enough. A good cryptographic system strikes a balance between what is possible and what is acceptable. Strong cryptography can withstand targeted attacks up to a point -- the point at which it becomes easier to get the information some other way. A computer encryption program, no matter how good, will not prevent an attacker from going through someone's garbage. But it can prevent data-harvesting attacks absolutely; no attacker can go through enough trash to find every AZT user in the country. And it can protect communications against non-invasive attacks: it's one thing to tap a phone line from the safety of the telephone central office, but quite another to break into someone's house to install a bug. The good news about cryptography is that we already have the algorithms and protocols we need to secure our systems. The bad news is that that was the easy part; implementing the protocols successfully requires considerable expertise. The areas of security that interact with people -- key management, human/computer interface security, access control -- often defy analysis. And the disciplines of public-key infrastructure, software security, computer security, network security, and tamper-resistant hardware design are very poorly understood. Companies often get the easy part wrong, and implement insecure algorithms and protocols. But even so, practical cryptography is rarely broken through the mathematics; other parts of systems are much easier to break. The best protocol ever invented can fall to an easy attack if no one pays attention to the more complex and subtle implementation issues. Netscape's security fell to a bug in the random-number generator. Flaws can be anywhere: the threat model, the system design, the software or hardware implementation, the system management. Security is a chain, and a single weak link can break the entire system. Fatal bugs may be far removed from the security portion of the software; a design decision that has nothing to do with security can nonetheless create a security flaw. Once you find a security flaw, you can fix it. But finding the flaws in a product can be incredibly difficult. Security is different from any other design requirement, because functionality does not equal quality. If a word processor prints successfully, you know that the print function works. Security is different; just because a safe recognizes the correct combination does not mean that its contents are secure from a safecracker. No amount of general beta testing will reveal a security flaw, and there's no test possible that can prove the absence of flaws. THREAT MODELS A good design starts with a threat model: what the system is designed to protect, from whom, and for how long. The threat model must take the entire system into account -- not just the data to be protected, but the people who will use the system and how they will use it. What motivates the attackers? Must attacks be prevented, or can they just be detected? If the worst happens and one of the fundamental security assumptions of a system is broken, what kind of disaster recovery is possible? The answers to these questions can't be standardized; they're different for every system. Too often, designers don't take the time to build accurate threat models or analyze the real risks. Threat models allow both product designers and consumers to determine what security measures they need. Does it makes sense to encrypt your hard drive if you don't put your files in a safe? How can someone inside the company defraud the commerce system? How much would it cost to defeat the tamper-resistance on the smart card? You can't design a secure system unless you understand what it has to be secure against. SYSTEM DESIGN Design work is the mainstay of the science of cryptography, and it is very specialized. Cryptography blends several areas of mathematics: number theory, complexity theory, information theory, probability theory, abstract algebra, and formal analysis, among others. Few can do the science properly, and a little knowledge is a dangerous thing: inexperienced cryptographers almost always design flawed systems. Good cryptographers know that nothing substitutes for extensive peer review and years of analysis. Quality systems use published and well-understood algorithms and protocols; using unpublished or unproven elements in a design is risky at best. Cryptographic system design is also an art. A designer must strike a balance between security and accessibility, anonymity and accountability, privacy and availability. Science alone cannot prove security; only experience, and the intuition born of experience, can help the cryptographer design secure systems and find flaws in existing designs. IMPLEMENTATION There is an enormous difference between a mathematical algorithm and its concrete implementation in hardware or software. Cryptographic system designs are fragile. Just because a protocol is logically secure doesn't mean it will stay secure when a designer starts defining message structures and passing bits around. Close isn't close enough; these systems must be implemented exactly, perfectly, or they will fail. A poorly-designed user interface can make a hard-drive encryption program completely insecure. A false reliance on tamper-resistant hardware can render an electronic commerce system all but useless. Since these mistakes aren't apparent in testing, they end up in finished products. Many flaws in implementation cannot be studied in the scientific literature because they are not technically interesting. That's why they crop up in product after product. Under pressure from budgets and deadlines, implementers use bad random-number generators, don't check properly for error conditions, and leave secret information in swap files. The only way to learn how to prevent these flaws is to make and break systems, again and again. CRYPTOGRAPHY FOR PEOPLE In the end, many security systems are broken by the people who use them. Most fraud against commerce systems is perpetrated by insiders. Honest users cause problems because they usually don't care about security. They want simplicity, convenience, and compatibility with existing (insecure) systems. They choose bad passwords, write them down, give friends and relatives their private keys, leave computers logged in, and so on. It's hard to sell door locks to people who don't want to be bothered with keys. A well-designed system must take people into account. Often the hardest part of cryptography is getting people to use it. It's hard to convince consumers that their financial privacy is important when they are willing to leave a detailed purchase record in exchange for one thousandth of a free trip to Hawaii. It's hard to build a system that provides strong authentication on top of systems that can be penetrated by knowing someone's mother's maiden name. Security is routinely bypassed by store clerks, senior executives, and anyone else who just needs to get the job done. Only when cryptography is designed with careful consideration of users' needs and then smoothly integrated, can it protect their systems, resources, and data. THE STATE OF SECURITY Right now, users have no good way of comparing secure systems. Computer magazines compare security products by listing their features, not by evaluating their security. Marketing literature makes claims that are just not true; a competing product that is more secure and more expensive will only fare worse in the market. People rely on the government to look out for their safety and security in areas where they lack the knowledge to make evaluations -- food packaging, aviation, medicine. But for cryptography, the U.S. government is doing just the opposite. When an airplane crashes, there are inquiries, analyses, and reports. Information is widely disseminated, and everyone learns from the failure. You can read a complete record of airline accidents from the beginning of commercial aviation. When a bank's electronic commerce system is breached and defrauded, it's usually covered up. If it does make the newspapers, details are omitted. No one analyzes the attack; no one learns from the mistake. The bank tries to patch things in secret, hoping that the public won't lose confidence in a system that deserves no confidence. In the long run, secrecy paves the way for more serious breaches. Laws are no substitute for engineering. The U.S. cellular phone industry has lobbied for protective laws, instead of spending the money to fix what should have been designed corectly the first time. It's no longer good enough to install security patches in response to attacks. Computer systems move too quickly; a security flaw can be described on the Internet and exploited by thousands. Today's systems must anticipate future attacks. Any comprehensive system -- whether for authenticated communications, secure data storage, or electronic commerce -- is likely to remain in use for five years or more. It must be able to withstand the future: smarter attackers, more computational power, and greater incentives to subvert a widespread system. There won't be time to upgrade them in the field. History has taught us: never underestimate the amount of money, time, and effort someone will expend to thwart a security system. It's always better to assume the worst. Assume your adversaries are better than they are. Assume science and technology will soon be able to do things they cannot yet. Give yourself a margin for error. Give yourself more security than you need today. When the unexpected happens, you'll be glad you did. ****************************************************************************** Bruce Schneier schneier(a)counterpane.com http://www.counterpane.com ******************************************************************************

2 1

Re: WebTV a "munition"
by Pablo Calamera 17 Dec '03

17 Dec '03

>>Date: Fri, 08 Nov 1996 17:16:00 -0800 >>From: Tom Weinstein <tomw(a)netscape.com> >>Organization: Netscape Communications, Inc. >>MIME-Version: 1.0 >>To: cypherpunks(a)toad.com >>Subject: Re: WebTV a "munition" >>Sender: owner-cypherpunks(a)toad.com >>Precedence: bulk >> >>Rich Graves wrote: >>> >>> Eric Murray wrote: >>> > >>> > Page 3 of the San Jose Mercury News has a small blurb >>> > about WebTV's browser/set-top box that "uses >>> > computer-security technology so powerful that the >>> > government is classifying it as a weapon >>> > that will require a special export license before >>> > it can be sold overseas".[...] >>> > shouldn't be too difficult. If they didn't use the "export" >>> > level SSL CipherTypes, then what're they up to? Are they >>> > fighting crypto export laws (for which they should be congratulated >>> > and supported) or are they just looking for free publicity? >>> >>> Based on the lack of public policy pronouncements from the WebTV >>> folks, I would answer C) They're clueless. I'm not sure that >>> management even understood, or wanted to understand, that they'd have >>> an export problem. >>> See http://www.webtv.net/ >> >>Since Pablo Calamera works there, they can't be too clueless. >> >>-- >>You should only break rules of style if you can | Tom Weinstein >>coherently explain what you gain by so doing. | tomw(a)netscape.com >> To clarify a bit, we're not talking about SSL here. Also, some how it was infered by some readers of the article that we were astonished about the munitions classification of our product. We were not. Oh... and yes, we are not the least bit clueless (thanks Tom). Below is a company statement we released: The WebTV Network is currently using a 128 bit encryption system that gives our U.S. subscribers the most sophisticated security protection of any online service today. It is our intent to offer our customers the most secure environment for transactions and transmission with their WebTV Network service. Our units, sold by Sony and Philips, include a sticker that states that the product is not to be exported outside of the United States. However, the government restriction does not prevent us from exporting our product outside of the United States. WebTV Networks has always intended to announce its expansion plans in early 1997, providing global communication using either 40 bits, now authorized by the government, or 56 bits which Bill Clinton recently endorsed. Pablo ----------------------------------------- | Pablo Calamera | Security Architect | WebTV Networks, Inc. http://webtv.net/ | 305 Lytton Avenue | Palo Alto, CA 94301 | . . . . . . . . . . . . . . . . . . . . | mailto:pablo@corp.webtv.net | voice:(415) 614-2749 -----------------------------------------

2 1

Re: another possible remailer attack
by anonymous＠miron.vip.best.com 17 Dec '03

17 Dec '03

Steve Reid writes: > > >> You want to know if Dimitri is the person regularly posting these > >> messages. So, you use your powers as ISP to block his access to all > >> remailers. If the public messages suddenly stop then you can be > >> reasonably certain that Dimitri was sending them. > > I'm not following something...just how to your "powers as ISP" affect a > > remailer in, say, Holland, or one for that matter on another ISP? (As a > > Packet filtering at the ISP's router. If Dimitri can't connect to a > remailer, he can't send anonymous messages. Sure there are a lot of hacks > that could be done (like have sendmail on another system send it to a > remailer) but such things could be detected and blocked by clever filters. I disagree, it's easy to bounce mail through ANY Internet-connected host running sendmail and thence to a remailer. In fact this mail was sent that way, I bounced it through sun.com before hitting a remailer. > In fact, the ISP could just claim to be "going down for maintenance" and > completely block Dimitri from the internet for a while. Only if the Backbone Cabal (there is no Cabal) is re-formed (and given special SuperPowers!) with the sole purpose of blocking Dimitri from posting to cypherpunks. > > Just as the Nazis could isolate spy transmitters by selectively > > turning off electricity to different neigborhoods, so, too, can various > > Isolating spy transmitters by selectively cutting power is exactly > alalogous to what I have suggested. The spy transmitters couldn't bounce their transmissions off of regular radio transmissions, could they? Buck Satan

2 1

FY 1997 classified programs list now available.
by ratak 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit To: dc-stuff(a)dis.org Date: Mon Nov 11 19:16:08 1996 People! I got this message today, and the web site : http://www.frogi.org/classified-programs.html It has all the details, take a close look at what the U.S Goverment has been up to in regards to there classified programs branchs... God damn do they ever spend money...! All research done by:: Paul McGinnis / PaulMcG(a)aol.com http://www.frogi.org/secrecy.html [military secrecy site] - -----Begin Included Message ----- Date: Mon, 11 Nov 1996 18:44:14 -0500 From: PaulMcG(a)aol.com To: skunk-works(a)mail.orst.edu, area51(a)lists.best.com Cc: I have posted my new, extensive list of classified military programs (and the references I used to find them) in the FY 1997 budget at: http://www.frogi.org/classified-programs.html (NOTE: requires a Web browser with table support) There are some shocking revelations such as 31% of the Air Force's research and development budget is being spent on programs whose purpose -and- cost is classified. Doesn't anyone believe in public accountability for taxpayer money? ___________________________________________________________________ GarGoyle Securities - -Intrusion Assessment Systems - -Security Consultation/Education/Curriculum Development - -Project Management/Research/Analysis World Wide... - -Member of CITDC (Canadian International Trade Development Council) - -Email: ratak(a)GargSec.mb.ca (Jason E.J. Manaigre) - -Web: www.GargSec.mb.ca - -Email for PGP key with phrase 'Get Public Key' as Subject ___________________________________________________________________ -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBMofP4PqtmO8M92GRAQGrKQgAtmH+2O5k8AODrjR1qvBoR6Q37AqWJ6Rg OOF0OeugKHr1rppeJDYhYCHyBXQ5m+ktrpecpPKBDqfSbHFnjrMI9jmXUcs5KTPz JjV5C3EssD4TIj7/EcOwgV4qWt18I2T4D612nj3yQ3S68D+brUNCthrJpsEfKFKX yAnizzUOtnBLeosnUkz4FDF5lM5MgadU7/kCmO8k/g9NrZHfIj8PMifDVx4bLeCl E+MdXoSqZnY47+RECL7vFOEIlBTfjBRjf2C/QGWBc1W6feBgL5R1OlZBHv2hIZLZ 72DcDzt8pjhbebqIU0AM4mLmNwmQT2qh3p47VopVjHaIr2/uHg4+2w== =OR7L -----END PGP SIGNATURE-----

1 0

Re: RSA and me...
by stewarts＠ix.netcom.com 17 Dec '03

17 Dec '03

>On Sun, 10 Nov 1996, Gemini Thunder wrote: >> 'Lo. >> Is the "RSA in 3 lines of Perl" a munition (under ITAR)? >> What if I got it as a tatoo? Lucky replied >Somebody did this. Check the RSA in perl homepage. Furthermore, you'd be wasting pain, time, and money. Perl5 makes it possible to do RSA in two lines of Perl :-) And that'd leave room on your arm for the 3-line RC4! If you want to leave the country with it, you might need to register as an, um, international arms dealer... # Thanks; Bill # Bill Stewart, +1-415-442-2215 stewarts(a)ix.netcom.com # You can get PGP outside the US at ftp.ox.ac.uk

1 0

Re: How many people killed by there own governments (Was: Re: a retort + a comment + a question = [RANT])
by jim bell 17 Dec '03

17 Dec '03

At 06:27 PM 11/11/96 -0500, Joseph M. Reagle Jr. wrote: >>With regard to b), governments--primarily through the use of >>their militaries--have killed, by some counts 170,000,000, men, >>women and children in this century alone. Hardly the guardians >>of freedom, in my opinion. > > Do you have a breakdown of that number? I'm working on one of my thought >experiments and am looking for the appropriate stats: > > >o THUGS V. GOVS > (during times of "modern" govts. 1800+) > >Deaths by Govts. on "own people" > > US Civil War x M > US Native Americans > Hitler: Jews 6 M > Hitler: Others 6 M > Stalin: 30 M > China: Cult Rev x M > France: Rev x M Don't forget that the likely cause of the 1917 world-wide influenza pandemic was probably caused or greatly increased in seriousness by the WWI movement of soldiers, and the conditions at the front. Had there been no war, there might still have been a very localized outbreak, but it would have been much less serious. The estimate of 170 million seems a bit high, but not by much. Jim Bell jimbell(a)pacifier.com

1 0

Re: Why is cryptoanarchy irreversible?
by Sean Roach 17 Dec '03

17 Dec '03

>At 12:58 AM 11/8/1996, stewarts(a)ix.netcom.com wrote: >> Strong vs. weak crypto isn't the real issue - for most business use, >> weak crypto is obviously unacceptable, but strong crypto with GAK >> is ok as long as it doesn't interfere with use (and as long as the >> government bureaucrats don't sell too many keys.) To which, at 09:02 AM 11/8/96 -0800, Peter Hendrickson wrote: >We often say that the government is a security weak point and that >this makes GAK impractical. However, this is not true. If the >holders of the government keys were individually responsible for >their release, they would not be released very often. That is, >in order to use cryptography you must purchase an expensive >encryption license. That pays the salary of a certified "key >escrow agent" who is the only person who can decrypt your messages. >What stops him from revealing your keys to unauthorized parties? >It's his business. If that's not enough, you back it up with >criminal penalties for disclosure. And, hiring this person is >no different from hiring an employee for your company. > >There are already similar activities. Lawyers are nominally employees >of the state. Employees of Swiss banks can go to jail for violating >their secrecy laws. Then there is the meat-packing inspectors, I don't know if this should give piece of mind or instill new fear. The inspectors were put in there because the meat was rancid, the thing is, some of it still is if you listen to the critics. A partial fix at least. >At 12:58 AM 11/8/1996, stewarts(a)ix.netcom.com wrote: >> The government might be able to stop new Netscape versions from >> using strong crypto - threatening to confiscate the company's >> ill-gotten gains from aiding and abetting money launderers might help, >> and threatening to confiscate PCs that use unapproved crypto. >> But it's tough to use a widespread threat like that on popular >> software once it's out there. To which, at 09:02 AM 11/8/96 -0800, Peter Hendrickson wrote: >I agree, if the software is popular. But, if the fears of the GAKers >and the dreams of certain cypherpunks are real, such software will >not be popular. Another point is, if the government attacks Netscape for their strong crypto(which is pretty hard to get, I'm in Oklahoma and I couldn't get it because some server didn't know for sure that my server was in the United States or Canada), someone will probabally make an in-line plug-in for encrypted data, and this plug-in may affect more of the browser than the existing system, making it more dangerous to the governments schemes. Anyone know where the data is stored on how to write for Netscape?

2 1

Re: Why is cryptoanarchy irreversible?
by Sean Roach 17 Dec '03

17 Dec '03

At 09:02 AM 11/8/96 -0800, Peter Hendrickson wrote: >At 12:29 AM 11/8/1996, Jim McCoy wrote: >>Peter Hendrickson writes: >>[...] >>>> Get a warrant, search my system, find nothing but a bunch of applications >>>> and a collection of risque (but definitely legal) pictures which I exchange >>>> with a few friends. You may suspect that when the images are concatenated >>>> in a particular way the low-order bits form a stego filesystem but no one >>>> will be able to prove it in court. > >>> Are you concatenating these images by hand? If so, the level of entropy >>> is probably low enough to recover the information through brute force >>> methods or you are hiding a very small amount of information. > >> I hide the relatively small amount of data within a very large amount of >> data which makes it impossible to find. Data from analog sources, like >> the "real world" (images, sounds, etc) is noisy. This is a fact of life. >> Because this data is noisy I can hide information in the noise. As long >> as the information I am hiding maintains the same statistical properties >> of noise it is impossible to pull the information out of the data file unless >> you have the key. If I am paranoid enough I can make this key impossible >> to discover without a breakthrough in factoring. > >Where will you keep your secret key? Remember, when they go through your >house they bring 20 young graduates from MIT who are just dying to show >how clever they are and save the world at the same time. > >> This is the essence of steganography and the nature of signal and noise are >> fundemental principles of information theory. > >The concept of noise is not all that well defined, however. There is no >way to look at a signal and say "this is all noise." Sometimes physical >theories may lead you to believe that it is all noise. That is fine >for many applications, but when becomes less convinced of things if >the consequences are severe. > >>> If you are not doing it by hand, you own terrorist software and will pay >>> the price. > >> Ah yes, terrorist programs like cat and perl and operating systems like >> Linux which contain a loopback filesystem that I can hook a perl >> interpreter into at compile-time (which is enough for me to rewrite the >> program from scratch each time if necessary, unless things like math >> libraries are also outlawed on computers :) I think that the crypto >> concentration camps are going to be very crowded places. > >Can you elaborate on this? I am curious to know exactly what you are going >to keep in your head and what goes on the disk. Please post the Perl >code that you would type in from scratch every time. (Most of the message left for clarity) I would type dungeon at the prompt and Ctrl-Alt-6 at the first door. But that's just me. BTW. The hypothetical Steno program (Trojan Horse) that I wrote about earlier (and that this refers) could have its own source hidden in the opening screen of both the game and the bmp that I would use for my windows background. If anyone has access to the source of a soon to be released game, they could add this to it as an easter egg, thus, the author would be spreading a very powerful tool which would be advertized several months after it was released. If it were added to a program with references to cypherpunks or similar, it might even reach the (primary) target audience.

2 1