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.

Sign up for GitHub

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

Jump to bottom

Update generated Certificates for Chrome #7

Open
edsealing opened this issue Dec 28, 2017 · 1 comment
Open

Update generated Certificates for Chrome #7

edsealing opened this issue Dec 28, 2017 · 1 comment

Comments

@edsealing
Copy link
Contributor

Chrome doesn't accept the certificates that are generated at install-time. Suspected culprit is that there is x509v3 certificates without any Subject Alternative Names. More troubleshooting required to figure out other reasons.
@edsealing
Copy link
Contributor Author

The certificates that are generated as part of the build process don't have the FQDN in them. This may cause problems with some browsers and applications.

As part of the build process, the certificate generation scripts should be updated with the FQDN that the user enters during the installation process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@edsealing