You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add --config-file to `serve`
* use viper to support env var and config file
* properly integrate viper with cobra
* add viper
* slightly better error message
* set default option for --server-config-output
* show config file option in configure output
* add powershell command to the output
* Tidy go.mod
* Update docs and demo for new env arguments
---------
Co-authored-by: Luke Rindels <lrindels@pm.me>
Copy file name to clipboardExpand all lines: README.md
+19-10Lines changed: 19 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ In this diagram, the client has generated and installed a WireGuard configuratio
17
17
1. Download binaries from the [releases](https://github.com/sandialabs/wiretap/releases) page, one for your client machine and one for your server (if different os/arch)
18
18
2. Run `./wiretap configure --port <port> --endpoint <socket> --routes <routes>` with the appropriate arguments
19
19
3. Import the resulting `wiretap.conf` file into WireGuard on the client machine
20
-
4. Copy and paste the arguments output from the configure command into Wiretap on the server machine
20
+
4. Copy and paste the server command output that best suits your target system into Wiretap on the server machine
21
21
22
22
## Requirements
23
23
@@ -62,20 +62,25 @@ Following the example in the diagram:
62
62
Configuration successfully generated.
63
63
Import the config into WireGuard locally and pass the arguments below to Wiretap on the remote machine.
There are two other ways to pass arguments to the server:
102
+
1. With a config file: `-f wiretap_server.conf`
103
+
2. The legacy method of passing command line arguments (`--endpoint 1.3.3.7:1337 ...`). Be aware that this method exposes arguments to other users on the system. Compromising the private key could allow someone to connect to the client as a peer and/or decrypt traffic
95
104
96
105
Confirm that the client and server have successfully completed the handshake. The client should see a successful handshake in whatever WireGuard interface is running. If using the command-line tools, check with `wg show`.
97
106
@@ -274,7 +283,7 @@ Configure Wiretap from the client machine. Remember, `--endpoint` is how the ser
274
283
*`--routes` needs to be the subnet of the target network: `10.2.0.0/16`. But there is also an IPv6 subnet, so we should also put `fd:2::/64`. If you just wanted to route traffic to the target host, you could put `10.2.0.4/32` here instead
cmd.Flags().StringVarP(&configureCmd.endpoint, "endpoint", "e", configureCmd.endpoint, "socket address of wireguard listener that server will connect to (example \"1.2.3.4:51820\")")
57
76
cmd.Flags().IntVarP(&configureCmd.port, "port", "p", configureCmd.port, "port of local wireguard listener")
0 commit comments