G reat-Grandma, my history teacher mentioned computers today. What were they?” So asked Ancath. “Yes, I remember them. They were among us when I was a child. My own grandfather was among the original inventors. They were everywhere and calculated everything. They were part of life. The biggest invention of all was called The Internet. It connected all computers in our homes, our towns, our cities, and even our colonies on Moon, Mars, and Europa.” “But Great-Grandma, what happened to it all?” “It was a sad story. From the beginning, the inventors dreamed of building computers that would be like people—thinking, reasoning, understanding. They predicted they would achieve such artificial intelligence by 2030, when they expected to be able to build computers the size and power of a brain. Yet, no matter how hard they tried, it seemed that every computer did really stupid things, making mistakes that injured people, confused their identities, or put them out of business. In their endless quest for an artificial intelligence, the inventors started with simple things for everyday business and personal life: automated chauffeurs, pilots, radar cops, toll collectors, voice menus, receptionists, call directors, reservation agents, help technicians, and complaint specialists; but these computers were invariably uncompassionate, insensitive, and error-prone. At first they thought the problem was a lack of computing power and an insufficient experience database. But by 2025, they had more computing power than any brain and more data than could be stored in a brain; that did not help. Believing that the problem was too few computers connected, the inventors offered their talents to the U.S. Government, which in 2025 announced its intention to fully automate. They automated entire bureaucratic departments, replacing staffs of thousands with a single computer that did the same job. When the first chip containing the algorithms of government came off the production line, tongue-in-cheek politicians announced it as an historic breakthrough in the long quest to shrink government. They hailed it as an important step toward efficiency and cost-saving. Hundreds of thousands of Federal workers were laid off in 2030 when the automated government system came on.” “That sounds pretty incredible, Great-Grandma!” said Ancath. “But what happened to it?” “As it turned out, they had created not artificial intelligence, but artificial stupidity. Soon the automated DEA started closing down pharmaceutical companies saying they were dealing drugs. The automated FTC closed down the Hormel Meat Company, saying it was purveying spam. The automated DOJ shipped Microsoft 500,000 pinstriped pants and jackets, saying it was filing suits. The automated Army replaced all its troops with a single robot, saying it had achieved the Army of One. The automated Navy, in a cost-saving move, placed its largest-ever order for submarines with Subway Sandwiches. The FCC issued an order for all communications to be wireless, causing thousands of AT&T installer robots to pull cables from overhead poles and underground conduits. “Within 10 years, the automated Federal Government had made so many mistakes, bankrupted so many businesses, and messed up so many lives that a great economic depression came upon the world. People everywhere were out of work; pollution, crime, homelessness, and hardship ran rampant. “Finally, in 2050 a group of graybeard programmers—who remembered enough about the programming of the automated Government system—created a solution. They built an Automated Citizen, which they trained to be helpless and adoring of authorities, and they installed one on every Internet port. Soon the automated government was completely occupied with taking care of automated citizens; and it left all the people alone. With the Government out of their lives, people forged a new, free society, enabling us to celebrate this lovely Christmas here today.” “Oh Great-Grandma, that is so wonderful! What a great story and happy ending! I love you!” ... ABOT1: I think I’m finally getting the hang of programming inter-citizen interactions. What do you think? ABOT2: It is stupid.
The distribution of keys in a computer network using single key or public key encryption is discussed. We consider the possibility that communication keys may be compromised, and show that key distribution protocols with timestamps prevent replays of compromised keys. The timestamps have the additional benefit of replacing a two-step handshake.
A method for implementing secure personal computing in a network with one or more central facilities is proposed. The method employs a public-key encryption device and hardware keys. Each user is responsible for his own security and need not rely on the security of the central facility or the communication links. A user can safely store confidential files in the central facility or transmit confidential data to other users on the network.
ertification mechanism for verifying the secure flow of information through a program. Because it exploits the properties of a lattice structure among security classes, the procedure is sufficiently simple that it can easily be included in the analysis phase of most existing compilers. Appropriate semantics are presented and proved correct. An important application is the confinement problem: The mechanism can prove that a program cannot cause supposedly nonconfidential results to depend on confidential input data.
This paper investigates mechanisms that guarantee secure information flow in a computer system. These mechanisms are examined within a mathematical framework suitable for formulating the requirements of secure information flow among security classes. The central component of the model is a lattice structure derived from the security classes and justified by the semantics of information flow. The lattice properties permit concise formulations of the security requirements of different existing systems and facilitate the construction of mechanisms that enforce security. The model provides a unifying view of all systems that restrict information flow, enables a classification of them according to security objectives, and suggests some new approaches. It also leads to the construction of automatic program certification mechanisms for verifying the secure flow of information through a program.