Re: Import private key from PEM file?

On Tue, 19 Jun 2012 05:43, quanngu...@mbm.vn said: > (Maybe you forgot that I asked 2 questions in the first email No. >> p.s. >> Maybe http://gnupg.org/service.html is of help to you. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

VIA padlock (was: Re: GPG with GPUs)

On 18/06/12 20:39, Werner Koch wrote: > FWIW, Libgcrypt uses this RNG directly in addition to other sources. Actually... I just checked git.gnupg.org, and I see these lines in Libgcrypt, file random/rndhw.c: # if defined (__i386__) && SIZEOF_UNSIGNED_LONG == 4 && defined (__GNUC__) # define USE_P

Re: VIA padlock

On Tue, 19 Jun 2012 10:55, pe...@digitalbrains.com said: > I'm running x86_64: the VIA Nano is a 64-bits processor. So I think Libgcrypt > doesn't recognise it can use the padlock from the VIA Nano. I have a patch in the queue and even a woodware note at my monitor. Shalom-Salam, Werner --

Re: way to see what cipher/algo was used to create your key?

gnupg-users-boun...@gnupg.org wrote on 06/19/2012 01:50:04 AM: > - Message from Sam Smith on Mon, 18 Jun > 2012 19:30:44 -0400 - > > To: > > Gnupg > > Subject: > > RE: way to see what cipher/algo was used to create your key? > > Does anybody know a way to learn what cipher & hash wa

Re: way to see what cipher/algo was used to create your key?

Am Di 19.06.2012, 09:05:41 schrieb michaelquig...@theway.org: > The details file documents using the --list-keys command with the and > specifying the --with-fingerprint option twice. This produces a list > which shows the algorithm used for the key. This can also be used with > the --list-secre

Re: decryption trouble - primary/subkey confusion, maybe version issues?

On Jun 19, 2012, at 1:50 AM, Hauke Laging wrote: > Am Di 19.06.2012, 01:03:26 schrieb Michael Hannemann: > >> pub:f:1024:17:xx--TpTpTpTp:1999-04-08:::-:[my collaborator]::scaESCA: >> sub:f:2048:16:xx--TsTsTsTs:1999-04-08::e: > > This seems not to leave any room for ambiguity: One ke

way to see what cipher/algo was used to create your key?

Sam Smith smickson at hotmail.com wrote on: Tue Jun 19 01:30:44 CEST 2012 >a way to learn what cipher & hash was used to create the secret key? export your secret key as seckey.asc then do gpg --list-packets seckey.asc here is an example of one of mine: V:\z\>gpg --list-packets v:\seckey.a

Re: way to see what cipher/algo was used to create your key?

On 06/19/2012 01:50 PM, ved...@nym.hush.com wrote: > (btw, Should a listing explaining these things be in the FAQ ? ) I won't put it in there. Once you open the door to that, then you have to answer questions about "so how do I change these settings?" and then you're explaining half of the edit-k

Re: way to see what cipher/algo was used to create your key?

On Tue, 19 Jun 2012 19:50, ved...@nym.hush.com said: > (all current gnupg keys are v4, older keys from pgp were v3, maybe > when elliptic curve crypto gets done, there might be a v5 ;-) ) 2.1beta has ECC support as described by RFC6637. Still using v4. Shalom-Salam, Werner -- Die Gedan

Re: Import private key from PEM file?

Thanks for your help. On Tue, Jun 19, 2012 at 2:25 PM, Werner Koch wrote: > On Tue, 19 Jun 2012 05:43, quanngu...@mbm.vn said: > > > (Maybe you forgot that I asked 2 questions in the first email > > No. > > >> p.s. > >> Maybe http://gnupg.org/service.html is of help to you. > > > Salam-Shalom, >

idea.dll

Hello. When I had a 32-bit version of Windows XP, I was able to utilize both the newer version of Gpg 2.0.X and the older 1.4.X version of it at the same time, and I would like to do the same thing now that I have a 64-bit version of Win7. I have installed the newer version, as well as the GPA