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

Incorrect path to openssl.cnf on Ubuntu 18 #98

Open
cyberphone opened this issue Apr 4, 2021 · 7 comments
Open

Incorrect path to openssl.cnf on Ubuntu 18 #98

cyberphone opened this issue Apr 4, 2021 · 7 comments

Comments

@cyberphone
Copy link

The file keygen-jwt.sh contains a line OPENSSL_CNF_PATH= holding a path which doesn't match Ubuntu. It makes installation fail. This is the proper path for Ubuntu 18.*:
/usr/lib/ssl/openssl.cnf

@F9Alejandro
Copy link

I found mine under /etc/ssl/openssl.cnf they might point towards the same file and are symlinked together.

Or is just the difference between 18 and 20.

@cyberphone
Copy link
Author

It is apparently something that more than I have had a problem with:
https://stackoverflow.com/questions/37035300/how-to-determine-the-default-location-for-openssl-cnf

I also had to change this line:
#RANDFILE = $ENV::HOME/.rnd

OpenSSL does no longer depend on this setting

@F9Alejandro
Copy link

true they use their own pseudorandom generator. However it might be better to use the urandom since it might help with the security flaw in ssl about the certificate date being part of the seed.

@cyberphone
Copy link
Author

This may be correct but this setting didn't work (according to the build script) on Ubuntu 18.04 which is why I disabled it.

@F9Alejandro
Copy link

I don't receive any errors like that. Could be because I don't have the verbose on, only errors I normally would get is incomplete downloads so I would delete the one that was causing the issue and just have it redownload. Should really make new keystores before doing an install so it has the proper certs in them. Same with the ldif files I should probably edit those to have the right cn and such to work with the FQDN.

@cyberphone
Copy link
Author

I'm an Ubuntu n00b. Anyway, random number thing only generated a warning that rnd file couldn't be created or is not available.

@F9Alejandro
Copy link

huh, think it was /dev/urandom or something of the sort.

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

No branches or pull requests

2 participants