woodman
Joined 12 years ago
Joined 12 years ago
Your comparison is out of line because of ridiculous characterizations like this. Microsoft said that it was a backup key, which either means that they have the most poorly implemented scheme for backing up cryptographic materials ever devised, or they don't mean what most people think when they hear the word "backup". Microsoft then claimed that the backup was necessary for passing the export control review, which is a bold lie to tell since the Export Administration Regulations are available for review to everybody. One thing not included in the EAR that might influence Microsoft's conduct in trying to get permission from the USG to reach global customers: executive orders. The government had a hard limit at 56-bits and was proposing that anybody wanting to export crypto beyond that needed to participate in their push for private-key escrow, which they were calling "key-recovery". Recovery... sounds kind of like a backup plan...
I provided links in my response to the parent comment.
I'll tell you what it looks like to me:
After the debug symbol is found, Microsoft gives a seemingly very stupid explanation for it[1]: "It is a backup key. Yeah, uhhhh... during the export control review - the NSA said that we had to have a backup key, so we named it after them..." After being challenged on the plausibility of their backup scheme they refuse to provide any further explanation.
Here is the funny part: Microsoft might be technically telling the truth about it being a "backup". Consider what else was going on around this period: ridiculous export controls on key-length, the clipper chip... and finally: government managed private-key escrow[2]. At that time the export regulations did not specify a backup requirement, and yet Microsoft claims otherwise. You know who else was talking a lot about backups? The Whitehouse, in its proposal for allowing the export of key-lengths above 56-bits - so long as applicants implement "key-recovery".[3] Somehow I don't think that we share the same definition of the word "backup".
Also, ECI Sentry Raven[4], have fun with that.
[0] https://assets.documentcloud.org/documents/784280/sigint-ena...
[1] https://cryptome.org/nsakey-ms-dc.htm
[2] https://web.archive.org/web/20000818204903/https://csrc.nist...
[3] https://epic.org/crypto/key_escrow/key_recovery.html
[4] https://archive.org/details/nsa-sentry-eagle-the-intercept-1...
https://en.wikipedia.org/wiki/NSAKEY.
I thought everybody already knew that US corporations serve as an extension to the surveillance apparatus. Remember all the corporations fighting against the government's mandate at an artificially crippled maximum keysize of 40 bits, in order to allow continued surveillance in the 90s? Yeah, neither do I.
The most recent liberation of useful taxpayer funded software that I can think of was over ten years ago, when NIST released NFIS2 - the fingerprint software that the FBI relied on. They of course had to be crappy about it and wrap it in export controls that limited its utility, but it was interesting to see all the work that internal development had done - very polished, with man pages going back to '97. Ah the memories: software classified as munitions, the clipper chip...
[0] http://archive.adaic.com/pol-hist/policy/naig94-1.txt
[1] https://en.wikipedia.org/wiki/IDEF#The_IDEF_modeling_languag...
[2] https://en.wikipedia.org/wiki/MIL-STD-498
[3] https://web.archive.org/web/20041206072946/http://fingerprin...
This is already a thing, and it is starting to look like an incredibly bad idea. Well over a year ago I had lunch with my financial advisor and he tried to sell me on a portfolio balanced on some kind of social responsibility metric (female board member ratio, carbon credits, etc). At the time I thought it was just a new way to separate morons from their money, but now I'm starting to think that the US markets are setting themselves up for a fungibility attack. I remember, many years ago, the debate on bitcoin tainting - keeping a register of illegally obtained coins (and leaf transactions) and refusing to accept them. That is obviously an attack on the utility of the currency - a unit of value.
So what is the metric here, what is the new unit of value? The best case outcome is a Tower of Babel pandemonium, worst case is an irreversible further consolidation of kingmaking power.
BTW... She is using a still[0] from a video that CNN owns the copyright to, and section 3 of their tos[1] explicitly forbids doing what she is doing - with the unnecessarily stated exception "as otherwise expressly permitted under copyright law". You really want to take that exception away from her? I can pretty easily argue that her use is transformative, can you? How does this differ from what she is complaining about?
[0] http://www.erynnbrook.com/white-feelings-for-charlottesville... [1] https://www.cnn.com/terms
I'm surprised by the sympathy I'm seeing for this position. You people know that she is effectively complaining about fair use, right? This is not something that can be budged on, even in deference to the feelings of a "writer/feminist/educator". Fair use is the only thing that stands between us and massive intellectual property cartels guiding the public consciousness through selective enforcement. Wanna go back to network television? Because this is how you do it.
Queue rekt.webm: https://trends.builtwith.com/feeds/RSS
8chan
Encyclopedia Dramatica
BitChute
If you expand the scope beyond Patreon and include Paypal then you can throw in: Wikileaks
Numerous Antifa chapters
World Socialist Web Site
As somebody who has been involved with bitcoin since 2012, I can tell you from first hand experience that when Visa declares you a persona non grata - a large number of businesses quickly do the same. Yes, the full list of Patreon service denials includes a lot of unsympathetic figures - but you'd be a fool to think that this behavior doesn't shift with the Overton window (welcome back to the world of crypto currency, Dwolla, betcha feel silly for screwing up that perfect opportunity Paypal gave you).
It would only work one way with an API relying on a PKI with a single CA, zero transparency, and trusted keys named after spy agencies suddenly appearing out of nowhere. I'm gonna bail here, because I'm now not sure if you honestly don't know what the CAPI was in relation to the NSAKEY - or if you're trying to waste my time by getting me to explain the most basic principles of public key infrastructure.