Optional mode: Persistent client, periodic refresh #11

Closed
opened 2024-04-18 17:29:53 +00:00 by steven · 1 comment
Owner

Instead of the client being a oneshot operation, there should be an optional mode to allow it to run persistent in the background, and perform the authentic knock sequence periodically.

The purpose of this to ensure the channel remains open and the timeout on the hypd server is refreshed periodically so that the ports do not get closed.

Instead of the client being a oneshot operation, there should be an optional mode to allow it to run persistent in the background, and perform the authentic knock sequence periodically. The purpose of this to ensure the channel remains open and the timeout on the hypd server is refreshed periodically so that the ports do not get closed.
steven added the
enhancement
hyp / Client
labels 2024-04-18 17:29:53 +00:00
steven self-assigned this 2024-04-18 17:29:53 +00:00
Author
Owner

Added in 2af574fd18

Added in 2af574fd18ff3eed6ac244b539c1808317f0e014
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: steven/hyp#11
No description provided.