diff options
| author | Werner Koch <wk@gnupg.org> | 2004-02-13 13:40:54 +0100 |
|---|---|---|
| committer | Werner Koch <wk@gnupg.org> | 2004-02-13 13:40:54 +0100 |
| commit | e98b7a9b21bcc33a35a0e17df722a8773fc670aa (patch) | |
| tree | 7a5a82832eae3c06e6a1a2ef3273f1fb191352d5 | |
| parent | * encrypt.c (init_dek): Check for too weak algorithms. (diff) | |
| download | gnupg2-e98b7a9b21bcc33a35a0e17df722a8773fc670aa.tar.xz gnupg2-e98b7a9b21bcc33a35a0e17df722a8773fc670aa.zip | |
Require libksba 0.9.4 and libgcrypt 1.1.92.
| -rw-r--r-- | ChangeLog | 4 | ||||
| -rw-r--r-- | NEWS | 4 | ||||
| -rw-r--r-- | README | 16 | ||||
| -rw-r--r-- | TODO | 3 | ||||
| -rw-r--r-- | configure.ac | 4 |
5 files changed, 17 insertions, 14 deletions
@@ -1,3 +1,7 @@ +2004-02-13 Werner Koch <wk@gnupg.org> + + * configure.ac: Require libksba 0.9.4 and libgcrypt 1.1.92. + 2004-02-12 Werner Koch <wk@gnupg.org> * autogen.sh: Removed cruft from debugging. @@ -5,6 +5,10 @@ Noteworthy changes in version 1.9.5 Cleaned up the build system to better comply with the coding standards. + * The --import command is now able to autodetect pkcs#12 files and + import secret and private keys from this file format. + + Noteworthy changes in version 1.9.4 (2004-01-30) ------------------------------------------------ @@ -452,16 +452,12 @@ Some of the search modes are not yet implemented ;-) HOW TO IMPORT A PRIVATE KEY =========================== There is some limited support to import a private key from a PKCS-12 -file. Note, that this does only import the private key and not any -certificates available in that file. +file. - gpgsm --call-protect-tool --p12-import --store foo.p12 + gpgsm --import foo.p12 + +This require that the gpg-agent is running. -This require that the gpg-agent is running, alternative you may give -the passphrase on the commandline using the option "-P <passphrase>" - -however this is in general not a good idea. If that key already -exists, the protect-tool refuses to store it unless you use the option -"--force". HOW TO EXPORT A PRIVATE KEY =========================== @@ -474,13 +470,13 @@ format. However the certificate is not stored and there is no MAC applied. SMARTCARD INTRO =============== -GPG, the OpenPGP implementation supports the OpenPGP smartcard +GPG, the OpenPGP part of GnuPG, supports the OpenPGP smartcard (surprise!); see http://g10code.com/p-card.html. [Fixme: We need to explain this further] -GPGSM, the CMS (S/MIME) implementation supports two kinds of +GPGSM, the CMS (S/MIME) part of GnuPG, supports two kinds of smartcards. The most flexible way is to use PKCS#15 compliant cards, however you must have build GnuPG with support for the OpenSC library. The build process automagically detects the presence of this library @@ -64,8 +64,7 @@ might want to have an agent context for each service request Remove the agent_reset_scd kludge. * agent/protect-tool.c -** Export and import certificates along with the secret key. -** Make it more comfortable; i.e. copy files to the correct place. +** Export certificates along with the secret key. ** BUG? --p12-export seems to work only with unprotected keys * Move pkcs-1 encoding into libgcrypt. diff --git a/configure.ac b/configure.ac index 6b8c1994d..1faf753c0 100644 --- a/configure.ac +++ b/configure.ac @@ -30,9 +30,9 @@ AC_INIT(gnupg, 1.9.5-cvs, gnupg-devel@gnupg.org) # sufficient. development_version=yes NEED_GPG_ERROR_VERSION=0.6 -NEED_LIBGCRYPT_VERSION=1.1.91 +NEED_LIBGCRYPT_VERSION=1.1.92 NEED_LIBASSUAN_VERSION=0.6.3 -NEED_KSBA_VERSION=0.9.3 +NEED_KSBA_VERSION=0.9.4 NEED_OPENSC_VERSION=0.8.0 |