Yes, that's the wiki I mean. And I can see your point about all those
sub-subdomains; there must be a stack of them. The domain name was changed
fairly recently and we got the bad cert messages then, and added our
exceptions. Tonight we got the messages again. Perhaps it was because the
subdomain's cert changed.
Risker/Anne
On 13 March 2013 00:30, Ryan Lane <rlane32(a)gmail.com> wrote:
You mean:
https://arbcom.en.wikipedia.org ?
Our certificates have never covered that. That's a sub-sub domain, and our
certs only cover single subdomains. We really need to rename all of our
sub-sub domains to single subdomains for them to be covered (or we need to
include every sub-subdomain in the unified cert, but that's going to bloat
it).
On Tue, Mar 12, 2013 at 9:18 PM, Risker <risker.wp(a)gmail.com> wrote:
On 12 March 2013 21:15, Ryan Lane
<rlane32(a)gmail.com> wrote:
> On Tue, Mar 12, 2013 at 4:47 PM, Brion Vibber <brion(a)pobox.com> wrote:
>
> > Thanks guys!
> >
> > -- brion
> >
> >
> Don't thank us too quick. We needed to revert this for mobile. Seems *.
>
m.wikipedia.org was also missing from the cert. Needless to say I'll
be
writing a
script that can be run against a cert to ensure it's not
missing
anything. We'll also be adding monitoring to
check for invalid
certificates
for any top level domain.
I think it might also be missing some of the small/private wikis. I got
"bad certificate" messages for the English Wikipedia Arbcom wiki tonight.
But thanks for working on this.
Risker/Anne
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l