On Sat, May 27, 2006 at 10:02:15PM +0200, Qed wrote:
> I was investigating the possibility to use a RSA master key with SHA256
> or SHA512 as certification digest algorithm.
> The problem is, as usual, compatibility.
>
> I don't know anything about the diffusion of the various PGP versions
> and t
I was investigating the possibility to use a RSA master key with SHA256
or SHA512 as certification digest algorithm.
The problem is, as usual, compatibility.
I don't know anything about the diffusion of the various PGP versions
and their capabilities.
I've found a PGP compatibility table, written
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Was Sat, 27 May 2006, at 21:41:04 +0200,
when Henk wrote:
> On Sat, 27 May 2006 21:13:15 +0200GMT (27-5-2006, 21:13 +0200, where I
> live), Mica Mijatovic wrote:
Anyway, what is this prep.sh?
>>> #!/bin/sh
>>> # reset.sh brings ev
Hello fellow gpg users..
I have a revoker on my key that i would like to remove, but i cant find a way to
do this. Can anyone help?
another question.
When i sign a key, is there any way i can set an expiration time for
the signature?
When i use the --list-sig command, is there any way i can see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 27 May 2006 21:13:15 +0200GMT (27-5-2006, 21:13 +0200, where I
live), Mica Mijatovic wrote:
>>> Anyway, what is this prep.sh?
>> #!/bin/sh
>> # reset.sh brings everything back to CVS state ( bare bones )
>> ./reset.sh
>> ./scripts/autogen
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Was Sat, 27 May 2006, at 20:27:44 +0200,
when Henk wrote:
> On Fri, 26 May 2006 15:21:50 -0400GMT (26-5-2006, 21:21 +0200, where I
> live), Joe Smith wrote:
>>> configure: creating ./config.status
>>> config.status: creating
>>> .infig.s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 26 May 2006 15:21:50 -0400GMT (26-5-2006, 21:21 +0200, where I
live), Joe Smith wrote:
>> configure: creating ./config.status
>> config.status: creating
>> .infig.status: error: cannot find input file:
> ".infig.status" ? That looks like a
[EMAIL PROTECTED] wrote:
>symmetrically encrypted message when the cipher algo is set to
>anything else besides IDEA in Disastry's version,
>and 1.4.3 also cannot, and 'assumes' IDEA is used, and upon
>decryption,
I'll try to test this. You'll have to explicitly state the encryption algo
used
On Saturday 27 May 2006 02:21, markus reichelt wrote:
> > [EMAIL PROTECTED]: gpg bigfile.pgp
> > gpg: fatal: zlib inflate problem: invalid block type
> > secmem usage: 1920/3872 bytes
>
> Have you tried redirection?
>
> gpg < bigfile.pgp > bigfile
>
> Using redirection is the correct way of handlin
