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

same dh4096.pem on all installation [add option to change in OVPM] #78

Open
jidea opened this issue Mar 12, 2019 · 2 comments
Open

same dh4096.pem on all installation [add option to change in OVPM] #78

jidea opened this issue Mar 12, 2019 · 2 comments
Assignees
Milestone

Comments

@jidea
Copy link

jidea commented Mar 12, 2019

I use the rpm version of ovpm, and all installations have the same dh4096.pem.
you should warn for changing it in /var/db/ovpm , or add an option in ovpm to change it.
just edit. each time you restart ovpm it rewrite dh4096.pem with the old same file

@cad
Copy link
Owner

cad commented Mar 12, 2019

@jidea I don't see any problem with using it in all installations as far as security concerned since 4096-bit field primes are known to be safe against logjam attacks and they are safe to be published. They are there for practicality reasons (generating 4096 DH-Params takes time).

But adding an option to change it in the OVPM is a good idea since this way the user don't have to trust OVPM developers for the DH-Params.

@cad cad self-assigned this Mar 12, 2019
@cad cad added this to the v0.3 milestone Mar 12, 2019
@cad cad changed the title same dh4096.pem on all installation same dh4096.pem on all installation [add option to change in OVPM] Mar 12, 2019
@cad
Copy link
Owner

cad commented Mar 12, 2019

Another thing to address is /var/db/ovpm is not meant to be edited or fiddled by the user. Nothing is guaranteed to stay still in that directory.

Thus obvious way to make changes to the underlying config would be through OVPM CLI or WebUI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants