The IMEI example was just to demonstrate the ability to slap a device-unique code + matching sticker on something during manufacturing at scale.
1,087 karma · joined June 4, 2015
The IMEI example was just to demonstrate the ability to slap a device-unique code + matching sticker on something during manufacturing at scale.
How so? It's a solved problem. Don't smartphones already have numerous device-specific identifiers and keys loaded to them? All they would really need to do is slap an extra sticker on the device with the device-specific key printed on it. For instance, my phone came with a sticker with its IMEI printed on it.
That's easily solved: On initial device setup, the user could be asked to explicitly disable the key by asking something like "Would you like to secure your device by permanently disallowing the installation of untrusted software? Y/N"
Also, as someone else clarified below, the alternate key I was proposing is unique to the device. So any attack against you would have to be tailored to your device. That leaves the main threats as: 1) an NSA-like shipment-interception and 2) someone getting access to your user key after the device is in your possession. 1) can be mitigated by buying your device in a random retail shop, and 2) can be prevented by immediately permanently clearing the user the key.
I think that's wrong: http://www.gnu.org/licenses/gpl-faq.en.html#GiveUpKeys:
> I use public key cryptography to sign my code to assure its authenticity. Is it true that GPLv3 forces me to release my private signing keys? (#GiveUpKeys)
> No. The only time you would be required to release signing keys is if you conveyed GPLed software inside a User Product, and its hardware checked the software for a valid cryptographic signature before it would function. In that specific case, you would be required to provide anyone who owned the device, on demand, with the key to sign and install modified software on his device so that it will run. If each instance of the device uses a different key, then you need only give each purchaser the key for his instance.
It sounds like a manufacturer could ship a GPLv3-compliant User Product with two signing keys: a secret one known only to the manufacturer, and a second per-device key than can be used by the end-user to install modified software. Such a manufacturer wouldn't be forced to disclose their signing key because the user already has access to an equivalent.
I also imagine it would be kosher for the device to provide the user the option, in the name of security, to permanently clear the second per-device key, so only manufacturer updates can ever be installed.
> companies like Apple won't even allow employees to install GPLv3 software on their work computer because if a single piece of GPLv3-licensed code makes it into iOS, even completely accidentally, the license demands that Apple release their root signing keys to the world, completely destroying the security of hundreds of millions of devices.
If Apple is behaving that way, it's Apple's own fault, not the GPLv3's. They could have chosen to design their software in a way that would have given them better options if they are ever forced to comply with the GPLv3, but they chose not to.
Are there full/partial mirrors published anywhere?
That's kind of an interesting question. There's certainly some stuff there worth saving forever, but there's also stuff that's just plain bad or that's the intellectual equivalent of embarrassing childhood photos, which may not be worth saving at all.
I never was part of Usenet, but I understand a lot of people were angry at Dejanews and Google when what was once (perhaps naively) viewed as ephemeral communication was turned into a public searchable archive. At least most people on Kuro5hin used pseudonyms.
Maybe you should also have the option of setting up a "coercion fingerprint(s)", which if used to authenticate would put the phone into require-passcode mode. Then, if the court compels you to unlock your phone with your fingerprint, you can put yourself back into 5th amendment territory.
Actually, in that last case, you might already be protected. If 9 if your fingers will force your phone to require a passcode, and only one will unlock it. Could the courts/police force you to disclose which finger is the one that unlocks? I'd imagine you could put them in a situation where they have to chose which finger you use (or manipulate your hand themselves) to perform the unlock action, and in that case they'd only have a 1/10 chance of actually getting what they want.
That hasn't happened to me, but I've seen it happen enough to not want to bother.
I used to see some kuro5hin usernames I recognized on Metafilter, but for the most part I think they've left that site (or been purged, you can never really tell).
https://web.archive.org/web/20080113234818/http://www.swtime...
Have you tried emailing them to test your theory?
Underspecified.
Understanding, correctly, what an underspecified system should do is a strong AI problem (in most cases, at least). All (or nearly all) unbuilt systems are underspecified (as well as many built ones). We do not yet have strong AI. Hence, we have developers who will continue to collect paychecks for the foreseeable future (your "tired meme").
> What is it about information machines (as opposed to humans) that make them unable to handle ambiguity? Why can't a machine handle ambiguous input?
Your focus on "ambiguous input" misleads you. The difficulty is more like ambiguous output.
Isn't this sort of thing really common?
If that's true, it sounds like a solution is search of a requirement. IIRC, but I don't think the US military has had problems with tampering and sabotage of military jets.
The fourth computer's software was only sufficient to abort the mission and return the shuttle to the Earth. IIRC, they never had to use it.
* They don't know that their beans can actually sell for so much
* They don't know how to sell their beans for higher prices (e.g. they don't have access to the right middlemen)
* They aren't coordinated enough and undercut each other when dealing with the middlemen.
* Starbuck's premium prices may have little to do with the beans themselves
I think it's more likely that, goods will become more flimsy, cheaply made, and disposable. If true progress no longer provides motivation to buy new things, manufacturers will invent new ones.
What do you mean by this? How likely would it be for a seller to even be in a position to ship orders from multiple websites in the same box? And how would Amazon find out without buying things on competitor websites and checking return addresses?
Wasn't the controversy more about how the shirt was perceived by randos on twitter, not by his colleagues?
It's not just about cost of the platform, but also the capabilities provided by it. So even if the F35 is "finished" it won't necessarily fill the void left by the A-10, so more A-10s might be a better investment.
From what I understand, the F35 did not gain effectiveness in proportion to its cost.
One hiccup to that idea is that apparently the original A-10 blueprints were "lost" over the course of several defense-contractor mergers. I don't think that should be a huge hurdle to overcome though, since they've been able to modernize the planes and design and build major replacement components for them (like new wings). However, the Air Force brass would probably make a big deal out of the missing plans in their smokescreen.
I think they should just transfer the close air support role (along with the planes, personnel, and all associated budget) to the Army.