On Tue, 4 Jan 2011 22:37, johnicholas.hi...@gmail.com said:
> Is there a built-in way to reverse the double-dash mangling for nested
> clearsigned messages?
gpg --verify --output inner.asc outer.asc
Verifies the outer signature and writes the signed text to inner.asc
which may then be verifie
On Wed, Jan 5, 2011 at 3:20 AM, Werner Koch wrote:
> On Tue, 4 Jan 2011 22:37, johnicholas.hi...@gmail.com said:
>
>> Is there a built-in way to reverse the double-dash mangling for nested
>> clearsigned messages?
>
> gpg --verify --output inner.asc outer.asc
>
> Verifies the outer signature and
Hello David,
Thanks.
I am not using this key for any email program.
I am using it to sign and encrypt my backups.
I do have a key pair (I think - I followed instructions from the gpg home
page):
$gpg --list-keys
pub 4096R/F784A849 2010-09-29
uid Madhusudan Singh
sub 4096R
Hi, it appears --digest-algo is ignored for symmetric encryption using gpg
1.4.9. I was able to verify --cipher-algo does work but for some reason no
matter what I specify for --digest-algo I always get RIPEMD160 as the hash
according to --list-packets and pgpdump. It's definitely looking at what I
On 01/05/2011 01:37 PM, freej...@is-not-my.name wrote:
> Hi, it appears --digest-algo is ignored for symmetric encryption using gpg
> 1.4.9.
Using --digest-algo is pretty dangerous. It's easy to create messages
your recipients can't parse. --personal-digest-preferences is what you
want to use in
On 01/05/2011 10:37, freej...@is-not-my.name wrote:
Hi, it appears --digest-algo is ignored for symmetric encryption using gpg
1.4.9. I was able to verify --cipher-algo does work but for some reason no
matter what I specify for --digest-algo I always get RIPEMD160 as the hash
according to --list-
Hi,
If you are using a key to encrypt backups - then you are able to decrypt - as
well as encrypt.
What operating system are you using?
A good idea would be to go to the pgp...@yahoogroups.com and post your question
there
telling them what operating system you are using and giving a read out o
Thanks for your response.
I do not think it is any of those issues. I have used this system (and this
script I wrote) successfully in the past (on Linux / Mac). I just
transferred machines a few months ago (Mac OSX to Mac OSX) and somehow the
key did not transfer properly. Then I started getting t
> On 01/05/2011 01:37 PM, freej...@is-not-my.name wrote:
> > Hi, it appears --digest-algo is ignored for symmetric encryption using
> > gpg 1.4.9.
>
> Using --digest-algo is pretty dangerous. It's easy to create messages
> your recipients can't parse. --personal-digest-preferences is what you
>
On 1/5/2011 4:00 PM, freej...@is-not-my.name wrote:
> Then something is very odd. Here's my output, only I used IDEA instead of
> 3DES for my test:
You might want to reconsider using IDEA: although it was the bee's knees
for the early 1990s, the past twenty years (good /grief/ it's so strange
to s
>Message: 2
>Date: Wed, 05 Jan 2011 14:01:10 -0500
>From: "Robert J. Hansen"
>To: gnupg-users@gnupg.org
>Subject: Re: --digest-algo ignored on gnupg-1.4.9?
>> Hi, it appears --digest-algo is ignored for symmetric encryption
>using gpg
>> 1.4.9.
>SHA-1 is used in the symmetric packet, as is ex
> If you have a 1024 bit dsa key this is likely the cause. To help you
> more we'd need to know what kind of key you have, and what you're
> setting for disgest-algo. Also, Robert's reply was correct too. :)
Hello Doug!
*Symmetric* encryption!
> hth,
Maybe next time ;-)
_
12 matches
Mail list logo
