hyp/hypd
Steven Polley 92f5c579e6
All checks were successful
continuous-integration/drone/push Build is passing
add README.md
2024-04-25 21:21:27 -06:00
..
cmd add support for multiple secrets (independent agents) on the knock daemon 2024-04-19 22:04:00 -06:00
configuration QoL feature - select best interface on current system 2024-04-20 19:25:15 -06:00
examples add README.md 2024-04-25 21:21:27 -06:00
server Add support for timeout action 2024-04-20 15:41:26 -06:00
main.go BREAKING: changes to CLI interface, moved to cobra CLI 2024-04-10 21:42:38 -06:00
README.md QoL feature - select best interface on current system 2024-04-20 19:25:15 -06:00

hypd | Hide Your Ports Daemon

hypd is the pork knocking daemon which listens for incoming authentic knock sequences. When it sees an authentic knock sequence, it then performs an action.

Usage

You can use -h to get help for hypd and all its commands. When figuring out how to do something, -h is your friend.

# Get general hypd help
./hypd -h

# Get help specific to the hypd generate command
./hypd generate -h

Running hypd requires generating secrets which are then shared with hyp clients. hypd is used to generate these secrets, and it's recommended you create a directory just for hyp secrets.

# Example: create a directory named secrets
mkdir -p secrets

# Then generate a secret file in this directory
./hypd generate secret > secrets/my-first-secret

It's recommended you generate a secret for each trusted agent so you can granularly control revocation just by removing a secret file from the secrets directory.

Running hypd requires specifying a configuration file. It's recommended you generate the default configuration file and then edit it afterwards.

# Create a default configuration file
./hypd generate defaultconfig > hypd.conf

Make sure you take the time to review the hypd.conf file and edit it to your liking, this is the most important step. Make sure the network interface is correct, hypd will make an educated guess based on the interfaces your system has.

If you have complex requirements, you can make the successAction/timeoutAction an external shell script. If you want to disable the timeoutAction, you can set timeoutSeconds to 0.

Once you have set your config file, you can finally run hypd.

# As root or sudo, specify the configuration file
sudo ./hypd server hypd.conf

If you encounter any errors while trying to run, address those. If not, then you're now listening for incoming authentic knock sequences. Make sure you distribute the secret to the client.