Live data from Hacker News

This seem legit...

trustico.ch

41–50 of 64 posts

Re: This seem legit...

#42

Apparently the feature is widespread: https://www.sslshopper.com/certificate-key-matcher.html http://www.ssltools.com/cert_key_match https://certificatesssl.com/ssl-tools/match-ssl-details.html http://www.mobilefish.com/services/privatekey_match_certific... http://sslchecker.com/matcher

Scary. To be fair, although this kind of tool should not exist at all, the sslshopper tool at least has a warning, enforces https and informs users how to check it properly on the command line. The others, however, do not.

Re: This seem legit...

#48
Hi,

The tool was made available for customers to legitimately check if the Private Key matched the SSL Certificate that was being installed - a common question and feature request from our customers.

However, upon review of the comments made in the internet community we have made a decision to remove this specific tool and to review all other tools that we make publicly available via our websites.

We also saw a heavy attempt to hack/abuse this tool over the past few hours, perhaps to look for exploits, an action I find absurd for those who make out to be security conscious.

I welcome any further comments on how we can improve our service and do hope that our actions to remove the tool today were prompt and satisfactory.

Zane Lucas General Manager Trustico Online Limited

Re: This seem legit...

#49
post #29
post #13

I contacted their support: Me: I wanted to know more about your certificate key matcher isn't the private key always meant to remain... private? Emanuele: Yes, it should. We offer the tool to help verify the correspondence SSL certificate it is lost. Me: But it would be sent over HTTP and viewable to anyone along the network. Emanuele: The page can also be accessed through HTTPS. Me: I think it should be enforced. Al…

So leaking my private key to somebody is OK if I do so over HTTPS, and even better if I encrypt it with a javascript crypto library beforehand? I don't think you've thought this through.

Sending it over HTTPS at least narrows down the recipient to.. who it's intended for. And I wasn't suggesting encrypting and then sending it to them, instead perform the check on the client side in a way that no information is ever sent back to their server; using the browser as a platform to run an "app".

I don't condone this at all, but if they're adamant about providing this service they should at least try and make it less damning than it already is.

Post reply on HN