denozord/strongswan-ext
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove obsolete pluto smartcard syntax in ipsec.secrets.5

Browse Source
This commit is contained in:
Martin Willi
2012-10-24 13:07:53 +02:00
parent f6d8fb3687
commit cd844e1c97
1 changed files with 5 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/ipsec.secrets.5.in
+5 -8
View File
@@ -155,14 +155,11 @@ The format of \fIsecret\fP is the same as that of \fBPSK\fP secrets.
The format of \fIpassword\fP is the same as that of \fBPSK\fP secrets. The format of \fIpassword\fP is the same as that of \fBPSK\fP secrets.
\fBXAUTH\fP secrets are IKEv1 only. \fBXAUTH\fP secrets are IKEv1 only.
.TP .TP
.B : PIN <smartcard selector> <pin code> | %prompt .B : PIN %smartcard[<slot nr>[@<module>]]:<keyid> <pin code> | %prompt
IKEv1 uses the format The smartcard selector always requires a keyid to uniquely select the correct
.B "%smartcard[<slot nr>[:<key id>]]" key. The slot number defines the slot on the token, the module name refers to
to specify the smartcard selector (e.g. %smartcard1:50). the module name defined in strongswan.conf(5).
The IKEv2 daemon supports multiple modules with the format Instead of specifying the pin code statically,
.B "%smartcard[<slot nr>[@<module>]]:<keyid>"
, but always requires a keyid to uniquely select the correct key. Instead of
specifying the pin code statically,
.B %prompt .B %prompt
can be specified, which causes the daemons to ask the user for the pin code. can be specified, which causes the daemons to ask the user for the pin code.
.LP .LP