Hi yes *now* the results are as expected - as i wrote that mail ssllabs cleary missed the root-cert in it's own chain while i am wondering how it can get satisfied by just add it to the PEM file because how does soemthing verify it's trust state
Am 02.03.2017 um 06:36 schrieb Bhushan Lokhande: > Reindl has shared the hostname with me while ago. We are in touch with > him to resolve issue. > The results seem fine when we removed roots from the test. > > Regards, > Bhushan > > On 28 February 2017 at 23:31, Ivan Ristic <ivan.ris...@gmail.com > <mailto:ivan.ris...@gmail.com>> wrote: > > It could be a bug, but we can't say without seeing the actual > report. If you don't want to reveal the hostname here, please send > it to me privately. > > If you wish, you can also open a ticket > here: https://github.com/ssllabs/ssllabs-scan/issues > <https://github.com/ssllabs/ssllabs-scan/issues> > > Thanks. > > On Tue, Feb 14, 2017 at 10:02 AM, Reindl Harald > <h.rei...@thelounge.net <mailto:h.rei...@thelounge.net>> wrote: > > Intermediate1.crt > Intermediate2.crt > Root.crt > > with only the intermediate certificates in the pem-file it falls > down to > grade B because broken chain, when i add the "Root.cert" as expected > grade A (HSTS follows later in the deployment) but then it complains > about "Chain issues: Contains anchor" > > seems to be a bug in ssllabs ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ ssllabs-discuss mailing list ssllabs-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ssllabs-discuss
