On Thu, 2006-07-13 at 23:15 +0200, Samuel ]slund wrote:
> If I read this thread right you actually wnt to make a decryption and
> compare the results and you do _not_ want to keep the private key on
> that machine.
>
> Could you do something creative with --show-session-key to be able to
> dec
On Sat, 2006-07-15 at 00:05 +0930, Alphax wrote:
> Better than that, if you get GPG to sign the file when it encrypts it
> (using a passwordless key/subkey) and/or use the MDC option, you'll be
> able to do this more reliably...
Thank you, Alphax! I'll look into that.
Benny
___
On Fri, 2006-07-14 at 15:07 +0200, Janusz A. Urbanowicz wrote:
> > Can you please explain what you mean by "check the gpg's rc after the
> > encryption run?" I'm unfamilar with the meaning of "rc" in this case.
>
> return code
>
> every unix code returns an numerical code which by convention mea
On Wed, 2006-07-12 at 15:13 -0400, Jeffrey F. Bloss wrote:
> Benny Helms wrote:
>
>
> Don't know if this will help or not, but I just did a quick test with
> GnuPG 1.4.4 and the --dry-run command line switch seem to work fine.
> Outputs to stdout rather than writing a fil
On Wed, 2006-07-12 at 13:11 -0500, Jonathan Rockway wrote:
>
> BTW, why are you encrypting these files anyway? If someone broke into
> your computer they could just steal the crypto key too.
Excellent question! Truth be told, as soon as they are encrypted,
they're being moved to another serve
On Wed, 2006-07-12 at 13:23 -0400, Mark Hardman wrote:
> If you're using bash, can't you just script it like this...
>
> 1. encrypt to gpg
> 2. decrypt to text (or whatever it was originally) with altered file
> name (filename.test_decrypt)
> 3. do a diff between the original file and the newl
On Wed, 2006-07-12 at 05:14 -0500, Robert J. Hansen wrote:
> Benny Helms wrote:
> > I'm looking for a way to gpg encrypt a file, test that the encryption
> > was good and that the file can be extracted, and then to delete the
> > original file.
>
> Forgive a silly
On Wed, 2006-07-12 at 12:25 +0200, Janusz A. Urbanowicz wrote:
> On Tue, Jul 11, 2006 at 01:38:23PM -0600, Benny Helms wrote:
> What is your actual threat model here?
>
> The simplest answer is to check gpg's rc after the encryption run.
Before deleting original file, I
3AM running 'gpg
--decrypt filename' to test it would be very helpful.
Is this something I'm just not seeing on the man page and in the FAQ's?
Thanks!
Benny Helms
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
