On Mon, Sep 22, 2008 at 9:08 AM, Gerd Stolpmann <[EMAIL PROTECTED]> wrote: > Yes, I know how to fix this, but it's expensive. It has to do with the > business model of some browser vendors - basically, trust centers pay > them for being included in the list of root certificates delivered with > the browser. If you buy a certificate from such a trust center, the > browser accepts the certificate without any problems. (And the browser > vendor gets money.)
Thanks for the explanation! > So I chose to use my own root certificate. In the past, the only effect > was that the browser showed a dialog that the certificate was not > trustworthy, but it nevertheless allowed the user to access the site > after pressing the OK button. Recent browsers, however (namely Mozilla), > changed that and do not let users in. It's still possible, but the user has to click on a few more things before the browser will accept untrusted certificates. I think it's prudent to do it this way, but it's certainly a nuisance in this case. > I don't know whether there is a way to revert to the old behavior with a > config setting, or with a browser extension. You can probably add my > root certificate to the list of trusted certificates: The browser offers you the option to accept the certificate permanently so it's not a big deal. I just wanted to make sure that I'm not sending my login information for your machine to anybody else... Regards, Markus -- Markus Mottl http://www.ocaml.info [EMAIL PROTECTED] _______________________________________________ Godi-list mailing list [email protected] https://godirepo.camlcity.org/mailman/listinfo/godi-list
