security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-03 22:56:33 +02:00
Code Activity

Require libksba 0.9.4 and libgcrypt 1.1.92.

Browse source
This commit is contained in:
Werner Koch 2004-02-13 12:40:54 +00:00
parent 1a159fd8e3
commit e98b7a9b21
5 changed files with 17 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

16
README
View file

@ -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