Good Morning,
I looked again at the dungog.net site for solutions to this issue. I downloaded the help file and looked for https. The solution provided is to use certification authorities. You can do this through dungog's package or use the Root Certification Authority (RCA) stuff in IE. This would only apply to folks running M$ stuff granted. In my situation, I will apply a Group Policy and restrict access to ssl sites through the RCA method. There is only one hitch to all of this while using this method, aging certificates. I have heard that the RCA folks won't recognize some of the aging cert's. This would present a problem with folks trying to get some valid sites with these aging cert's.
I'm beginning to think that for a small school, business, or home setup you would just block the entire https layer. If users needed to access certain https sites, use the exception list and add the url's that are needed. This would be a minor, in my humble opinion, maintenance hassle. For example, elementary students, K-6, wouldn't need to even look at a https site. High school students, 7-12, might need to access certain sites for contest information and/or other state educational resources.
Another solution would be just to install some type of network monitoring software and hammer the folks that have high traffic. After looking at the dansguardian log via SawMill, it shows the https request. Since I have users authenticating, I can apply filters and look for folks accessing these types of url's.
I'm going to be relying heavily on SawMill for information. I know it costs money but for $80 for 5 configurations, that's cheap. It also puts things in nice pie charts that principals and other beauracrats(?) like to look at. My opinion, on a tangent here, the principals need to look at the information, disseminate it and discipline accordingly. I'm tired, as an IT person, of handing out discipline or being put in a position that makes it look like I'm the one hammering the student. Now, back to the real world.