-
Notifications
You must be signed in to change notification settings - Fork 140
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
Latest version of Chrome browser rejects generated certificate #216
Comments
|
Fix ported to v3.5 branch. if cd path_to_generated_cert_directory |
|
Hi! For Debian stretch, which will be released with e2guardian 3.4.0.3, it would be good to have a fix for this issue backported to the 3.4 branch. Is that possible from the upstream devs? It would be highly appreciated. With a upstream sanctioned patch, I could update e2guardian in Debian stretch and make people happy when using Google Chrome and Chromium against an e2guardian on a stretch server. Hope someone raises his/her finger for this... Mike |
|
Ok, I will, I hope next week |
|
Hi Fred,
On Di 23 Mai 2017 08:41:57 CEST, Fredb wrote:
Ok, I will, I hope next week
Awesome! Thanks!
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
|
|
at least if that is possible ... |
|
I think I have already fixed this in v3.5 branch - just needs testing and if OK releasing.
Regards
Philip
…----- Original Message -----
From: "Fredb" ***@***.***>
To: "e2guardian/e2guardian" ***@***.***>
Cc: "Philip Pearce" ***@***.***>, "Author"
***@***.***>
Sent: Tuesday, 23 May, 2017 7:41:57 AM
Subject: Re: [e2guardian/e2guardian] Latest version of Chrome browser
rejects generated certificate (#216)
Ok, I will, I hope next week
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread
.
|
|
Yes Philip, but 3.4.0.3 has been selected to be in Debian stretch (so also in Ubuntu) |
|
Ok pushed, thanks Philip |
This is due to Google implementing a non-standards based policy in Chrome.
Adjustment to certificate generation made in latest v4.1 branch which adds fields required by Chrome. Note: You must clear your generated certificates cache on systems for the new policy to have an effect. Do this safely with script such as:-
if cd path_to_generated_cert_directory
then
rm -fr *
fi
The text was updated successfully, but these errors were encountered: