Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Plessey System 250
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{tone|date=January 2025}} '''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. [[Plessey]] built the systems for a [[British Army]] message routing project. ==Description== 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]]<ref name="Civilizing Cyberspace: The Fight for Digital Democracy">{{cite book |last1=Hamer-Hodges |first1=kenneth |title=Civilizing Cyberspace: The Fight for Digital Democracy |date=1 January 2020 |isbn=978-1-95-163044-7 |page=256 |url=http://amazon.com/author/kennethhamerhodges |accessdate=25 February 2020 |ref=ccthffdd}}</ref> Other capability based computers, which include [https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/ CHERI] and [[CAP computer]]s, are hybrids. They retain default instructions that can access every word of accessible physical or logical (paged) memory.<ref name="The Fate of AI Society: Civilizing Superhuman Cyberspace">{{cite book |last1=Hamer-Hodges |first1=Kenneth |url=https://www.amazon.com/Fate-Society-Civilizing-Superhuman-Cyberspace/dp/1964148545/ref=sr_1_1?crid=2E5O7RE5LBW6R&dib=eyJ2IjoiMSJ9.7k9k9UXr0HjNOprcAA30MAkS4yPTYqlHKASLedFKngs.EtrJeOrXEQAksTU_dAFZeyDXbcLOUbPzmf1-CGBFYTs&dib_tag=se&keywords=The+Fate+of+AI+Society%3A+Civilizing+Superhuman+Cyberspace&qid=1727394100&s=books&sprefix=the+fate+of+ai+society+civilizing+superhuman+cyberspace%2Cstripbooks%2C753&sr=1-1 |title=The Fate of AI Society: Civilizing Superhuman Cyberspace |date=August 27, 2024 |publisher=Studio of Books LLC |isbn=978-1964148540 |edition=2nd |page=170 |ref= |accessdate=}}</ref> It is an unavoidable characteristic of the [[von Neumann architecture]]{{cn|date=February 2020}} that is founded on shared random access memory and 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]] (MMU) must be trusted.{{cn|date=February 2020}} Using a default privilege among many compiled programs allows corruption to grow without any 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.{{cn|date=February 2020}} PP250 removed not only [[virtual memory]]<ref name="Civilizing Cyberspace: The Fight for Digital Democracy" /> 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 (computer science)|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 instruction]]s. 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 a Turing machine through the separately programmed structure of the [[object-capability model]]. Immutable capability keys 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 as a digitally secure, functional Church–Turing Machine for trusted software. As a [[real-time computing|real-time]] [[controller (control theory)|controller]], the 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. It is a [[processor register|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.<ref name="levy-chap4">{{cite book|author=Henry M. Levy|url=https://homes.cs.washington.edu/~levy/capabook/|title=Capability-Based Computer Systems|date=1984|publisher=Digital Press|chapter=The Plessey System 250|chapter-url=http://www.cs.washington.edu/homes/levy/capabook/Chapter4.pdf}}</ref> 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.<ref name="levy-chap4"/> 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 result achieved many decades of trusted software reliability.<ref name="Civilizing Cyberspace: The Fight for Digital Democracy" /> ==History== Manufactured by [[Plessey|Plessey company plc]] in the [[United Kingdom]] in 1970, it was successfully deployed by the [[Ministry of Defence (United Kingdom)|Ministry of Defence]] for the [[Army Communications and Information Systems (United Kingdom)#Ptarmigan | British Army Ptarmigan project]]<ref>{{cite web|url=http://www.army.mod.uk/royalsignals/equipment/digital.html|title=Ptarmigan project|publisher=[[British Army]], [[Ministry of Defence (United Kingdom)|Ministry of Defence]], UK|archiveurl=https://web.archive.org/web/20060728093921/http://www.army.mod.uk/royalsignals/equipment/digital.html|archivedate=28 July 2006}}</ref> and served in the first [[Gulf War]] as a [[Military tactics|tactical]] mobile communication [[network switch]]. The PP250 was sold commercially circa 1972. ==See also== *[[Army Communications and Information Systems (United Kingdom)]] * [[Flex machine]] ==References== {{reflist}} ==External links== *{{Citation | last = von Neumann | first = John | author-link = John von Neumann | title = First Draft of a Report on the EDVAC | year = 1945 | url = http://web.mit.edu/STS.035/www/PDFs/edvac.pdf | accessdate = August 31, 2020 }} *{{cite book | last = Goldstine | first = Herman H. | authorlink = Herman Goldstine | title = The Computer: from Pascal to von Neumann | url = https://archive.org/details/computerfrompasc00herm | url-access = registration | year = 1972 | publisher = Princeton University Press | location = Princeton, New Jersey | isbn = 0-691-02367-0 }} *{{cite book | last = Stern | first = Nancy | title = From ENIAC to UNIVAC, An appraisal of the Eckert-Mauchly Computers | year = 1981 | publisher = Digital Press | location = Bedford, Massachusetts | isbn = 0-932376-14-2 }} * {{cite book|url=https://archive.org/details/plessey-system-250-general-introduction/mode/1up|title=System 250 General Introduction |publisher=Plessey LTD|date=1972}} * {{cite conference|url=http://www.cs.ucf.edu/courses/cop6614/fall2005/englandplessey250.pdf|title=Capability Concept Mechanisms And Structure In System 250|author=D. M. England|conference=International Workshop on Protection in Operating Systems|date=August 1974}} * {{cite web|url=https://archive.org/details/architectural-features-of-system-250/mode/1up|title=Architectural Features of System 250|author=D. M. England|date=1972}} * [https://archive.org/details/plessey-system-250-icc-papers/page/n32/mode/1up System 250 ICC Papers] - four papers presented at the inaugural International Conference on Computer Communications * [https://archive.org/details/plessey-system-250-iss-papers/mode/1up System 250 ISS Papers] - four papers presented at the International Switching Symposium * {{cite web|url=http://www.cs.ucf.edu/courses/cop6614/fall2004/System250_Direcks.pdf|title=Capability Concept Mechanism and Structure in System 250|author=Christian Diercks}} * [https://photos.google.com/share/AF1QipNrCK2thGg7srEcJ-PjYgjNhhA6SX6C89vfJVybxqrM-U8qXFCgelpg_a7ihJZRJw/photo/AF1QipO1Fyp7NwBzoEMTyLd_ueAOFnT46o_WBFV2ToSc?key=MzlxbG9rbUdXUGprUGp0STJpYlB5WjhidkpIcjBR Photograph of the 250 Multiprocessor System (1975)] * [https://www.amazon.com/Civilizing-Cyberspace-Digital-Democracy-Latest/dp/1964148669/ref=sr_1_1?crid=3U4YEPMOVCH9J&dib=eyJ2IjoiMSJ9.f1UGcjGAVcMom2dBDVPZRdEbQKvN-vtutb-sDo2xWPH0D0zn45sCaFJgTIzkM9st.mlBxgloJpVuT0iQPUkW4tJnypagtatBKePz6VsAu-bM&dib_tag=se&keywords=Civilizing+Cyberspace%3A+The+Fight+for+Digital+Democracy&qid=1727393451&s=books&sprefix=civilizing+cyberspace+the+fight+for+digital+democracy%2Cstripbooks%2C1187&sr=1-1 Civilizing Cyberspace - The Fight for Digital Democracy, Book on PP250] * [[Winning World War III: Industrial Strength Computer Science, Book on PP250,]] [https://www.amazon.com/dp/1964864984/ref=sr_1_1?crid=22ZBPGZG01O8D&dib=eyJ2IjoiMSJ9.F6mgGoWdx5kKSiSBwuL_MI96OXNCLSWH1S4X5YE3FH7_TavVoO1L8S-RnD0JSggdinANxE3KdARa-h8S1ZrMWHPfsRQ_kWIzG6FtuQsgyERZveiU4LZV1G6dWaDuWlath9lLb1lke090L56CK5ffjyLoOyEbD6JS0L0b0hWiRDz8HSwAa5NVgU7jij7X9rzgaF0KqjlZ4COIAXPUcDGwvR_S-OQS6cDhbZ9GX-kAItg.NtI1WL-TPDPiWs0rMQdzxDEllXzBPL0cRnpNxClbcyE&dib_tag=se&keywords=Winning+World+War+III&qid=1739297999&s=books&sprefix=winning+world+war+iii%2Cstripbooks%2C529&sr=1-1] {{Object-capability security}} [[Category:British Army equipment]] [[Category:Computers designed in the United Kingdom]] [[Category:Capability systems]] [[Category:History of computing in the United Kingdom]] [[Category:Military computers]] [[Category:Plessey]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Ambox
(
edit
)
Template:Citation
(
edit
)
Template:Cite book
(
edit
)
Template:Cite conference
(
edit
)
Template:Cite web
(
edit
)
Template:Cn
(
edit
)
Template:DMCA
(
edit
)
Template:Object-capability security
(
edit
)
Template:Reflist
(
edit
)
Template:Tone
(
edit
)