Web lists-archives.com

Re: Help, I broke sso.debian.org for chrome

Re: Enrico Zini 2017-09-05 <20170905163334.2mi5tzacykzjacak@xxxxxxxxxxxxxx>
> I should have managed to do it, but chrome still doesn't seem to like
> it. Can you generate a new certificate and see if you still find
> differences?

"openssl x509 -text -noout" doesn't show any differences anymore
except for the obvious parts (serial, validity, modulus and sig algo).

One bit that might or might not be relevant is that the CA certificate
was re-issued on Aug 3rd:

/srv/sso.debian.org/etc $ openssl x509 -text -noout < debsso.crt 
        Version: 3 (0x2)
        Serial Number: 1 (0x1)
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN = SSO CA 2015-08-21, O = Debian SSO client certificate
            Not Before: Aug  3 06:08:36 2017 GMT
            Not After : Dec 31 23:59:59 9999 GMT
        Subject: CN = SSO CA 2015-08-21, O = Debian SSO client certificate
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: critical
            X509v3 Key Usage: critical
                Certificate Sign, CRL Sign
            X509v3 Subject Key Identifier: 
            X509v3 CRL Distribution Points: 

                Full Name:

    Signature Algorithm: sha256WithRSAEncryption

This file is the one distributed to participating servers, so if
there's something wrong, it will have "infected" the other hosts as
well. I can't see anything wrong there either, though...

Starting with a blank chromium config (.config/chromium + .pki/nssdb)
and importing the client there doesn't help either.