l10n enhancement of ssl mismatch error page landed
Axel Hecht
Gavin just landed a fix for shipping locales that enables a
click-through link for non-matching ssl certs.
Like, https://amazon.com offers a certificate for
https://www.amazon.com/, and while they could beef up their cert, it's
fine to link to them.
So, please, update your security/manager/chrome/pipnss/pipnss.properties
file, the full list of check-ins is in the bonsai query,
Further detail is in https://bugzilla.mozilla.org/show_bug.cgi?id=402210.
If there are follow-up issues with this patch, please file bugs, CC me,
and mark them to depend on bug 402210.
Thanks and I hope you appreciate the noise
Axel
Hasse
wrote...
> Hi all,
>
> Gavin just landed a fix for shipping locales that enables a
> click-through link for non-matching ssl certs.
>
> Like, https://amazon.com offers a certificate for
> https://www.amazon.com/, and while they could beef up their cert, it's
> fine to link to them.
>
> So, please, update your security/manager/chrome/pipnss/pipnss.properties
> file, the full list of check-ins is in the bonsai query,
>
> <http://bonsai-l10n.mozilla.org/cvsquery.cgi?branch=HEAD&branchtype=match&date=explicit&mindate=2008-04-30+13%3A44&maxdate=2008-04-30+13%3A46>
Works fine in sv-SE. Though I have to wonder why the localization note
was not added to the l10n files?
--
Hasse
sv-SE l10n team
Axel Hecht
Good question, I guess because sed or awk can't do that easily.
File a bug on that, and CC me?
Axel