……上层评论所说的内容，而且在此例中确实如此。这是基于能力的安全机制（capability based security）的一种较老形态，区别于后来那种靠加密算法强制约束名称的概念，但两者同样有效。你可以在 Henry M Levy 的《Capability Based Computer Systems》里了解更多内容。Hydra MMP、GE-645 和 iAPX 432 都是这种概念在硬件上的早期实现。在这两种情况下（无论是靠 TCB 表强制执行，还是靠加密单向函数强制执行），名称本身就是能力，……
…what the parent is talking about, and does in this case. It's an older morph of capability based security than the newer crypto enforced name concept, but equally valid. You can read more about it in Capability Based Computer Systems by Henry M Levy. The Hydra MMP, GE-645, and iAPX 432 are older implementions of this concept in hardware. In both cases (TCB table enforced and crypto one way function enforced) the name is the capability,…
System/38，后来的 AS/400，是我见过的当时设计最出色的系统之一：
https://homes.cs.washington.edu/~levy/capabook/Chapter8.pdf
为商业应用设计、面向未来、集成数据库、很大程度上自我管理、能力安全、持续运行在可靠的（POWER）硬件上……几乎一切都做对了。这就是为什么我们经常修崩溃的 Windows 和 'NIX 机器
System/38, later AS/400, was one of the most brilliantly designed systems of the time that I've seen:
https://homes.cs.washington.edu/~levy/capabook/Chapter8.pdf
Designed for business apps, future-proofing, integrated database, largely self-managing, capability-security, continuing on solid (POWER) hardware... did about everything right. That's why we regularly fix crashed Windows and 'NIX machi
Here is a book of case studies of object-capability projects in the 1960s 70s and 80s, including several products from big computer companies:
http://homes.cs.washington.edu/~levy/capabook/
Henry M Levy 1984 年写的那本相关著作《Capability-Based Computer Systems》，在作者的个人网站上提供免费的 PDF 版本：http://homes.cs.washington.edu/~levy/capabook/
Henry M Levy's relevant 1984 book, Capability-Based Computer Systems, is available free in PDF form on the author's web site: http://homes.cs.washington.edu/~levy/capabook/
> 它在硬件层面实现了对对象的支持，
> 并基于每个对象进行访问保护。
定期提醒：Henry Levy 的《Capability-Based Computer Systems》有免费 PDF 版¹。
432 很慢，但 i960² 是一个干净的 RISC，本来可以有未来。
¹ http://homes.cs.washington.edu/~levy/capabook/
² https://en.wikipedia.org/wiki/Intel_i960
> It implemented support for objects at the hardware level,
> with access protection for on a per-object basis.
Periodic reminder that Henry Levy's Capability-Based Computer Systems is available in PDF form for free¹.
The 432 was slow, but the i960² was a clean RISC that could have had a future.
¹ http://homes.cs.washington.edu/~levy/capabook/
² https://en.wikipedia.org/wiki/Intel_i960
We were thinking on the same lines. IBM System/38 was truly a brilliant, integrated design in so many ways. Even had capability-security built into the hardware. Check it out at the reference below. Intel made a monster of a system too. Would love to have either on a SOC or an inexpensive server.
http://homes.cs.washington.edu/~levy/capabook/index.html
……上层评论所说的内容，而且在此例中确实如此。这是基于能力的安全机制（capability based security）的一种较老形态，区别于后来那种靠加密算法强制约束名称的概念，但两者同样有效。你可以在 Henry M Levy 的《Capability Based Computer Systems》里了解更多内容。Hydra MMP、GE-645 和 iAPX 432 都是这种概念在硬件上的早期实现。在这两种情况下（无论是靠 TCB 表强制执行，还是靠加密单向函数强制执行），名称本身就是能力，……
…what the parent is talking about, and does in this case. It's an older morph of capability based security than the newer crypto enforced name concept, but equally valid. You can read more about it in Capability Based Computer Systems by Henry M Levy. The Hydra MMP, GE-645, and iAPX 432 are older implementions of this concept in hardware. In both cases (TCB table enforced and crypto one way function enforced) the name is the capability,…
System/38，后来的 AS/400，是我见过的当时设计最出色的系统之一： https://homes.cs.washington.edu/~levy/capabook/Chapter8.pdf 为商业应用设计、面向未来、集成数据库、很大程度上自我管理、能力安全、持续运行在可靠的（POWER）硬件上……几乎一切都做对了。这就是为什么我们经常修崩溃的 Windows 和 'NIX 机器
System/38, later AS/400, was one of the most brilliantly designed systems of the time that I've seen: https://homes.cs.washington.edu/~levy/capabook/Chapter8.pdf Designed for business apps, future-proofing, integrated database, largely self-managing, capability-security, continuing on solid (POWER) hardware... did about everything right. That's why we regularly fix crashed Windows and 'NIX machi
这是一本关于 20 世纪 60、70、80 年代对象能力项目的案例研究书，包括大型计算机公司的几个产品： http://homes.cs.washington.edu/~levy/capabook/
Here is a book of case studies of object-capability projects in the 1960s 70s and 80s, including several products from big computer companies: http://homes.cs.washington.edu/~levy/capabook/
Henry M Levy 1984 年写的那本相关著作《Capability-Based Computer Systems》，在作者的个人网站上提供免费的 PDF 版本：http://homes.cs.washington.edu/~levy/capabook/
Henry M Levy's relevant 1984 book, Capability-Based Computer Systems, is available free in PDF form on the author's web site: http://homes.cs.washington.edu/~levy/capabook/
> 它在硬件层面实现了对对象的支持， > 并基于每个对象进行访问保护。 定期提醒：Henry Levy 的《Capability-Based Computer Systems》有免费 PDF 版¹。 432 很慢，但 i960² 是一个干净的 RISC，本来可以有未来。 ¹ http://homes.cs.washington.edu/~levy/capabook/ ² https://en.wikipedia.org/wiki/Intel_i960
> It implemented support for objects at the hardware level, > with access protection for on a per-object basis. Periodic reminder that Henry Levy's Capability-Based Computer Systems is available in PDF form for free¹. The 432 was slow, but the i960² was a clean RISC that could have had a future. ¹ http://homes.cs.washington.edu/~levy/capabook/ ² https://en.wikipedia.org/wiki/Intel_i960
我们想到一块去了。IBM System/38 在很多方面都是一个真正出色、高度集成的设计。甚至把能力安全（capability-security）内建到了硬件里。看看下面参考资料里的内容吧。Intel 也做过一个巨无霸系统。要是能在 SOC 或者便宜的服务器上跑其中任何一个就好了。 http://homes.cs.washington.edu/~levy/capabook/index.html
We were thinking on the same lines. IBM System/38 was truly a brilliant, integrated design in so many ways. Even had capability-security built into the hardware. Check it out at the reference below. Intel made a monster of a system too. Would love to have either on a SOC or an inexpensive server. http://homes.cs.washington.edu/~levy/capabook/index.html