7 ms·
Unlike Medicine, many of the ideas that we had in the past were better than the commonly accepted way things are done now. Capability based security, for examp
by mikewarot 6y ago
Unlike Medicine, many of the ideas that we had in the past were better than the commonly accepted way things are done now.
Capability based security, for example was something that allowed you to run any program, with no danger to your system. It's not part of any common OS. They had it at Xerox PARC, but Steve Jobs chose not to take that part.
On the other hand, the PARC focus on replicating paper was a step backwards from work by Engelbart and others.
The limitation of a single desktop was put in place to allow children to ease into the desktop metaphor... it wasn't meant for adults to be stuck with the training wheels on.
I've been digging back, looking for the ideas we missed... and boy, there are some really powerful tools waiting to be reified in a modern context.
- Animats 6y agoCapability based security, for example was something that allowed you to run any program, with no danger to your system. It's not part of any common OS. I know, I know. Norm Hardy was really good, his system, KeyCos, worked, and few could understand him. I used to know his "explainer", Susan Rajunas. We don't even have proper "rings of protection", like Multics, any more. Although the real problem today is that we need to run programs with less authority than the user running them, and we still lack a good conceptual model for doing that. "Allow write to SD card" is far, far too powerful a privilege to grant.
- brandmeyer 6y ago> Although the real problem today is that we need to run programs with less authority than the user running them, All true; But. What really stopped capability systems is that most users cannot be bothered to grant minimum privilege. Even most developers cannot - we invented containers in part as a way to mitigate the consequences of failing to grant minimum privilege.
- jerf 6y agoAs the old saying goes, you go to war with the army you have. I have a bunch of fantastic solutions to all our problems, if only programmers would work 10 times harder for every line of code, and the project managers would be OK with that, and the business funding it would be OK with that, and society would be OK with getting 1/10th the software. Capabilities-based stuff is really neat, but it's also really complicated to put into practice, and I live in a world where it's often a struggle to get developers to label their brand new REST interface for whether or not it's "admin only". Personally, I think a lot of that "really complicated to put into practice" is essential complexity, not incidental; anytime you sit down and really think about what the optimal permissions scheme around any even slightly non-trivial system ought to be, you generally end up with something pretty complicated. But even if the perfect system existed and you handed it to the real developers we have today, you'd still be working with people who would do whatever the simplest thing they could do to fully bypass the capabilities system is and get on with life without a moment's twinge of conscience. I don't want to be too hard on the average programmer; contra fashionable cynicism, things are actually getting better on the decade time scale. But at the current pace, "capabilities" are probably still a decade or two away from even being "niche".
- cratermoon 6y agoI wish I could show this to a Big Data analyst I worked with. He spent all day doing machine learning things but once complained to my team that we were making access control too complicated.
- AnimalMuppet 6y agoIt's worse than that. You implement your perfect, minimum capability system. Your programmers really implement that. Everything's great... ... until someone from marketing shows up, and says, "Hey, we also need it to...", and the program now needs a bunch of new capabilities.
- ryukafalz 6y ago>we invented containers in part as a way to mitigate the consequences of failing to grant minimum privilege Also because it's extremely difficult to grant minimum privilege on your typical general-purpose OS today. Spawn a new process and the default is that it has all the same authority that you do - it takes a lot of work to dial that down. This is typically inverted in a capability system: the program only has the authority that you give it.
- contingencies 6y agowe need to run programs with less authority than the user running them, and we still lack a good conceptual model for doing that Isn't this now the standard reality for most desktop and mobile OSs? "Allow write to SD card" is far, far too powerful a privilege to grant. Granting a permission based upon user approval is never secure anyway since if they want to see the porn / flashing lights they are going to click the button regardless. Having spent some time with both carriers and mobile device manufacturers, there are also areas of undeclared commercial utility in keeping control with the OS (device manufacturer) and out of the hands of the user: DRM, app sales, increased chargeable mobile data use, reduced chance of non-cellular data paths (mesh networking), etc.
- mikewarot 6y agoPeople manage permissions just fine in the real world... if you have money in your pocket, you can pick and choose what portion of it to hand to the cashier when you're purchasing something. When you had someone $3.50... you're giving them $3.50 of capability, and no matter how clever the Loch Ness Monster is, they'll never get more than that $3.50. If on the other hand, you have to give them the entire wallet... like you do in Windows, Linux, etc... the game is over. Capability Based Security is NOT the same as "Global Permission to do X" PayPal exists because it is an instantiation of capabilities for finance on the internet.
- contingencies 6y agoyou can pick and choose what portion... That was the old way. The new way is you give them your credit card or WeChat 'bill me' code. You get billed whatever the merchant wants to bill. Any post-facto complaint will be at the cost of your own time. Your further analogy is factually inaccurate. Under Windows, AFAIK most programs have a partially restricted permission set, hence Run as administrator. In Linux, under modern distributions, most programs run in both a user and a cgroup context, and some under further restrictions such as chroot and caps.
- ryukafalz 6y ago
- jdsalaro 6y ago> Capability based security, for example was something that allowed you to run any program, with no danger to your system. It's not part of any common OS. They had it at Xerox PARC, but Steve Jobs chose not to take that part. For FreeBSD there's Capsicum(1) and for Linux, although the implementation is not strictly capabily-based, there's SE-Linux which depending on the usecase resembles capability-based restrictions. Also, although not based around capabilities, Linux has supported them for awhile https://linux.die.net/man/7/capabilities https://linux.die.net/man/7/capabilities (1) https://www.cl.cam.ac.uk/research/security/capsicum/ https://www.cl.cam.ac.uk/research/security/capsicum/
- mikewarot 6y agoSE-Linux is the worst possible way to secure a linux system, its like when Microsoft went overboard on warnings, instead of actually trying to solve the problem. The main implementation difference in a capability based system is using a PowerBox to select files to give to a process, instead of letting the process access everything the user has rights to.
- pjmlp 6y agoOn Android you get no option, SE-Linux and seccomp are enabled by default and there are other measures in place that top any other Linux based OS.
- C4ne 6y agoI find the comparison between medicine and computer science very interesting! I have never thought about it this way. Could you elaborate on how you „dig back“? Do you read old papers / books? I imagine that one would have to dig through much old stuff that just isn‘t interesting until you find something that could be really usefull (like capability based security).
- mikewarot 6y agoLook at the recent talks by Alan Kay, Ted Nelson, Joe Armstrong on YouTube. Watch "The Mother of all Demos" by Douglass Engelbart. There is a lot of stuff online, just follow the threads. I've been pushing Capability Based Security for a decade... only in the last 6 hours did I learn that they had it at Xerox PARC, in an offhanded comment by Ted Nelson at the end of one of his videos, where he mentions the great ideas that got away.
- deleted 6y ago[deleted]
- vector_spaces 6y agoOne of my favorite talks by Joe Armstrong -- computer science, a guide for the perplexed. He talks through what he feels are some important but forgotten ideas in CS https://youtu.be/rmueBVrLKcY https://youtu.be/rmueBVrLKcY
- saagarjha 6y agoWell, better in some sense: they might be cleaner, or more robust on some axis, but perhaps not practical or efficient. But, with computing the landscape can change rapidly so it is always good to see if older ideas can now be made a reality.
- redis_mlc 6y ago> Capability based security, ... They had it at Xerox PARC, but Steve Jobs chose not to take that part. To be fair: 1) Apple II and Macintoshes were slow 2) and single user 3) and pre-Internet (no networking, even.) Microsoft also had to make an early choice about what features to add to DOS, particularly networking or multiuser, and networking was chosen to implement first. (Probably because of Novell and other early networking competitors.) > the PARC focus on replicating paper was a step backwards "Replicating paper" was resurrected about 10 years ago when everybody was making apps with a UI like books turning pages. There was actually a programmer (Russian name if I receall) who specialized in consulting on that, advising companies on what algorithms to use and how to get the page flipping appearance they wanted. I thought it was pointless but hilarious, as it was totally ornamental. https://en.wikipedia.org/wiki/Skeuomorph https://en.wikipedia.org/wiki/Skeuomorph
- andi999 6y ago"The limitation of a single desktop was put in place to allow children to ease into the desktop metaphor." Any source for this? I dont thinkchildren were the target customers at that time.
- tremon 6y agoThey didn't mean literal children I guess, but "children" in the sense of blank-slate individuals exploring a new space. Adults can use training wheels too when first learning to ride a bike. But once they're competent, it's more expressive to ride without.
- andi999 6y agoI agree. But I am wondering, I remember linux had a lot of multiple Desktops, but somehow this fad never stuck. So maybe one Desktop was somehow a good idea?
- adamnew123456 6y agoI'm not sure fad is the right descriptor here. Unix WMs have had virtual desktops since the 90s (80s?), MacOS got them around 2006 and Windows in 2015. Use by the non-initiated may not be that high, but that shouldn't be surprising given that user education is a very scarce resource and it's being spent elsewhere.
- andi999 6y agoI meant as a default.
- pbhjpbhj 6y agoAren't document tabs, eg browser tabs, an app-confined version of multiple desktops. The idea behind their are virtual screens of content you can switch between. Every KDE I've installed (Slackware, Mandrake, Ubuntu, Fedora), to my recollection defaulted to multiple desktops. I'm so happy Win10 has virtual desktops as in moving from Linux to MS Windows - mandated by my workplace - that was a massive pain point.
- afarrell 6y agoWhen you someone performs surgery on one patient, the legacy medical impacts of that surgery are contained to at most 2 people and their immediate families. There will probably be fewer than 10 surgeries where someone might think about that -- and we don't begrudge a surgeon who doesn't. When you add a commit to an OS, the legacy impact of that stays with the OS and must be un-done by anyone who changes it.
- mr_t 6y agoCould you name a few examples of ideas we missed? You made me quite curious.
- doctorbaum 6y agoHow do you go about digging old PARC papers?
- pjmlp 6y agoYou start here, https://archive.org/details/bitsavers_xerox https://archive.org/details/bitsavers_xerox And then go over to symbolics, Borland, whatever.
- forgotmypw17 6y agoI think the same problems are present in medicine. For example, there's tons of evidence that fasting and rest can heal most things. It's talked about in just about every tribal knowledge compendium. It's assisted by doctors in some countries, almost completely ignored in others.
- bsder 6y ago> Capability based security, for example was something that allowed you to run any program, with no danger to your system. It's not part of any common OS. Basically, haven't we "reinvented" this via "The Eternal Mainframe"? Only now it's called Amazon Web Services?
- Shorel 6y agoThat's not your system.
- pjmlp 6y agoThe Burroughs mentioned by Knuth, already had tagged memory, a systems programming language with unsafe code blocks, co-routines, bounds checking, the whole package, Go like compile speed (for 1961 hardware), compiler intrisics instead of Assembly, the whole package. Nowadays still available as Unisys ClearPath MCP, with high level security as selling point, while it will take generations to fix UNIX and C's adoption at large, if ever.
- pjmlp 6y ago> They had it at Xerox PARC, but Steve Jobs chose not to take that part. At least they created Object Pascal and did two OSes with it, and contributed later on to the C++ industry adoption, instead of being yet another C powerhouse cloning UNIX.
- kps 6y ago> Capability based security … allowed you to run any program, with no danger to your system. ‘No danger to your system’ shouldn't be conflated with ‘no danger to you.’ The problem with capabilities is that they reinforce and solidify the ‘smartphone model’: your data isn't yours, it's an app's, so what you're permitted to do with it is entirely controlled by someone else.
- Jtsummers 6y agoWe shouldn't fear ideas just because it could be used to restrict some users of some systems. In the end, there will continue to be a market for less regulated hardware and OSes. Linux and the BSDs, as an end user if you own the system, are still wide open. x86/x64 systems aren't getting more locked down in general, and there's a significant movement toward more open hardware (at least within some niches) with RISC-V. Something like capability based security would be a godsend for the corporate and enterprise environment compared to what's commonly in place.
- jonjacky 6y agoSee also Bret Victor's talk, "The Future of Programming". The conceit: it's 1973, he describes (with an overhead projector and transparencies) some then-innovative ideas that he hopes will be adopted in the future. http://worrydream.com/dbx/ http://worrydream.com/dbx/
- jonjacky 6y agoThis was linked on HN a few days ago, contains links to dozens of classic papers back to the 1930s: https://canvas.harvard.edu/courses/34992/assignments/syllabus https://canvas.harvard.edu/courses/34992/assignments/syllabu... - Classics of Computer Science and that page contains this link to a spreadsheet with links to over 150 historic papers and other sources: https://docs.google.com/spreadsheets/d/1wS6O7-ZoFL7Cfjgt-kdhYxfg0qHdXyzpjJxikiqNPZg/edit#gid=65049622 https://docs.google.com/spreadsheets/d/1wS6O7-ZoFL7Cfjgt-kdh...
- jonjacky 6y agoAn unusual historical paper from Niklaus Wirth, about many "good and original ideas (that) turned out to be less brilliant than they first appeared." http://pascal.hansotten.com/uploads/wirth/Good%20Ideas%20Wirth.pdf http://pascal.hansotten.com/uploads/wirth/Good%20Ideas%20Wir...