-
Notifications
You must be signed in to change notification settings - Fork 380
T8136: IPSEC PPK Support #1733
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: current
Are you sure you want to change the base?
T8136: IPSEC PPK Support #1733
Conversation
| tunnels when a Post-Quantum key exchange algorithm such as ML-KEM is not | ||
| available. The use of PPKs in IKEv2 is described in :rfc:`8784`. | ||
|
|
||
| PPKs can be configued within VyOS under the vpn.ipsec.authentication.ppk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| PPKs can be configued within VyOS under the vpn.ipsec.authentication.ppk | |
| PPKs can be configued within VyOS under the `vpn ipsec authentication ppk` |
In my opinion it will be better this way.
| PPKs can be configued within VyOS under the vpn.ipsec.authentication.ppk | ||
| config. | ||
|
|
||
| .. cfgmod:: edit vpn authentication ppk <name> | ||
|
|
||
| PPKs need an id and a secret value. The ID and secret must match if PPKs are | ||
| required for a successful IPSEC connection. The secret can be plain text, a | ||
| hex value, or a base64 value. The default is plain text. If using another | ||
| type of value, you must define the secret-type. | ||
|
|
||
| .. cfgmod:: set vpn authentication ppk <name> secret-type <plaintext|hex|base64> | ||
|
|
||
| To use a PPK within a site-to-site or remote-access connection, define the PPK | ||
| id under the connection. | ||
|
|
||
| .. cfgmod:: set vpn ipsec site-to-site <name> ppk id <id> | ||
|
|
||
| Optionally, you can require the use of PPK to have a successful connection. | ||
|
|
||
| .. cfgmod:: set vpn ipsec site-to-site <name> ppk required | ||
|
|
||
| To confirm the use of a PPK in an IKE SA, check for the presence of "up-ppk" in | ||
| the output of the show command under the status heading. If you only see "up", or | ||
| "down", PPK is not in use. | ||
|
|
||
| .. cfgmod:: show vpn ike sa |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| PPKs can be configued within VyOS under the vpn.ipsec.authentication.ppk | |
| config. | |
| .. cfgmod:: edit vpn authentication ppk <name> | |
| PPKs need an id and a secret value. The ID and secret must match if PPKs are | |
| required for a successful IPSEC connection. The secret can be plain text, a | |
| hex value, or a base64 value. The default is plain text. If using another | |
| type of value, you must define the secret-type. | |
| .. cfgmod:: set vpn authentication ppk <name> secret-type <plaintext|hex|base64> | |
| To use a PPK within a site-to-site or remote-access connection, define the PPK | |
| id under the connection. | |
| .. cfgmod:: set vpn ipsec site-to-site <name> ppk id <id> | |
| Optionally, you can require the use of PPK to have a successful connection. | |
| .. cfgmod:: set vpn ipsec site-to-site <name> ppk required | |
| To confirm the use of a PPK in an IKE SA, check for the presence of "up-ppk" in | |
| the output of the show command under the status heading. If you only see "up", or | |
| "down", PPK is not in use. | |
| .. cfgmod:: show vpn ike sa | |
| .. cfgmod:: edit vpn authentication ppk <name> | |
| PPKs can be configued within VyOS under the `vpn ipsec authentication ppk` | |
| config. | |
| .. cfgmod:: set vpn authentication ppk <name> secret-type <plaintext|hex|base64> | |
| PPKs need an id and a secret value. The ID and secret must match if PPKs are | |
| required for a successful IPSEC connection. The secret can be plain text, a | |
| hex value, or a base64 value. The default is plain text. If using another | |
| type of value, you must define the secret-type. | |
| .. cfgmod:: set vpn ipsec site-to-site <name> ppk id <id> | |
| To use a PPK within a site-to-site or remote-access connection, define the PPK | |
| id under the connection. | |
| .. cfgmod:: set vpn ipsec site-to-site <name> ppk required | |
| Optionally, you can require the use of PPK to have a successful connection. | |
| .. cfgmod:: show vpn ike sa | |
| To confirm the use of a PPK in an IKE SA, check for the presence of "up-ppk" in | |
| the output of the show command under the status heading. If you only see "up", or | |
| "down", PPK is not in use. |
As I see on other pages, the command description should be after the command (not before).
alexandr-san4ez
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes I requested have been made.
Change Summary
Provides information on use of post-quantum preshared keys (PPK)
Related Task(s)
Related PR(s)
vyos/vyos-1x#4930
Backport
Checklist: