one has to read the displayed warning thouggh, and click on "I understand the risk".If this is paranoid or even MS-like, I won't state any opinion on that ... 
That's only half of the story, though. You need to click on "I understand the risk" then on another button, then a window pops up which has "install permanently" selected
by default and a built-in 2 second delay before the UI can be accessed. Seriously, if the browser tells you "Warning! Great danger ahead, do not proceed, don't trust that site!" then why in the name of all that is holy would you want to
permanently install that certificate? This is just a flipping stupid preset.
A lot of websites use https:// for no apparent reason, and most people don't care about whether a connection to a random site on the web is secure or not, as they know that they can't trust a random website anyway. No need to be so darn smart-alec about security when it really doesn't add anything to security and indeed only steals the user's time. A simple "yeah, I know... show it anyway" would be entirely sufficient.
On top of that, if a site has updated their certificate at some point in the past and it's one of the commonly used "snake oil" certificates (i.e. the unsigned self-made ones), then Firefox will deny access to that site alltogether, with no "show anyway" option at all. It will only keep you telling that the certificate is ambiguous. This is what has happened to me before and what might (possibly) have happened to the Kiwisoft person, hence my above post.
You can of course fix the problem by deleting the certificate database, but hey... what the hell? What program (other than Code::Blocks of course
) requires you to delete files to fix program self-configuration errors?!
