Trying to understand CA reporting mechanisms - 1 makes no sense

[Kurt Seifried]

So I'm trying to understand the CA problem reporting mechanisms listed at:

https://ccadb-public.secure.force.com/ccadb/AllProblemReportingMechanismsReport

Most are simple, an email address or URL (contact_pki@vendor, https://problemreport.vendor, ok easy).

But there is one I can't figure out:

5463283B6793FF55277CEDE39098E80422F912F7 Certicámara

And ironically there's no problem report mechanism listed on https://www.ccadb.org/ for itself so I'm posting it here. 

--

Kurt Seifried (He/Him)
ku...@seifried.org

[Matthew McPherrin]

That string is the sha-1 fingerprint of their root.  If I had to guess, somebody's mixed up some form fields.

--
You received this message because you are subscribed to the Google Groups "public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public+un...@ccadb.org.
To view this discussion on the web visit https://groups.google.com/a/ccadb.org/d/msgid/public/CABqVa38UCFvPX5SeYzamepU2VSjc9N4_NxPsJ0DAyRsL-5aAfg%40mail.gmail.com.

[Kurt Seifried]

On Wed, Dec 14, 2022 at 11:40 AM Matthew McPherrin <ma...@letsencrypt.org> wrote:

That string is the sha-1 fingerprint of their root.  If I had to guess, somebody's mixed up some form fields.

Which leads to a second question: has anyone validated that these reporting methods are still active/working/effective?