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

left|rightrsasigkey accepts SSH keys but the key format has to be specified explicitly

Browse Source 
The default is now PKCS#1. With the dns: and ssh: prefixes other formats
can be selected.
This commit is contained in:
Tobias Brunner
2013-05-07 15:38:28 +02:00
parent cc4408abcb
commit fa1d3d39dc
6 changed files with 37 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/ipsec.conf.5.in
+9 -3
View File
@@ -756,9 +756,15 @@ None of the kernel backends currently supports opaque or port ranges and uses
for policy installation instead.
.TP
.BR leftrsasigkey " = <raw rsa public key> | <path to public key>"
the left participant's public key for RSA signature authentication, in RFC 2537
format using hex (0x prefix) or base64 (0s prefix) encoding. Also accepted is
the path to a file containing the public key in PEM or DER encoding.
the left participant's public key for RSA signature authentication, in PKCS#1
format using hex (0x prefix) or base64 (0s prefix) encoding. With the optional
.B dns:
or
.B ssh:
prefix in front of 0x or 0s, the public key is expected to be in either
the RFC 3110 or RFC 4253 public key format, respectively.
Also accepted is the path to a file containing the public key in PEM or DER
encoding.
.TP
.BR leftsendcert " = never | no | " ifasked " | always | yes"
Accepted values are