On Sat, Jun 16, 2012 at 05:32:36PM -0400, David Shaw wrote:
Yes, I understand that spreading out keyserver requests can help avoid this
sort of tracking, but remember that the keyserver URL feature allows the
keyholder to bypass the keyserver chosen by the user, and send the requests
On Sat, 16 Jun 2012 22:42, papill...@gmail.com said:
For some reason, every time I do anything to an encrypted message, I
have to re-enter my passphrase. If I open a message, I enter my
passphrase, then, when I reply to it, I have to enter it again. And to
send that reply? Yep, enter it
On Sat, 16 Jun 2012 22:06, papill...@gmail.com said:
git clone git://git.gnupg.org/gnupg.git
Is the server down?
No. I had to restart the server for maintenance reasons and forgot to
check the git daemon. Sorry.
For unknown reason it was not in the runlevel.conf. Started git-daemon
and
I see that --edit-key pref lists out preferences. I'm assuming the first S is
default cipher, first H is default algo, etc? so if a key is generated it will
use the first S, first H, etc. But why are all those other S and H options
listed? when would they ever be used to create keys?
Lastly,
On Sat, Jun 16, 2012 at 07:54:46PM +0200, Hauke Laging wrote:
Are these files huge? It's hard for me to believe that this takes seconds.
What I would easily believe is that the system gets an entropy problem. The
delay would not be related to CPU performance then. So maybe a hardware RNG
On Jun 17, 2012, at 9:16 AM, Sam Smith wrote:
I see that --edit-key pref lists out preferences. I'm assuming the first S
is default cipher, first H is default algo, etc? so if a key is generated it
will use the first S, first H, etc. But why are all those other S and H
options listed?
Curious as to why the encryption standard AES is not used to encrypt secret
keys for GPG?
It appears users have the option to use AES for sec key encryption, but it's
not default. Do people generally change the cipher to AES when generating their
secret key?
On 06/17/2012 11:56 AM, Sam Smith wrote:
Curious as to why the encryption standard AES is not used to encrypt
secret keys for GPG?
Because GnuPG predates AES. When GnuPG 1.0 came out AES has yet to be
invented. CAST5-128 was the choice back then, and nobody's changed it
yet -- at least
Am So 17.06.2012, 08:04:09 schrieb Aaron Toponce:
These files are about 200KB in size. We have a Perl script that handles the
encryption/decryption for us. It could be the RNG slowing the process down.
I won't disagree with that, but each time I need to encrypt the file, it
takes about 2s.
On 17/06/12 19:26, Hauke Laging wrote:
start cmd: time gpg --encrypt --sign 200k-file
Sie benötigen eine Passphrase, um den geheimen Schlüssel zu entsperren.
Benutzer: Hauke Laging ha...@laging.de
2048-Bit RSA Schlüssel, ID 0x3A403251, erzeugt 2010-03-04 (Hauptschlüssel-ID
0xECCB5814)
On Jun 17, 2012, at 7:36 AM, Michel Messerschmidt wrote:
On Sat, Jun 16, 2012 at 05:32:36PM -0400, David Shaw wrote:
Yes, I understand that spreading out keyserver requests can help avoid this
sort of tracking, but remember that the keyserver URL feature allows the
keyholder to bypass the
Doesn't the IETF openPGP standard call for 256-bit key for TWOFISH?
Could someone verify that the TWOFISH cipher uses 256-bit key length in GnuPG?
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
On Jun 17, 2012, at 4:13 PM, Sam Smith wrote:
Doesn't the IETF openPGP standard call for 256-bit key for TWOFISH?
Could someone verify that the TWOFISH cipher uses 256-bit key length in GnuPG?
Yes.
See section 9.2 of RFC-4880 for confirmation.
David
On 6/17/2012 7:10 AM, Werner Koch wrote:
On Sat, 16 Jun 2012 22:42, papill...@gmail.com said:
For some reason, every time I do anything to an encrypted message, I
have to re-enter my passphrase. If I open a message, I enter my
passphrase, then, when I reply to it, I have to enter it again.
On 06/17/2012 01:26 PM, Hauke Laging wrote:
start cmd: time gpg --encrypt --sign 200k-file
Unless you're testing with 50 certificates, this isn't exactly a fair
comparison. Here's what I came up with:
System: Intel i7-2600K @ 3.4GHz, 32Gb RAM
Methodology:
* A 256k random file was
Hello,
has there already been a discussion about it whether it would make sense to
have conditional entries in the gpg config file (like e.g. SSH for different
destinations)?
Depending on the key to which is encrypted, the key by which is signed and
maybe even the application which calls gpg
16 matches
Mail list logo