ultimate_evil wrote:Invalid ssl is not really any less secure then regular HTTP.
True, but why not use regular HTTP then?
ultimate_evil wrote:Do you really want me to put it up on the http server? I could, but I don't see any advantages to doing so.
I do see one: no pile of annoying messages by the web browser. No need to use --no-check-certificate on wget. Faster access.
Seriously, if you want SSL without the security, use a VALID self-signed certificate. That's just one message - the "this certificate was not signed by a CA I know" one. Not three dialog boxes as one has to answer on your site ("certificate is expired", "not signed by a trusted CA", "invalid host name"). When I visit your website
https://cat2.dynu.ca, I actually get these three messages THREE TIMES. Means I have to click okay NINE TIMES just to be able to see your website. That's more annoying than commercial popups.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again
You can vary the number of "MS", so you can clearly see it's MS which is causing it.