On 2005-03-15 00:13:22 +0100, Marcus Frings wrote:
> Sorry for the misunderstanding, my problem was that I wasn't aware
> of the new option "tsign" which is new in 1.4.0. After reading the
> info about "tsign" in the manpage I understand the difference now.
I went looking for this too, and found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Servie Platon wrote:
> Hi folks,
>
> I got this error message after I issued the command
> shown below:
>
>
> gpg: invalid module `Lib\idea': The specified module
> could not be found.
>
> Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256,
> TWOF
Hi folks,
I got this error message after I issued the command
shown below:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\servie>gpg --version
gpg (GnuPG) 1.4.0
Copyright (C) 2004 Free Software Foundation, Inc.
This program comes with A
Hello,
see this:
,
| [00:[EMAIL PROTECTED]:~]$ gpg --set-policy-url
http://www.sc-delphin-eschweiler.de/pgp/ --ask-cert-level --sign-key 82F61240
|
| pub 1024D/82F61240 created: 2004-10-22 expires: 2010-10-21 usage: CS
| trust: unknown validity: undefined
|
* David Shaw <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 10, 2005 at 01:04:20PM +0100, Marcus Frings wrote:
>> First of all, what is actually the difference between "pgp" and
>> "classic"? The first option tells about WOT and trust signatures but the
>> latter just mentions the WOT.
> That is the di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
i am seeking for a well written German book about gnupg. Is there any
book 'bout it?
thx
~ ny
- --
- -
Rainer Bendig aka "Ny" | http://www.moins.de | GnuPG-Key 0x41D44F10
Given the following example of an ASCII Armored Message in section 6.6
of rfc2440bis-12: (Note I removed the leading two blanks from each line)
-BEGIN PGP MESSAGE-
Version: OpenPrivacy 0.99
yDgBO22WxBHv7O8X7O/jygAEzol56iUKiXmV+XmpCtmpqQUKiQrFqclFqUDBovzS
vBSFjNSiVHsuAA==
=njUN
-END PGP
On Mon, 14 Mar 2005 05:02:21 -0600, John Clizbe said:
> I don't know that "extended the standard" is the language I'd use. More to
> the point would be "second guessed the IETF OpenPGP WG". Did they even
> meet at last week's IETF meeting? The current draft, rfc2440bis-12,
> expires in May of this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan Wevers wrote:
> Hello,
>
> Now that PGP 9 beta seems to have extended the standard to allow non-160 bit
> hashes to be used with DSA keys, isn't it time for GnuPG to do the same,
> especially after the recent attacks on SHA-1? I know it's agains
On Mon, 14 Mar 2005 19:19:43 +0900, Kory T said:
> the list know whether it's possible to import off-card generated keys
> into OpenPGP Card which are larger than 1024bits? I now know that the
> card is only capable of 'generating' 1024bit keys on the card, but
> there should be enough space to s
On Sun, 13 Mar 2005 15:17:01 +0100 (MET), Johan Wevers said:
> Now that PGP 9 beta seems to have extended the standard to allow non-160 bit
> hashes to be used with DSA keys, isn't it time for GnuPG to do the same,
Their beta seems to use a truncated hash; it is not intended
behaviour.
> And whi
Thanks for the help Robert.
That HOWTO was very helpful. I hope more documentation like this will
pop up on the net. It's been really hard to find info on the OpenPGP
card implementation.
I've been searching around the net for an answer to whether it's
possible to use large keys on smartca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maj. Dennis Bludnok, Ret. wrote:
> Thanks for the help so far everyone.
> I've been able to download the new version from a different network.
> I think the firewall at my office doesn't like FTP sites.
>
> My other question was:
> Is the old version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the help so far everyone.
I've been able to download the new version from a different network.
I think the firewall at my office doesn't like FTP sites.
My other question was:
Is the old version I have at the moment vulnerable to any att
14 matches
Mail list logo