From: Martin Willi <martin@revosec.ch>
Date: Wed, 17 Oct 2012 13:53:44 +0000 (+0200)
Subject: Remove obsolete pluto smartcard syntax in ipsec.secrets.5
X-Git-Tag: 5.0.2dr4~286
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=cd844e1c97be895e2169caf959f38d2c52acc46c;p=thirdparty%2Fstrongswan.git

Remove obsolete pluto smartcard syntax in ipsec.secrets.5
---

diff --git a/man/ipsec.secrets.5.in b/man/ipsec.secrets.5.in
index aa1b5c9c1d..2e58db1e1c 100644
--- a/man/ipsec.secrets.5.in
+++ b/man/ipsec.secrets.5.in
@@ -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.
 \fBXAUTH\fP secrets are IKEv1 only.
 .TP
-.B : PIN <smartcard selector> <pin code> | %prompt
-IKEv1 uses the format
-.B "%smartcard[<slot nr>[:<key id>]]"
-to specify the smartcard selector (e.g. %smartcard1:50).
-The IKEv2 daemon supports multiple modules with the format
-.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 : PIN %smartcard[<slot nr>[@<module>]]:<keyid> <pin code> | %prompt
+The smartcard selector always requires a keyid to uniquely select the correct
+key. The slot number defines the slot on the token, the module name refers to
+the module name defined in strongswan.conf(5).
+Instead of specifying the pin code statically,
 .B %prompt
 can be specified, which causes the daemons to ask the user for the pin code.
 .LP