Plessey System 250

Plessey System 250, also known as PP250, was the first operational computer to implement capability-based addressing, to check and balance the computation as a pure Church-Turing Machine. A Church-Turing Machine is a digital computer that encapsulates the symbols in a thread of computation as a chain of protected abstractions by enforcing the dynamic binding laws of Alonzo Church's Lambda Calculus[1] Other Capability Based Computers including CHERI and CAP computer are hybrids. They retain default instructions that can access every word of accessible physical or logical (paged) memory. It is an unavoidable characteristic of the von Neumann Architecture that is founded on shared random access memory and blind trust in the sharing default access rights. For example, every word in every page managed by the virtual memory manager in an operating system using a Memory management unit must be blindly trusted. Using a default privilege among many compiled programs allows corruption to grow without ant method of error detection. However, the range of virtual addresses given to the MMU or the range of physical addresses produced by the MMU is shared undetected corruption flows across the shared memory space from one software function to another. PP250 removed not only virtual memory[1] or any centralized, precompiled operating system but also the superuser, removing all default machine privileges. It is default privileges that empower undetected malware and hacking in a computer. Instead, the pure Object-capability model of PP250 always requires a limited capability key to define the authority to operate. PP250 separated binary data from capability data to protect access rights, simplify the computer and speed garbage collection. The Church-Machine encapsulates and context limits the Turing Machine by enforcing the laws of the Lambda Calculus. The typed digital media is program-controlled by distinctly different machine instructions. Mutable binary data is programmed by 28 RISC instruction set for Imperative programming and Procedural programming the binary data using binary data registers confined to a capability limited memory segment. The immutable Capability Keys, exclusive to six Church-Instructions, navigate the computational context of the Turing Machine through the separately programmed structure of the Object-capability model. PP250 was sold commercially circa 1972.

Immutable Capability Key represent named Lambda Calculus variables. This Church side is a Lambda Calculus Meta-Machine. The other side is an object-oriented machine of binary objects, programmed functions, capability lists defining function abstractions, storage for threads of computation (Lambda Calculus Applications) or storage for the list of Capability Keys in a namespace. The laws of the Lambda Calculus are implemented by the Church-Instructions with micro-programmed access to the reserved (hidden) capability registers. The software is incrementally assembled as object-oriented machine-code linked by the Capability Keys. The structure of function abstractions, including those for memory management, input, and output, scheduling and communication services are protected as private frames in a Thread. Threads computer inline or as parallel computations activated by program controlled Church-Instruction.

Conceptually, the PP250 operates at the dead center of the Church-Turing Thesis as a digitally secure, functional Church-Turing Machine for trusted software. As a real-time controller, PP250 provided fail-safe software applications for computerized telephone and military communication systems with decades of software and hardware reliability. Capability limited addressing detects and recovers from errors on contact without any harmful corruption or information theft. Furthermore, no unfair, default privileges exist for an operating system or a superuser, thereby blocking all hacking and malware. The multiprocessing hardware architecture and the dynamically bound, type limited memory, exclusively accessed through capability limited addressing, replace the statically bound, page based linear compilations with dynamically bound instructions, crosschecked and authorized at run time.

By checking all memory references as an offset within the base, limit, and access types specified bugs, errors and attacks are detected by the type limited capability register. The imperative Turing-Commands must bind to binary data objects as defined by the selected capability register. The access rights of the selected capability register must approve data access rights (Read Binary Data, Write Binary Data or Execute Machine Code). On the other hand, functional Church-Instructions are bound dynamically to a capability key in a capability list held in a capability register with capability access rights (Load Capability Key, Save Capability Key or Enter Capability List). In this way, object-oriented machine code is encapsulated as a function abstraction in private execution space. This PP250 is unlike the stretched von Neumann architecture. Instead, a Lambda Calculus Meta-Machine scales a 'single tape' Turing Machine through a DNA network of 'Enter' capability keys representing functional nodes in a Lambda Calculus namespace

It is a register-oriented architecture, with 8 program accessible data registers and 8 program accessible capability registers. Data registers are 24-bit; capability registers are 48-bit and contain the base address of the segment to which the capability refers, the size of the segment, and the access rights granted by the capability. Capabilities in memory are 24-bit and contain the access rights and an index into the System Capability Table for the segment to which the capability refers; entries in that table contain the segment base address and length for the segment to which the entry refers.[2]

Instructions that access memory have an opcode, a field specifying a data register operand, a field specifying a data register used as an index register containing an offset into a segment, a field specifying a capability register referring to the segment containing the memory location, and a field containing a base offset into the segment. The offset into the segment is the sum of the base offset and the contents of the index register.[2]

The software was modular based on the universal model of computation and the Lambda calculus. Six Church-Instructions hide the details of a named function application using capability keys for the typed concepts of variables, functions, abstractions, applications and a namespace. Instead of binding instructions to static linear memory as a default shared privilege used by malware and hackers, instructions are bound to typed and protected, private digital objects using Capability Keys in a Capability-based security system of immutable mathematical symbols. The resulting Object-Oriented Machine Code achieved many decades of trusted software reliably as mathematically pure, Industrial Strength Computer Science[1].

History

Manufactured by Plessey company plc in the United Kingdom in 1970, it was successfully deployed by the Ministry of Defence for the British Army Ptarmigan project[3] and served in the first Gulf War as a tactical mobile communication network switch.

gollark: Never java.
gollark: Not Java.
gollark: Rust.
gollark: <@!202992030685724675> COMMUNIST.
gollark: Red and black would look a bit bad; try yellow and green.

See also
  • Army Communications and Information Systems (United Kingdom)
  • Flex machine

References
  1. Hamer-Hodges, kenneth (1 January 2020). Civilizing Cyberspace: The Fight for Digital Democracy. p. 256. ISBN 978-1-95-163044-7. Retrieved 25 February 2020.
  2. Henry M. Levy (1984). "The Plessey System 250" (PDF). Capability-Based Computer Systems. Digital Press.
  3. "Ptarmigan project". British Army, Ministry of Defence, UK. Archived from the original on 28 July 2006.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.