On Tuesday, December 18, 2018 at 2:44:22 AM UTC-8, Matt Palmer wrote: > Hi all, > > I'd like to make everyone aware of a service I've just stood up, called > pwnedkeys.com. It's intended to serve as a clearinghouse of known-exposed > private keys, so that services that accept public keys from external > entities (such as -- relevant to mdsp's interests -- CAs) can make one call > to get a fairly authoritative answer to the question "has the private key > I'm being asked to interact with in some way been exposed?". > > It's currently loaded with great piles of Debian weak keys (from multiple > architectures, etc), as well as some keys I've picked up at various times. > I'm also developing scrapers for various sites where keys routinely get > dropped. > > The eventual intention is to be able to go from "private key is on The > Public Internet somewhere" to "shows up in pwnedkeys.com" automatically and > in double-quick time. > > I know there are a number of very clever people on this list who have found > and extracted keys from more esoteric places than Google search, and I'd be > really interested in talking to you (privately, I'd imagine) about getting > specimens of those keys to add to the database. > > I'd also welcome comments from anyone about the query API, the attestation > format, the documentation, or anything else vaguely relevant to the service. > Probably best to take that off-list, though. > > I do have plans to develop a PR against (the AWS Labs') certlint to cause it > to query the API, so there's no need for anyone to get deep into that unless > they're feeling especially frisky. Other linting tools will *probably* have > to do their own development, as my Go skills are... rudimentary at best, > shall we say. I'd be happy to give guidance or any other necessary help to > anyone looking at building those, though. > > Finally, if any CAs are interested in integrating the pwnedkeys database > into their issuance pipelines, I'd love to discuss how we can work together. > > Thanks, > - Matt
This is great. I purchased keycompromise.com ages ago to build something just like this. Im very glad to see you took the time to make this. My first thought is by using SPKI you have limited the service unnecessarily to X.509 related keys, I imagined something like this covering PGP, JWT as well as other formats. It would be nice to see the scope increased accordingly. It would be ideal if it were possible to download the database also, the latency of the use of a third-party service while issuing certs is potentially too much for a CA to eat at issuance time; something that could optionally be used on-prem wouldn't leak affiliation and address this. As long as its limited to X.509, or at least as long as it supports it and uses SPKI, it would be interesting to have the website use PKIjs to let you browse to a cert, csr or key and the SPKI calculated for you. Happy to help with that if your interested. Personally I prefer https://api.pwnedkeys.com/v1/<fingerprint> to https://v1.pwnedkeys.com/<fingerprint>. I see your using JWS; I had been planning on building mine on top of Trillian (https://github.com/google/trillian) so you could have an auditable low trust mechanism to do this. Let me know if your interested in that and I would be happy to help there. Anyways thanks for doing this. Ryan Hurst (personal) _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
