The political appointees pushing this new policy have not presented any evidence of these deaths beyond a vague assertion in a leaked internal email. They have not provided that evidence to career staffers either.
Yes, that's a good way to think of it---we need to come up with a valid / reasonable context in which to explore the function at all, which will subsequently let us look for other bugs (like the divide by zero in the blog post).
Developer here: "not actively developed" might be a little strong---we currently don't have resources dedicated to quickly responding to issues, but we're not planning on abandoning it.
Various components of the SGX system (launch approval, remote attestation quote signing, etc) are implemented as Intel provided enclaves. AESM manages those enclaves and provides an untrusted API to communicate with them.
There is some very cool language design work from Chinawat Isradisaikul and Andrew C. Myers at Cornell on adding very powerful matching constructs to a Java-like language.
Database choice aside, I'm shocked that this wasn't noticed when designing the app... It's clearly not a design decision because they refer to it as an error later in the paragraph.
Of course, this article is about New Zealand, but I will not be surprised to see similar things in the States. Thankfully ACA provides protection for health insurance, but we're already seeing things like https://www.congress.gov/bill/115th-congress/house-bill/1313.
I think the alternative being suggested is that rm shouldn't accept a string that magically can reference anything in the filesystem...
In our capability-based shell scripting language Shill (shill-lang.org) for example, you could prevent this sort of bug by giving the script a capability for just the diaspora_home directory, and deriving the child directories from that capability. (Of course, you still need to make sure you pass in the right directory in the first place.)
I (with some colleagues) developed a capability-based shell scripting language (http://shill-lang.org) that makes it easier to apply the Principle of Least Privilege to system administration tasks and also functions as a modular, programmable sandbox.
We're currently working on a port to Linux and a commercial version. If you're intrigued, I'd love to chat.
In a Typed Racket program that does not import any untyped racket code, there is no runtime enforcement. Runtime contracts are only introduced at the boundary between typed and untyped code. This allows programs to be soundly transitioned from untyped to partially typed to fully typed.
Well, for one, that he chose to say "will be taken away" when responding to this criticism, instead of "should be taken away," implying that he thinks they ought to be taken away (because it would allow for his libertarian utopia) but that it won't happen for other reasons.
This is among the many use cases we're hoping to solve with our secure shell scripting language Shill (http://shill.seas.harvard.edu/).
We're currently working on a commercial version of Shill targeting Linux. If Shill sounds like a product your company wishes it could find, we'd love to hear from you. Shoot me an email at [email protected].