oysteikt/heimdal
0
0
Fork 0
Code Issues 5 Pull Requests Releases Activity

language.

Browse Source 
git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@17941 ec53bebd-3082-4978-b11e-865c3cabbd6b
This commit is contained in:
Love Hörnquist Åstrand
2006-08-25 10:16:45 +00:00
parent 8a996b0fac
commit 697f1cfa22
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/setup.texi
View File

@@ -1182,23 +1182,25 @@ Its useful to have one PEM file that contains all the trust anchors.
Syntax is:
@example
FILE:certificate-file.pem,private-key-file.key,other-cert.pem,....
FILE:certificate.pem,private-key.key,other-cert.pem,....
@end example
@item PKCS11:
PKCS11: is used handle smartcards via PKCS11 drivers
(soft-token,opensc,muscle) files.
PKCS11: is used handle smartcards via PKCS11 drivers, for example
soft-token opensc, or muscle. Default is to use all slots on the
device/token.
Syntax is:
@example
PKCS11:shared-object.so:slot=<num>:otherattribute=<value>
PKCS11:shared-object.so
@end example
@item PKCS12:
PKCS12: is used handle PKCS12 (.pfx/.p12) files.
PKCS12: is used handle PKCS12 files. PKCS12 files commonly have the
extension pfx or p12.
Syntax is:
@@ -1210,8 +1212,6 @@ PKCS12:/path/to/file.pfx
@section Configure the Kerberos software
Write about configuration options to krb5.conf.
First configure the client's trust anchors and what parameters to
verify, see subsection below how to do that. Now you can use kinit to
get yourself tickets. One example how that can look it like this: