Hi,
I'm wondering about the privacy implications of using mutt. Say I'm
using it on my laptop (or any untrusted host, maybe a computer owned and
administrated by someone else) and if my laptop gets stolen I don't want
my email to be compromised in any way. I don't want a copy of my email
to be sto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Monday, May 10 at 04:06 PM, quoth chombee:
> I'm wondering about the privacy implications of using mutt. Say I'm
> using it on my laptop (or any untrusted host, maybe a computer owned
> and administrated by someone else) and if my laptop gets st
On May 10, 2010 at 11:00 AM -0500, Kyle Wheeler wrote:
I used to do that, until I discovered the power of gpg to decode things on
the fly. Now I have an encrypted mutt config file that is sourced by the
main mutt config file, like this:
source "gpg -d .muttrc.secure.gpg|"
Do what?!? Tha
chombee writes:
> I'm wondering about the privacy implications of using mutt.
As usual, if "they" have physical access then all bets are off. Having
said that, at least physical access to a computer you own is pretty much
under your control. Data on some remote server? Not so much, no.
chombee wrote:
Hi,
I'm wondering about the privacy implications of using mutt. Say I'm
using it on my laptop (or any untrusted host, maybe a computer owned and
administrated by someone else) and if my laptop gets stolen I don't want
my email to be compromised in any way. I don't want a copy of m
On Mon, May 10, 2010 at 12:08:52PM -0400, Tim Gray wrote:
>On May 10, 2010 at 11:00 AM -0500, Kyle Wheeler wrote:
>>I used to do that, until I discovered the power of gpg to decode
>>things on the fly. Now I have an encrypted mutt config file that is
>>sourced by the main mutt config file, like thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Monday, May 10 at 01:06 PM, quoth rog...@sdf.org:
>>>source "gpg -d .muttrc.secure.gpg|"
>>
>> Do what?!? That's awesome. Thanks for the tip. Not sure if I'll
>> use it, but it's a great thing to keep in the bag of tricks.
>
> wow, a bash