Path: mv.asterisco.pt!mvalente
From: mvale…@ruido-visual.pt (Mario Valente)
Newsgroups: mv
Subject: Firefox Bounty Followup II
Date: Sun, 03 Jul 07 23:40:21 GMT
To all we contributed to aditional diagnosis of the
problem my heartfelt thanks.
We have now confirmed our initial suspicion (see my
first post) that the problem was most probably related
to character encodings and not to some server side
configuration problems. This has been confirmed thanks
to Nelson Bolyard:
https://bugzilla.mozilla.org/show_bug.cgi?id=245609#c20
Unfortunately although we have the diagnostic, we
do not have a solution. I mean, sure its relatively easy
for the state agencies involved to go and reissue the
certificates with matching encodings. But I must say that
it pains me to see the standards (RFC3280 and RFC4630)
implemented in a reasonable way (comparing strings as
they should be; keep in mind that both RFCs state MAY
and SHOULD, there’s no MUST) in other browsers and FF
displaying a wrongful message just because of the lack
of some string conversion code.
So, until it is obvious that no solution is
forthcoming and that we might as well reissue the
certificates, the bounty still stands for anyone that
submits the feature/bug/whatever to Bugzilla and comes
up with the code/patch to back it up.
— MV
