Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preshared keys #9

Open
cab404 opened this issue Feb 13, 2022 · 3 comments · May be fixed by #17
Open

Preshared keys #9

cab404 opened this issue Feb 13, 2022 · 3 comments · May be fixed by #17

Comments

@cab404
Copy link
Owner

cab404 commented Feb 13, 2022

Preshared keys

Each pair of hosts need to have their own preshared key.

Maybe generate them on demand, and store in a map like

{ 
  "1:2": "YFkBJfhgGWwYY6fE1PO+YCkDRZ86WnZChPRK1QFFHa0=",
  "1:3": "R2YqPfqcc8GvC0wt+44J1WiB2GSknJNI4kahLQkyjik=",
  "2:3": "O6zbcK3zN2Oo2GAOnIYWOQuG+Wh3bXxbe/k+1nah0GA="
}

Orig: https://gitlab.com/cab404/wg-bond/-/issues/19

@sancho20021
Copy link
Contributor

Can I do this?

@cab404
Copy link
Owner Author

cab404 commented Jun 17, 2022

@sancho20021 yeah, sure ❤️

@sancho20021
Copy link
Contributor

@cab404 Is this the same PresharedKeys as Peer::preshared_key : Option<String>?
When we export configuration for a certain peer, for all other peers we should insert corresponding preshared_key option taken from the map you shown above?

sancho20021 added a commit to sancho20021/wg-bond that referenced this issue Jul 5, 2022
Solution: Add a map in Wireguard Networkinfo that contains
pre-shared keys for each pair of hosts.
Add command that generates keys on demand.
@sancho20021 sancho20021 linked a pull request Jul 5, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants