-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Wednesday 24 July 2019 at 2:36:36 AM, in
, vedaal via
Gnupg-users wrote:-
> but for the default size GnuPG key of 4096,
The default key size is 2048. That is the size generated if you use
the --quick-generate-key command.
- --
Best regard
Hi everyone,
First, please allow me to define a bit of ad-hoc
nomenclature. I will use the uppercase tems "ENCRYPT",
"ENCRYPTION", etc. as shorthands for "compress and
AES256-encrypt", "compression and AES256 encryption", etc.
Likewise, I will use "DECRYPT", etc. as shorthands for
"[AES256] decry
Hi!
The GnuPG documentation refers to an "INTEROPERABILITY WITH
OTHER OPENPGP PROGRAMS section", but when I search for this
title, I find only references to it, not the actual section.
Does any one know where that section is?
Thank you in advance,
kj
> First, please allow me to define a bit of ad-hoc
> nomenclature. I will use the uppercase tems "ENCRYPT",
> "ENCRYPTION", etc. as shorthands for "compress and
> AES256-encrypt", "compression and AES256 encryption", etc.
> Likewise, I will use "DECRYPT", etc. as shorthands for
> "[AES256] decrypt
On Thu 2019-07-25 14:00:08 -0400, Kynn Jones via Gnupg-users wrote:
> The GnuPG documentation refers to an "INTEROPERABILITY WITH
> OTHER OPENPGP PROGRAMS section", but when I search for this
> title, I find only references to it, not the actual section.
>
> Does any one know where that section is?
@Daniel : thanks!!!
On Thu, Jul 25, 2019 at 4:11 PM Daniel Kahn Gillmor
wrote:
> On Thu 2019-07-25 14:00:08 -0400, Kynn Jones via Gnupg-users wrote:
> > The GnuPG documentation refers to an "INTEROPERABILITY WITH
> > OTHER OPENPGP PROGRAMS section", but when I search for this
> > title, I find
On Thu, Jul 25, 2019 at 3:26 PM Robert J. Hansen
wrote:
> > First, please allow me to define a bit of ad-hoc
> > nomenclature. I will use the uppercase tems "ENCRYPT",
> > "ENCRYPTION", etc. as shorthands for "compress and
> > AES256-encrypt", "compression and AES256 encryption", etc.
> > Likewi
> Pardon my ignorance, but I gather from this example that I would have
> to manage not only passphrases but also iv's as well? (That would add
> to my work's complexity.)
An AES256 key is only 32 bytes long; an IV, only 16. Keeping track of
48 bytes to decrypt your files isn't exactly a lot. Y
