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.
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
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
Multiple keys should be able to be generated and loaded by hypd.
Added in
2951c1f684and
1e195c3768