aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/DETAILS8
-rw-r--r--doc/gpg.texi10
2 files changed, 18 insertions, 0 deletions
diff --git a/doc/DETAILS b/doc/DETAILS
index 9581f3032..a3fe802a2 100644
--- a/doc/DETAILS
+++ b/doc/DETAILS
@@ -1504,6 +1504,14 @@ CREATE TABLE signatures (
- One octet with the length of the following serial number.
- The serial number. Regardless of what the length octet
indicates no more than 16 octets are stored.
+ - 3 :: The internal representation of a private key: For v4 keys we
+ first write 4 octets big endian length of the following
+ s-expression with the protected or unprotected private key;
+ for v5 keys this is not necessarily because that length
+ header is always there. The actual data are N octets of
+ s-expression. Any protection (including the real S2K) is
+ part of that data. Note that the public key aparemters are
+ repeated in th s-expression.
Note that gpg stores the GNU S2K Extension Number internally as an
S2K Specifier with an offset of 1000.
diff --git a/doc/gpg.texi b/doc/gpg.texi
index c82a4aa4d..1a3cb9e25 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -2721,6 +2721,16 @@ opposite meaning. The options are:
each record to allow diverting the records to the corresponding zone
file.
+ @item mode1003
+ Enable the use of a new secret key export format. This format
+ avoids the re-encryption as required with the current OpenPGP format
+ and also improves the security of the secret key if it has been
+ protected with a passphrase. Note that an unprotected key is
+ exported as-is and thus not secure; the general rule to convey
+ secret keys in an OpenPGP encrypted file still applies with this
+ mode. Versions of GnuPG before 2.4.0 are not able to import such a
+ secret file.
+
@end table
@item --with-colons