On 8/9/2013 9:03 AM, Edward K. Ream wrote:
On Fri, Aug 9, 2013 at 7:37 AM, Jacob Peck <[email protected]
<mailto:[email protected]>> wrote:
In light of recent government-sponsored programs in the US (not
that I wish to start a political debate here), perhaps it's not a
terrible idea to write a plugin that hooks into the loading and
saving code, encrypting/decrypting your data?
Relying on encryption looks hopeless. Today's story:
http://thenextweb.com/insider/2013/08/09/silent-circle-follows-lavabit-in-closing-its-encrypted-email-service-because-it-cannot-be-secure/
and the announcement from silent circle:
http://silentcircle.wordpress.com/2013/08/09/to-our-customers/
That's depressing.
The only wise course of action, imo, is to assume the NSA is spying on
*everything* we do.
Well, always have anyway. Still, I think this is a worthy place to
inspect, regardless of the NSA's power. Perhaps you want to store
passwords in a .leo, but you don't want those being visible to others.
I know, dangerous behavior, but still a valid use case. NSA or not,
preventing (non-government funded) unauthorized users from accessing the
outline seems like a good idea.
If you want to take effective action, then support the ACLU in it's
lawsuit:
http://www.aclu.org/nsa-surveillance
Please sign their petition and contribute money. I have.
Ditto.
Edward
--
As a side note, I've already gotten a quick AES-256 script working with
PyCrypto on Windows/Python 2.7. Shouldn't be too hard to scale up, once
I get around to it.
-->Jake
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
