It strikes me that some people might not have a good idea how people use certs to do bad things. As the token bad guy in this forum I'll take it upon myself to share some examples of how I might use a perfectly good cert in a "bad" way:
‎
* ‎Create a phishing site to harvest login credentials from unsuspecting people. For this I might create my own bogus domain or piggyback off an existing, legitimate domain. Either way, I can use the cert to help create the illusion of legitimacy to a victim while I steal his or her info.

* Use a server to distribute malware via online adverts (malvertising). Having a cert helps make it look more legit and is required by some advertising services.
‎
* Set up a spam email server and use the cert for my login page to the control panel.‎ The cert wouldn't be used on the email side of things but controlling access to a server that lets me do bad stuff.
‎
* Use a server to distribute malware via downloads. When I launch a spam campaign I'll attach an infected document with some dropper malware in it. The dropper malware then contacts my server to get the real malware, be it ransomware or a banking trojan or remote desktop control or general zombie code or.... Whatever the case may be I can use certs to encrypt the malware download making it harder for people to figure out what's really going on.  
‎
‎* Sign my malware code so that Windows or MacOS will happily‎ install it.

‎* Set up a command and control server and use certs to send encrypted messages between the malware on the devices I've pwnd and my server.
‎
* Set up a media server so that people can download some great movies that I pilfered from someone else.

* Create a forum so people can talk about things their government does that really bugs them and how to evade the different law enforcement agencies.‎ Obviously I'm using certs to make it harder for those agencies to snoop on the forum participants. 
‎
* Set up an online marketplace to swap/buy/trade any compromised keys and the certs that go with them. Naturally I'd have a place to discuss which CA's have the easiest security measures to bypass.
‎‎
* And sometimes it's just fun to park outside a hotel and setup a free WiFi network to do some MITM. People do some crazy things when they think no one is watching, and certs keep people from getting suspicious that anything is amiss.

* Oh, and Lenovo and Dell demonstrated some out of the box thinking with all the Superfish stuff.

‎
The point here is that while "bad" can be a subjective term there are some behaviors that ought to be discouraged. There is a role for CA's to play in that effort but not in any sort of absolute, all or nothing sense.

My suggestion is to frame the issue‎ as: What is reasonable to expect of a CA if somebody sees bad stuff going on? How should CA's be notified? What sort of a response is warranted and in what timeframe? What guidelines should CA's use when determining what their response should be?

All of this is worthy of discussion, but it's gonna get complicated. 

_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to