Small cleanups in man wg(8)
PATCH 1/1 Small cleanups in man wg(8)
Signed-off-by Kai Haberzettl <[email protected]>
--- src/man/wg.8 | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
src/man/wg.8 +4 -4
@@ -40,7 +40,7 @@ Sub-commands that take an INTERFACE must be passed a WireGuard interface. Shows current WireGuard configuration and runtime information of specified \fI<interface>\fP. If no \fI<interface>\fP is specified, \fI<interface>\fP defaults to \fIall\fP. If \fIinterfaces\fP is specified, prints a list of all WireGuard interfaces, -one per line, and quit. If no options are given after the interface +one per line, and quits. If no options are given after the interface specification, then prints a list of all attributes in a visually pleasing way meant for the terminal. Otherwise, prints specified information grouped by newlines and tabs, meant to be used in scripts. For this script-friendly display,
@@ -61,7 +61,7 @@ Sets configuration values for the specified \fI<interface>\fP. Multiple for a peer, that peer is removed, not configured. If \fIlisten-port\fP is not specified, or set to 0, the port will be chosen randomly when the interface comes up. Both \fIprivate-key\fP and \fIpreshared-key\fP must -be a files, because command line arguments are not considered private on +be files, because command line arguments are not considered private on most systems but if you are using .BR bash (1), you may safely pass in a string by specifying as \fIprivate-key\fP or
@@ -163,8 +163,8 @@ port number. This endpoint will be updated automatically to the most recent source IP address and port of correctly authenticated packets from the peer. Optional. .IP \(bu -PersistentKeepalive \(em a seconds interval, between 1 and 65535 inclusive, of -how often to send an authenticated empty packet to the peer for the purpose of keeping a +PersistentKeepalive \(em a seconds interval, between 1 and 65535 inclusive, how +often to send an authenticated empty packet to the peer for the purpose of keeping a stateful firewall or NAT mapping valid persistently. For example, if the interface very rarely sends traffic, but it might at anytime receive traffic from a peer, and it is behind NAT, the interface might benefit from having a persistent keepalive
Signature · 6 lines
2.20.1 _______________________________________________ WireGuard mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/wireguard
Thanks. The first two chunks seem right, but not the last one. Applied as:
https://git.zx2c4.com/wireguard-tools/commit/?id=95aa00b8846396273a4ece75de7701d11516e050
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard