On Thu, 12 Mar 2015 11:08, p...@heypete.com said:
> I (perhaps incorrectly) interpreted the question as "If GnuPG makes
> backwards-incompatible changes in the future, would it be possible for
> one who knows the encryption algorithm used, key, etc. of a message to
> decrypt that message with othe
On Thu, Mar 12, 2015 at 10:56 AM, Werner Koch wrote:
> On Wed, 11 Mar 2015 20:39, p...@heypete.com said:
>
>>> One more question: Is there any standardization in output formats
>>> between encryption programs and libraries, for example say you encrypt
>>> with AES128 in CBC, with the same key (dir
On Wed, 11 Mar 2015 20:39, p...@heypete.com said:
>> One more question: Is there any standardization in output formats
>> between encryption programs and libraries, for example say you encrypt
>> with AES128 in CBC, with the same key (directly or via passphrase), and
>> since the output will have
s of asymmetric encryption?Thank you for your help.
From: Peter Lebbing
To: Maricel Gregoraschko ; Gnupg-users
Sent: Wednesday, March 11, 2015 3:06 PM
Subject: Re: AES-NI, symmetric key generation
On 11/03/15 18:55, Maricel Gregoraschko wrote:
> One more question: Is there any
On 3/11/2015 6:55 PM, Maricel Gregoraschko wrote:
> Thank you Pete for clearing things up. Makes a lot of sense to store
> passphrase-to-key identification data, in addition to actual algorithm
> used, in the output message rather than have the decryptor just assume
> things.
Indeed. The folks who
On 11/03/15 18:55, Maricel Gregoraschko wrote:
> One more question: Is there any standardization in output formats
> between encryption programs and libraries, for example say you
> encrypt with AES128 in CBC, with the same key (directly or via
> passphrase), and since the output will have to have
s!
From: Pete Stephenson
To: Maricel Gregoraschko ;
gnupg-users@gnupg.org
Sent: Tuesday, March 10, 2015 5:32 PM
Subject: Re: AES-NI, symmetric key generation
On 3/10/2015 8:28 PM, Maricel Gregoraschko wrote:
> Pete,
> Very useful info about using --show-session-key to avoid rev
> Thanks Vedaal, yep that would be one mighty strong password!
It's also way overkill. :)
"gpg --armor --gen-rand 1 16" will produce a (relatively) short
passphrase suitable for pretty much any imaginable usage. 128 shannons
of entropy's nothing to sneeze at.
__
Thanks Vedaal, yep that would be one mighty strong password!
From: "ved...@nym.hush.com"
To: Maricel Gregoraschko ;
gnupg-users@gnupg.org
Sent: Tuesday, March 10, 2015 4:42 PM
Subject: Re: AES-NI, symmetric key generation
On 3/10/2015 at 4:19 PM, "Maricel Gregor
On Tue, 10 Mar 2015 20:33, maricelgregorasc...@yahoo.com said:
> I admit I haven't looked at the AES-NI instruction set, but I've read
> that it could be easy for the CPU to reconstruct the key from a
Possible. It is also easy to detect the instructions used for software
based AES keyscheduling
On 3/10/2015 8:28 PM, Maricel Gregoraschko wrote:
> Pete,
> Very useful info about using --show-session-key to avoid revealing your
> private asymmetric key.
No worries.
> In your example ("gpg --show-session-key < example.txt") , had you
> somehow set up gpg to use symmetric by default, rather t
On Tue, 10 Mar 2015 20:39, maricelgregorasc...@yahoo.com said:
> Thanks Werner.On Windows, you mean on each drive letter, in the root
> directory? (e.g. c:\hwf.deny, d:\hwf.deny, etc.?).Also would there be
Yes, that was the idea. The file names should however be
c:\etc\gcrypt\hwf.deny
d:\etc
On 3/10/2015 at 4:19 PM, "Maricel Gregoraschko"
wrote:
>I agree, using key instead of passphrase doesn't enhance security
>(assuming an attacker knows that the key was derived from a
>passphrase and with what key derivation algorithm? I assume the
>randomness/entropy of the key itself is high
had an effect)?
Thank you.
From: Werner Koch
To: Andre Heinecke
Cc: gnupg-users@gnupg.org; Maricel Gregoraschko
Sent: Tuesday, March 10, 2015 10:58 AM
Subject: Re: AES-NI, symmetric key generation
On Tue, 10 Mar 2015 10:05, aheine...@intevation.de said:
>> Also is the
on/decryption (I think implementations even use
Intel-provided code), and store it for later retrieval through a secret CPU
instruction set. From: Andre Heinecke
To: gnupg-users@gnupg.org; Maricel Gregoraschko
Sent: Tuesday, March 10, 2015 5:05 AM
Subject: Re: AES-NI, symmetric key gene
upg.org
Sent: Tuesday, March 10, 2015 10:36 AM
Subject: Re: AES-NI, symmetric key generation
On 3/9/2015 6:15 PM, Maricel Gregoraschko wrote:
> Hello All,
Hi!
> 2. When using symmetric encryption and providing a passphrase, I
> understand the actual encryption key is generated on
On 3/9/2015 6:15 PM, Maricel Gregoraschko wrote:
> Hello All,
Hi!
> 2. When using symmetric encryption and providing a passphrase, I
> understand the actual encryption key is generated on the spot, used to
> do the encryption, and then discarded from memory and not stored
> anywhere, is that cor
On Tue, 10 Mar 2015 10:05, aheine...@intevation.de said:
>> Also is there any
>> option to turn hardware acceleration on or off at runtime?
You can globally disable certain hardware features: Create a file
--8<---cut here---start->8---
# We do not want to use
Hi,
To answer your first question regarding gpg4win:
On Monday, March 09, 2015 05:15:14 PM Maricel Gregoraschko wrote:
> Hello All,I would first like to thank you for your effort and time
> developing gnupgp.I have a couple of questions: 1. Does GnuGP (in
> particular, the Windows binaries distri
Hello All,I would first like to thank you for your effort and time developing
gnupgp.I have a couple of questions:
1. Does GnuGP (in particular, the Windows binaries distributed for gpg4win) use
AES-NI, the Intel dedicated AES instruction set? There are some concerns, I'm
not sure how realistic,
20 matches
Mail list logo
