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

Site compatibility list checks/fix #50

Open
intika opened this issue Dec 27, 2018 · 5 comments
Open

Site compatibility list checks/fix #50

intika opened this issue Dec 27, 2018 · 5 comments
Labels
miss-behavior Unwanted behavior to-do (secondary) Next release to-do

Comments

@intika
Copy link
Owner

intika commented Dec 27, 2018

Test/Fix compatibility on those sites:

@intika intika added the to-do (secondary) Next release to-do label Dec 27, 2018
@intika intika changed the title Site compatibility checks/fix Site compatibility list checks/fix Dec 28, 2018
@intika
Copy link
Owner Author

intika commented Dec 29, 2018

Report from a ghack user...

I cannot access any of the ‘google sites’ in Librefox.

“The error message begins thus:”An error occurred during a connection to google.com. The server uses key pinning (HPKP) but no trusted certificate chain could be constructed that matches the pinset. Key pinning violations cannot be overridden. Error code: MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE”.

Need help. Thanks

@Atavic
Copy link

Atavic commented Dec 29, 2018

security.OCSP.enabled should be set to true to avoid such issues (that may have other causes, BTW).

@intika
Copy link
Owner Author

intika commented Dec 29, 2018

@Atavic yes just gathering users feedback but at the end of the day next version will be very soft by default so all of those issues should be fixed in one shoot, but don't worry there will be a menu to harden the settings

@elypter
Copy link

elypter commented Dec 30, 2018

Key pinning violations cannot be overridden.

although you really shouldn't visit a site like this because this quite likely means there is someone doing a man in the middle attack i think users shold still be allowed to do it anyways. after all unencrypted traffic is still allowed in most browsers. it is a good choice to disable it by default like with the nohttp addon but there should be no hardlocks.

@intika
Copy link
Owner Author

intika commented Dec 30, 2018

@elypter hahahaha i know, you did notice it too 👍 i was willing to ask the user from where he was connecting, but just did not bother to...

@intika intika added the miss-behavior Unwanted behavior label Dec 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
miss-behavior Unwanted behavior to-do (secondary) Next release to-do
Projects
None yet
Development

No branches or pull requests

3 participants