Oops, sent previous message under wrong email address. Hopefully this one will go through:
According to info I just found in Chrome (didn't dig in too deep, just looked at "certificate details" when visiting https://www.mozdev.org/), the certificate is valid for www.mozdev.org and these "alternative names": - www.mozdev.org - mozdev.org - svn.mozdev.org - hg.mozdev.org - mozdev.org - bugzilla.mozdev.org As an example, I know that if you try to go to https://downloads.mozdev.org/, the certificate is invalid, but it does seem to be working on https://hg.mozdev.org/. (Alex - maybe your hg client doesn't recognize the "alternative names" or whatever they are called in the certificate?) I have almost no experience with SSL certificates, but this is what I found out. --Jake On Sat, Feb 12, 2011 at 4:32 PM, Pete Collins <[email protected]> wrote: > Hrm, I thought we had a wildcard certificate? > > --pete > > > On 2/12/11 2:29 PM, Alex Vincent wrote: > > On my MacBook, when I tried to push, I got this: > > abort: hg.mozdev.org certificate error: certificate is for www.mozdev.org > > Please advise. > > > -- > Pete Collins - Founder, Mozdev Group Inc.www.mozdevgroup.com > Mozilla Software Development Solutions > tel: 1-719-302-5811 > fax: 1-719-302-5813 > > > _______________________________________________ > Project_owners mailing list > [email protected] > https://www.mozdev.org/mailman/listinfo/project_owners > >
_______________________________________________ Project_owners mailing list [email protected] https://www.mozdev.org/mailman/listinfo/project_owners
