18d321f061c842459197134bd316f226af184e27
howto/IPsecWithPublicKeys.md
| ... | ... | @@ -35,7 +35,7 @@ Different implementations use different formats to represent public keys, and it |
| 35 | 35 | ### How-To examples |
| 36 | 36 | | Implementation | Key format | |
| 37 | 37 | | :------------------ | --------------: | |
| 38 | -| Cisco IOS | Hexadecimal DER | |
|
| 38 | +| [Cisco IOS][a] | Hexadecimal DER | |
|
| 39 | 39 | | IPsec-Tools | Base64 RFC 3110 | |
| 40 | 40 | | Mikrotik RouterOS | PEM | |
| 41 | 41 | | OpenBSD | PEM | |
| ... | ... | @@ -43,6 +43,8 @@ Different implementations use different formats to represent public keys, and it |
| 43 | 43 | | strongSwan >= 5.0.0 | PEM | |
| 44 | 44 | | Vyatta/VyOS/EdgeOS | Base64 RFC 3110 | |
| 45 | 45 | |
| 46 | +[a]: /howto/IPsecWithPublicKeys/CiscoIOSExample |
|
| 47 | + |
|
| 46 | 48 | ### Notes |
| 47 | 49 | 1. Best practice is to generate the private key on the router itself, and not transfer it to another machine. This part should be kept secret! |
| 48 | 50 | 2. Some implementations support more than one key format. The examples here only show how to use one of them (usually PEM) for brevity. |
| ... | ... | \ No newline at end of file |