steven/hyp
1
1
Fork 0
Code Issues 6 Pull Requests Packages Projects 1 Releases 1 Wiki Activity

Support for Multiple Clients #1

New Issue
Closed
opened 2024-04-08 04:12:35 +00:00 by steven · 2 comments
steven commented 2024-04-08 04:12:35 +00:00
Owner
Copy Link

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
steven commented 2024-04-11 03:59:13 +00:00
Author
Owner
Copy Link

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 ```
steven commented 2024-04-20 04:09:41 +00:00
Author
Owner
Copy Link

Added in 2951c1f684
and 1e195c3768

Added in 2951c1f68450aa1090a49775466709f20cd8f3f7 and 1e195c3768d43e1a2ee7f3bda7ca3ebd937a5404
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
hyp / Client
hypd / Server
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
enhancement
hypd / Server
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees steven
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: steven/hyp#1
No description provided.
Delete Branch "%!s()"

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?