Re: Disabling encryption on saved copies of outgoing.
On 2000.10.11 13:19:22, you, the extraordinary raf, opined: Nollaig MacKenzie wrote: snip! Am I right in thinking that the message Bcc-ed to myself is encrypted quite independently of the message "To: " whoever (and vice-versa, which is what actually matters)? Cheers, N. no, but the solution is trivial. create an "anonymous" secret/public key pair for use when sending anonymous mail. it doesn't matter if people can see that a message was encrypted to: [EMAIL PROTECTED] and they can't locate the "public" key because you've hidden it under a rock Cool. Thanks! I made it a little more complicated, Bcc-ing to [EMAIL PROTECTED] encrypted, and putting an entry in /etc/hosts: my.ip.num.ber go-fsck-youself.com (I didn't actually use go-fsck-youself.com :-) Cheers, N. -- Nollaig MacKenzie :: [EMAIL PROTECTED] http://www.amhuinnsuidhe.cx
Re: Disabling encryption on saved copies of outgoing.
Nollaig, et al -- ...and then Nollaig MacKenzie said... % % On 2000.10.10 21:45:14, you, % the extraordinary Mikko Hänninen, opined: He is, indeed :-) % % Nollaig MacKenzie [EMAIL PROTECTED] wrote on Tue, 10 Oct 2000: % Am I right in thinking that the message Bcc-ed to ... % % AFAIK, you're not right. The sendmail (or equivalent) program gets ... % % Quite right, as usual (just for that I'm going % to make a sig asserting the superiority of the % Dixie Chicks to the Corrs :-) *grin* % % The single message contains the info about both % the keys used to encrypt, it seems. So I don't % see any straightforward way around the original % problem. It seems pretty simple to me... Just create an additional public/private pair and don't distribute the public key (or note any contact/identification in they key); if nobody has the public key, those 8 hex digits don't really mean much... % % Cheers, N. % -- % Nollaig MacKenzie :: [EMAIL PROTECTED] % http://www.amhuinnsuidhe.cx :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. PGP signature
Disabling encryption on saved copies of outgoing.
Hello, Wondering if anyone knows the answer to this. Looked through mutt.org docs and this newsgroup and couldn't find an answer. A copy of all my outgoing mail gets saved in =sent. When I send out mail encrypted with PGP, is there some way to prevent the saved copy from being encrypted too? It's almost pointless to save the encrypted version, since it is encrypted with someone else's public key and I can't decrypt and read my own sent mail. The mutt-pgp HOW-TO mentions a config variable called pgp_encryptself. But this variable doesn't seem to exist anymore in 1.2.5i, which is the version I'm using. Thanks, -- Red __ Do You Yahoo!? Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/
Re: Disabling encryption on saved copies of outgoing.
On Tue, Oct 10, 2000 at 12:14:24AM -0400, David T-G wrote: It's almost pointless to save the encrypted version, since it is encrypted with someone else's public key and I can't decrypt and read my own sent mail. Well, then, you should simply encrypt to your key as well :-) If you contemplate EVER using remailers, this is a BAD idea. It's very easy to forget that outgoing messages are being encrypted to you, and that anyone can see that fact. So, when your message, carefully routed through a remailer chain to hide the source of the message, gets to the recipient, s/he can see that it is encrypted to you (as can anyone else with access to the encrypted message), which is a VERY strong clue as to who sent the message. It's really, really, easy to bungle security... -rex
Re: Disabling encryption on saved copies of outgoing.
red chair muttered: A copy of all my outgoing mail gets saved in =sent. When I send out mail encrypted with PGP, is there some way to prevent the saved copy from being encrypted too? set fcc_clear HTH, Michael -- What this country needs is a good five cent microcomputer. PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: Disabling encryption on saved copies of outgoing.
On 2000.10.10 05:23:25, you,
the extraordinary rex, opined:
On Tue, Oct 10, 2000 at 12:14:24AM -0400, David T-G wrote:
It's almost pointless to save the encrypted version, since it is
encrypted with someone else's public key and I can't decrypt and read my
own sent mail.
Well, then, you should simply encrypt to your key as well :-)
If you contemplate EVER using remailers, this is a BAD idea. It's very
easy to forget that outgoing messages are being encrypted to you, and that
anyone can see that fact. So, when your message, carefully routed through
a remailer chain to hide the source of the message, gets to the recipient,
s/he can see that it is encrypted to you (as can anyone else with access
to the encrypted message), which is a VERY strong clue as to who sent the
message.
May I check my thought about achieving the effect
of encrypting to self while avoiding the loss of
anonymity?
Put this in Mutt.aliases (or functional equivalent):
alias moi ${NAME} ${USER}@${HOST}
Define these macros in Muttrc or .muttrc:
macro compose \ce "bmoi\npe"
macro compose \cb "bmoi\npb"
^E in the compose menu puts myself on the "Bcc: "
line, invokes the pgp menu, and chooses "encrypt".
Am I right in thinking that the message Bcc-ed to
myself is encrypted quite independently of the
message "To: " whoever (and vice-versa, which is
what actually matters)?
Cheers, N.
--
Nollaig MacKenzie :: [EMAIL PROTECTED]
http://www.amhuinnsuidhe.cx
Re: Disabling encryption on saved copies of outgoing.
Nollaig MacKenzie [EMAIL PROTECTED] wrote on Tue, 10 Oct 2000: Am I right in thinking that the message Bcc-ed to myself is encrypted quite independently of the message "To: " whoever (and vice-versa, which is what actually matters)? AFAIK, you're not right. The sendmail (or equivalent) program gets invoked only once by Mutt, and all the copies will be thus sent at that one go. The message going to everyone is identical. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / From the Department of Redundancy Dept.
Re: Disabling encryption on saved copies of outgoing.
On 2000.10.10 21:45:14, you, the extraordinary Mikko Hänninen, opined: Nollaig MacKenzie [EMAIL PROTECTED] wrote on Tue, 10 Oct 2000: Am I right in thinking that the message Bcc-ed to myself is encrypted quite independently of the message "To: " whoever (and vice-versa, which is what actually matters)? AFAIK, you're not right. The sendmail (or equivalent) program gets invoked only once by Mutt, and all the copies will be thus sent at that one go. The message going to everyone is identical. Quite right, as usual (just for that I'm going to make a sig asserting the superiority of the Dixie Chicks to the Corrs :-) The single message contains the info about both the keys used to encrypt, it seems. So I don't see any straightforward way around the original problem. Cheers, N. -- Nollaig MacKenzie :: [EMAIL PROTECTED] http://www.amhuinnsuidhe.cx
Re: Disabling encryption on saved copies of outgoing.
Nollaig MacKenzie wrote:
On 2000.10.10 05:23:25, you,
the extraordinary rex, opined:
On Tue, Oct 10, 2000 at 12:14:24AM -0400, David T-G wrote:
It's almost pointless to save the encrypted version, since it is
encrypted with someone else's public key and I can't decrypt and read my
own sent mail.
Well, then, you should simply encrypt to your key as well :-)
If you contemplate EVER using remailers, this is a BAD idea. It's very
easy to forget that outgoing messages are being encrypted to you, and that
anyone can see that fact. So, when your message, carefully routed through
a remailer chain to hide the source of the message, gets to the recipient,
s/he can see that it is encrypted to you (as can anyone else with access
to the encrypted message), which is a VERY strong clue as to who sent the
message.
May I check my thought about achieving the effect
of encrypting to self while avoiding the loss of
anonymity?
Put this in Mutt.aliases (or functional equivalent):
alias moi ${NAME} ${USER}@${HOST}
Define these macros in Muttrc or .muttrc:
macro compose \ce "bmoi\npe"
macro compose \cb "bmoi\npb"
^E in the compose menu puts myself on the "Bcc: "
line, invokes the pgp menu, and chooses "encrypt".
Am I right in thinking that the message Bcc-ed to
myself is encrypted quite independently of the
message "To: " whoever (and vice-versa, which is
what actually matters)?
Cheers, N.
no, but the solution is trivial. create an "anonymous" secret/public key
pair for use when sending anonymous mail. it doesn't matter if people can
see that a message was encrypted to: [EMAIL PROTECTED]
and they can't locate the "public" key because you've hidden it under a
rock. they won't be able to identify you but you can still decrypt your own
sent mail. just don't ever use the same key when encrypting non-anonymous
mail.
raf
p.s. if you do this, please don't use the example address
given above 'cause they'll come looking for me :)
Disabling encryption on saved copies of outgoing.
Hello, Wondering if anyone knows the answer to this. Looked through mutt.org docs and this newsgroup and couldn't find an answer. A copy of all my outgoing mail gets saved in =sent. When I send out mail encrypted with PGP, is there some way to prevent the saved copy from being encrypted too? It's almost pointless to save the encrypted version, since it is encrypted with someone else's public key and I can't decrypt and read my own sent mail. The mutt-pgp HOW-TO mentions a config variable called pgp_encryptself. But this variable doesn't seem to exist anymore in 1.2.5i, which is the version I'm using. Thanks, -- Red __ Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/
Re: Disabling encryption on saved copies of outgoing.
Red -- ...and then red chair said... % Hello, % % Wondering if anyone knows the answer to this. Looked % through mutt.org docs % and this newsgroup and couldn't find an answer. Well, you've come to a good place :-) % % A copy of all my outgoing mail gets saved in =sent. Yep. % When I send out mail % encrypted with PGP, is there some way to prevent the % saved copy from being Sure, if you want to. Take a look at $fcc_clear (6.4.43 in the 1.2.5 manual) for more. % encrypted too? It's almost pointless to save the % encrypted version, since % it is encrypted with someone else's public key and I % can't decrypt and read % my own sent mail. Well, then, you should simply encrypt to your key as well :-) % % The mutt-pgp HOW-TO mentions a config variable called % pgp_encryptself. But % this variable doesn't seem to exist anymore in 1.2.5i, % which is the version % I'm using. Yes, that changed a bit. I use gpg; in the newer mutts I started out specifying my key as an additional recipient on the *encrypt* lines in the gpg.rc file (as in set pgp_encrypt_only_command="pgpewrap gpg -v ... -- -r B66D9EEA %r ..." or so) but have since changed my method to specify this on the gpg side (as in encrypt-to B66D9EEA in $HOME/.gnupg/options) since I only ever sign with one key (mutt could let me define *-hooks that changed the pgp_* command to change the key specified with -r if it were necessary). One of these two approaches ought to work for you... % % Thanks, % -- Red HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. PGP signature
