"intentionally-vulnerable" in your quote referrs to the intentions of Cloudflare in installing Nginx on top of a vulnerable Openssl installation.

Thanks!

No, I just scanned through it looking for hints on what the ca subject might be. Now I have however and I have to admit it still isn't clear to me from the article that this is not a common ca or whatever we should call them.

I can't find any certificate that looks like this on Centos 6 either.

Just asked a collegue to check his windows machine for any ca certificates named anything with Gemnet or KPN, no matches there either.

Ok, so this Ca is already not included in Debian?

I can't find anything about it in the changelog for the ca-certificates package.

So the first question I expected t.f.a. to answer:

What is the subject name of this Ca so I can remove it from my list of "trusted" Cas?

... anywhere else that thing is going to collect colossal amounts of dust.

If I recall correctly CDIndex uses a different
algorithm for calculating the (hopefully (not!))
unique DiscID. Supposedly CDIndex's method is
better -- less lossy. This would make a proxy
virtually impossible to create.

So why do I say not in the above paragraph?
Well I've got some Kraftwerk CD's in both
german and english. These have exactly the same
track layout, giving them identical discids.
I'd like an algorithm that also samples a few
msec's of audio in certain places, to prevent
this.