This is probably OT, but SSL is meant to be so Man in the middle attacks cannot happen, only the two endpoints know how to decrypt messages they send to each other. You could create rules in each computer to redirect all SSL messages to a proxy and do what you say but your kid's browser will warn he/she as the certificate would be self signed instead of the appropriate cert.

I would tackle your problem in a different way, why don't set up an regular HTTP proxy ( such as Squid ) and block your internet connection and make every computer in your home use that proxy? With that setup you would be able to monitor all kind of activity and even block sites with unappropriated content

Since all traffic pass through one box you can also use other tools ( iptables, scripts ) to enforce your internet policy such as an script that shuts down squid at the afternoon/night when they have to do assignments. Out of the box Squid has many features and it might have whay you're looking for.

               ------------
               | Internet |
               ------------
                     |
                 ---------
                 | Proxy |
                 ---------
                     |
       --------------+---------------
       |             |              |
   ---------     ---------      ---------
   | PC #1 |     | PC #2 |  ... | PC #N |
   ---------     ---------      ---------
[download]

I believe you could do something like...

• Generate a bogus CA.
• Install CA root cert in kids' browser.
• Have the proxy generate bogus certs and sign with your CA.
• Hope the kids don't notice how slow SSL has become.

Something like this is actually done in big institutions.

Some year ago I did a project in a big bank in Switzerland.
Pretty much everybody there was using the "official" Internet Explorer. The funny thing was that when you used Firefox you got warnings on ssl-secured sites that the certificate did not match the domain-name. In fact it turned out that their proxy just returned a self-signed certificate and the "official" Internet Explorer had been modified so that it would silently accept this certificate.

So in effect they had a man-in-the-middle with hardly anybody noticing it.

So if you want to do it yourself the important thing is that you must be able to control the browser (and I assume that if you can force your users to use IE you're already halfway there).

And as an aside: Never trust the browsers that are rolled out by the IT-departments of big organisations.

Thanks for the responses. Not looking to break SSL security for NSA's sake. Funny though.

I intend to generate bogus CA, install into kids browser, etc, etc...

My main question has to do with the "Perl" side of this, and whether or not HTTP::Proxy can be used as the proxy for this need? I want to know if anyone knows if it will support SSL? If not, is there another module someone recommends for this?

Thank you again for your help in advance

I haven't ever written anything with HTTP::Proxy but it looks very flexible so you might be able to convince it to work with SSL. On the other hand, HTTP::Proxy isn't really designed for MITM attacks so it'll want to add the proper headers and such.

One way to do this would be to use POE. You can do something based on the Cookbook example of a simple Web Proxy.