mirror of
https://github.com/strongswan/strongswan.git
synced 2025-11-27 00:00:29 -05:00
man: Update description of the esp keyword
Clarifies how DH groups are applied, updates the proposal selection description and ESN can now also be configured for IKEv1. References #1039.
This commit is contained in:
parent
fe4ed4578f
commit
bbd4620777
@ -247,7 +247,9 @@ can be added at the end.
|
|||||||
If
|
If
|
||||||
.B dh-group
|
.B dh-group
|
||||||
is specified, CHILD_SA/Quick Mode setup and rekeying include a separate
|
is specified, CHILD_SA/Quick Mode setup and rekeying include a separate
|
||||||
Diffie-Hellman exchange.
|
Diffie-Hellman exchange (refer to the
|
||||||
|
.B esp
|
||||||
|
keyword for details).
|
||||||
.TP
|
.TP
|
||||||
.BR also " = <name>"
|
.BR also " = <name>"
|
||||||
includes conn section
|
includes conn section
|
||||||
@ -410,18 +412,27 @@ exclamation mark
|
|||||||
can be added at the end.
|
can be added at the end.
|
||||||
|
|
||||||
.BR Note :
|
.BR Note :
|
||||||
As a responder the daemon accepts the first supported proposal received from
|
As a responder, the daemon defaults to selecting the first configured proposal
|
||||||
the peer. In order to restrict a responder to only accept specific cipher
|
that's also supported by the peer. This may be changed via
|
||||||
suites, the strict flag
|
.BR strongswan.conf (5)
|
||||||
|
to selecting the first acceptable proposal sent by the peer instead. In order to
|
||||||
|
restrict a responder to only accept specific cipher suites, the strict flag
|
||||||
.RB ( ! ,
|
.RB ( ! ,
|
||||||
exclamation mark) can be used, e.g: aes256-sha512-modp4096!
|
exclamation mark) can be used, e.g: aes256-sha512-modp4096!
|
||||||
.br
|
|
||||||
If
|
If
|
||||||
.B dh-group
|
.B dh-group
|
||||||
is specified, CHILD_SA/Quick Mode setup and rekeying include a separate
|
is specified, CHILD_SA/Quick Mode rekeying and initial negotiation use a
|
||||||
Diffie-Hellman exchange. Valid values for
|
separate Diffie-Hellman exchange using the specified group. However, for IKEv2,
|
||||||
|
the keys of the CHILD_SA created implicitly with the IKE_SA will always be
|
||||||
|
derived from the IKE_SA's key material. So any DH group specified here will only
|
||||||
|
apply when the CHILD_SA is later rekeyed or is created with a separate
|
||||||
|
CREATE_CHILD_SA exchange. Therefore, a proposal mismatch might not immediately
|
||||||
|
be noticed when the SA is established, but may later cause rekeying to fail.
|
||||||
|
|
||||||
|
Valid values for
|
||||||
.B esnmode
|
.B esnmode
|
||||||
(IKEv2 only) are
|
are
|
||||||
.B esn
|
.B esn
|
||||||
and
|
and
|
||||||
.BR noesn .
|
.BR noesn .
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user