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

FireFox Warning: Potential Security Risk Ahead #2198

Closed
rstens opened this issue Dec 20, 2019 · 6 comments
Closed

FireFox Warning: Potential Security Risk Ahead #2198

rstens opened this issue Dec 20, 2019 · 6 comments
Assignees
Labels
bug Something isn't working ENTITY Business Team Priority1 Relationships Work for Relationships team

Comments

@rstens
Copy link
Member

rstens commented Dec 20, 2019

Describe the bug
Firefox does not trust dev.bcregistry.ca because its certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates.

The Certificateseems to be valid and correct

To Reproduce
Steps to reproduce the behavior:

  1. Open FireFox
  2. Go to https://dev.bcregistry.ca/cooperatives/auth/'
  3. See error

Expected behavior
No Error, functionality is now blocked.

Screenshots
image.png

Desktop (please complete the following information):

  • OS: Win10
  • Browser FireFox
  • Version 70.0.1 (64-bit)
@rstens rstens added the bug Something isn't working label Dec 20, 2019
@thorwolpert
Copy link
Collaborator

@rstens seems to be fine under Chrome. It looks like the certificate chain is loaded correctly.

image

@thorwolpert
Copy link
Collaborator

An overall grading of a C. That's not great by any measure.
SSL_Server_Test_dev.bcregistry.ca.pdf

@Kaineatthelab
Copy link
Collaborator

Kaineatthelab commented Dec 20, 2019 via email

@rstens
Copy link
Member Author

rstens commented Jan 23, 2020

Is there a correlation with the TLS 1.0 version still being the only supported one?

@WalterMoar
Copy link
Contributor

WAM has five tickets open for this, due to the variety of applications behind *.bcregistry.ca. To make it easier on WAM we're closing ours and letting Dave McKinnon deal with it, since he has the oldest servers hosting the highest profile applications.

Yes, it's due to both the TLS version, as well as the cipher suite in use). Chrome 81 (March 17) will not allow access to TLS1.0 and TLS1.1 sites. Likewise Firefox 74 (March 10).

@severinbeauvais severinbeauvais added Priority1 ENTITY Business Team Relationships Work for Relationships team labels Jan 31, 2020
@severinbeauvais
Copy link
Collaborator

severinbeauvais commented Jan 31, 2020

See also #1487.

Closing this ticket per Walter's note above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ENTITY Business Team Priority1 Relationships Work for Relationships team
Projects
None yet
Development

No branches or pull requests

5 participants