3 ms·
> Which highlights a few things... Yeah, that sounds a lot like the author misunderstood what actually happened and why it was bad. > the article expects anyo
by xg15 8y ago
> Which highlights a few things...
Yeah, that sounds a lot like the author misunderstood what actually happened and why it was bad.
> the article expects anyone creating private CA’s to follow the Baseline Requirements for public CA but those requirements are the reason you can’t use public CA’s in the first place.
Not that it matters much, but I believe you can fulfill that requirement by using the "localhost.company.tld" trick - it's just another unnecessary hoop to jump through.
Of course the requirement "don't tell everyone and their grandma about your private key" is a bit harder to keep...
> but it does highlight that the cert was for localhost, so delivery of the certs to the websocket server wouldn’t be too much of an issue in this case.
Ah, true. Because the article was about headphones, I was imagining some kind of rube-goldberg setup where the headphones themselves pretended to be a USB network interface and terminated the websocket connection. But upon reading again, the connection is for the setup/utility program, not the actual hardware.