Christopher Soghoian
Benjamin Wittes
@csoghoian To reiterate: I am not against encryption. Not even against end-to-end encryption. And once again, ad hominem with no analysis.
In which @benjaminwittes continues his braindead jihad against encryption.https://twitter.com/benjaminwittes/status/626710837856706561 …
-
-
-
@benjaminwittes give me permission to publish the emails you sent me about HTTPS. -
@csoghoian What does that have to do with it? -
@benjaminwittes your view of HTTPS as some kind of luxury to be withheld from your readers to spite me is relevant to this discussion. -
@csoghoian It's not a question of spite. It's a question of not being bullied into things by you--or anyone else. Feel free to publish... -
@benjaminwittes thank you. -
@csoghoian Where are you going to publish it, btw?
-
-
-
@csoghoian I am not sure at all that Apple is not doing the right thing by encrypting end to end. -
@benjaminwittes And is Apple doing the right thing or wrong thing by backing up those same messages, unencrypted, to its iCloud service? -
@lofdev@csoghoian The service in question is public key management. -
@benjaminwittes@lofdev also, delivery of messages.
-
-
@csoghoian ...post as a jihad. I agree with you, of course, that I'm braindead. -
@csoghoian You can be in denial if you like that there's a serious set of questions here, but I promise you that Apple GC would read that... -
@csoghoian But that does not answer the question of whether there is potential liability for the move. That is a legal question. -
-
@csoghoian@benjaminwittes should we be allowed to keep secrets from the government? -
@JoeBeOne@csoghoian of course. -
@benjaminwittes@csoghoian cool. those are the table stakes. recent hypo would be more interesting if the tool were an open source tool
-
-
-
@csoghoian@benjaminwittes@AZoeB85 so if gun mfgs kept ballistics records, they'd be similarly liable? -
@JohnLaprise@csoghoian@AZoeB85 that issue is closer to the one we addressed in Part I of the series.
-
Dave Loftis
Joseph Lorenzo Hall
John Laprise
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.