[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Fix releasing procedure
From: |
Scott James Remnant |
Subject: |
Re: [PATCH] Fix releasing procedure |
Date: |
Tue, 27 Jan 2004 10:59:58 +0000 |
On Tue, 2004-01-27 at 10:40, Alexandre Duret-Lutz wrote:
> On Tue, Jan 27, 2004 at 10:17:52AM +0000, Scott James Remnant wrote:
> > *gulps* it stores my GPG passphrase in a shell variable?!
>
> Yep. Just like mailcrypt stores it in an emacs variable, or gpg in a
> C variable. What's the difference?
>
GPG takes great pains to use secure memory for the passphrase, so it
can't be read by any random joe logged into the box.
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
- [PATCH] Fix releasing procedure, Scott James Remnant, 2004/01/27
- Re: [PATCH] Fix releasing procedure, Alexandre Duret-Lutz, 2004/01/27
- Re: [PATCH] Fix releasing procedure, Gary V . Vaughan, 2004/01/27
- Re: [PATCH] Fix releasing procedure, Alexandre Duret-Lutz, 2004/01/27
- Re: [PATCH] Fix releasing procedure, Alexandre Duret-Lutz, 2004/01/27
- Re: [PATCH] Fix releasing procedure, Gary V. Vaughan, 2004/01/27
- Re: [PATCH] Fix releasing procedure, Alexandre Duret-Lutz, 2004/01/27
- Re: [PATCH] Fix releasing procedure, Scott James Remnant, 2004/01/28
- FYI: fix gnupload (Was: Re: [PATCH] Fix releasing procedure), Alexandre Duret-Lutz, 2004/01/28
Re: [PATCH] Fix releasing procedure, Gary V . Vaughan, 2004/01/27