Support for Multiple Clients #1

Closed
opened 2024-04-08 04:12:35 +00:00 by steven · 2 comments
Owner

While you could technically use multiple clients in the current state, each client would have the same pre-shared key. If a trust client suddenly becomes untrusted, a key rotation may be a cumbersome process if there are many clients. Each client should have their own key, meaning each client will have their own knock sequence. The client will be able to be identified from the knock sequence being tied to their key.

While you could technically use multiple clients in the current state, each client would have the same pre-shared key. If a trust client suddenly becomes untrusted, a key rotation may be a cumbersome process if there are many clients. Each client should have their own key, meaning each client will have their own knock sequence. The client will be able to be identified from the knock sequence being tied to their key.
steven added the
enhancement
hypd / Server
labels 2024-04-08 04:12:35 +00:00
steven self-assigned this 2024-04-08 04:12:35 +00:00
Author
Owner

Multiple keys should be able to be generated and loaded by hypd.

./hypd generate secret >/etc/hyp/secrets.d/client1.secret
./hypd generate secret >/etc/hyp/secrets.d/client2.secret
./hypd generate secret >/etc/hyp/secrets.d/client3.secret
Multiple keys should be able to be generated and loaded by hypd. ```bash ./hypd generate secret >/etc/hyp/secrets.d/client1.secret ./hypd generate secret >/etc/hyp/secrets.d/client2.secret ./hypd generate secret >/etc/hyp/secrets.d/client3.secret ```
Author
Owner

Added in 2951c1f684
and 1e195c3768

Added in 2951c1f68450aa1090a49775466709f20cd8f3f7 and 1e195c3768d43e1a2ee7f3bda7ca3ebd937a5404
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#1
No description provided.