Close Ports When Done #6
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: steven/hyp#6
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There is no mechanism to close the port, only to open the port when the authentic knock sequence is received.
I'm thinking one approach is to make the hyp client as a continuously running process/daemon instead of a oneshot and exit. If left running, this would then enable your ports to open up and follow you whereever you connect from.
The hypd-server would require tracking clients that have successfully knocked, as well as the last time they succeeded. There also needs to be a timeout value, with a reasonable default (1 hour?)
The client would need to perform periodic refreshes in the background, maybe just under 1/3 of the server timeout value?
I also need to work out how much information about the key is leaked during each knock sequence transmission to ensure this frequency is sane. Only 64 bits of the sha1hmac are used for the authentic knock sequence, which shouldn't be reavealing much about the key?
Going to move client refresh into its own issue: #11
Added in:
d1239867ae