Wireshark · Wireshark-dev: Re: [Wireshark-dev] Bugzilla SSL Issue?

[Graham Bloice <graham.bloice@xxxxxxxxxxxxx>]

On 20 January 2017 at 15:04, Pascal Quantin <pascal.quantin@xxxxxxxxx> wrote:

2017-01-20 15:59 GMT+01:00 João Valverde <joao.valverde@tecnico.ulisboa.pt>:

I think the correct (?) URL is: https://bugs.wireshark.org/

Doh, of course. I did not realize when clicking on Roland's link ;)
 

Ah, I'd manually typed the (correct) URL.  Never click on links in email -:)

 

On 01/20/2017 02:55 PM, Pascal Quantin wrote:

2017-01-20 15:46 GMT+01:00 Graham Bloice <graham.bloice@xxxxxxxxxxxxx
<mailto:graham.bloice@trihedral.com>>:

    On 20 January 2017 at 14:39, Roland Knall <rknall@xxxxxxxxx
    <mailto:rknall@xxxxxxxxx>> wrote:

        I am getting SSL issues while contacting
        https://bugzilla.wireshark.org

        Anyone else does as well?

        My Google Chrome (Version 55 on Linux) does not accept the
        certificate. Moreove, the certificate seems to have been issued
        on Jan 02 2017 and expires on April 02 2017, which is weird by
        itself

        Anyone else having this issue?

        Cheers
        Roland


    I'm getting a cloudflare SSL cert for bugzilla, valid until 2 July
    2017 and my Chrome (5.0.2883.87 m on Windows) is happy with it.

    The short lifetime of the cert you see is typical of a Let's Encrypt
    cert (90 days) and that's what Gerrit is using (for me).


I'm now facing the same issue as Roland. Firefox reports:

bugzilla.wireshark.org <http://bugzilla.wireshark.org> uses an invalid
security certificate. The certificate is only valid for the following
names: wireshark.org <http://wireshark.org>, www.wireshark.org
<http://www.wireshark.org> Error code: SSL_ERROR_BAD_CERT_DOMAIN

There is probably some work ongoing ;)

Pascal.

--

Graham Bloice