minimo SSL problem
Andrew de Quincey
just targetting at x86 for the moment.
I've got it to compile fine using the _unmodified_ defaults and build
instructions on the minimo web page.
The problem is SSL is acting weirdly.
If I run "TestGtkEmbed https://www.sf.net", the browser doesn't display
anything. Investigating with ethereal shows it does talk to the web server,
but for some reason thinks it send a bad certificate - I can see it sending
a certificate rejection message back to www.sf.net.
If I run "TestGtkEmbed http://www.sf.net", it works. If I then enter
"https://www.sf.net" into the URL bar, SSL works fine!
If I use another initial website, e.g. "TestGtkEmbed http://www.google.com",
and then enter https://www.sf.net, it fails as before.
It doesn't just affect sourceforge - all SSL websites seem to be like this
for me. I'm not using a proxy or anything...
Anyone have any ideas? This is driving me mad.
Andrew de Quincey
Hmm, further research and *many* compiles later.. going to
https://www.sf.net gives:
open_uri_cb https://www.sf.net/
load_started_cb
new_window_orphan_cb
chromemask is -134216698
new_gtk_browser
new browser is 0x9291928
++WEBSHELL == 2
###!!! ASSERTION: EnableGlobalHistory() failed: 'NS_SUCCEEDED(rv)',
file /tmp/mozilla/embedding/browser/webBrowser/nsWebBrowser.cpp, line 1168
Break: at file /tmp/mozilla/embedding/browser/webBrowser/nsWebBrowser.cpp,
line 1168
++DOMWINDOW == 2
open_uri_cb file:///etv_dev/scratch/activy-mozilla/mozilla/dist/bin/chrome/
domainMismatch.xul
i.e. its trying to complain that the certificate is mismatched to the
domain. In fact, I just saw this with that very site in konqueror.
What I assume is happening that it is waiting for the above popup window to
be confirmed/denied by me - but since XUL is disabled by minimo, nothing
appears to me. To me, this points to having to replace
security/manager/pki/src/nsNSSDialogs.cpp somehow when using minimo+SSL in
order to display a non-XUL dialogue box for confirming these things... but
I don't know enough about mozilla yet to know if I'm not talking rubbish.
Has something like this already been done in a later version?
As to why that error didn't get displayed earlier, I've no idea... maybe it
was somehow just rejecting the domain out of hand 'cos it was wrong...
Doug Turner
It is a bug. feel free to file it in bugzilla.mozilla.org. We need to
implement the nss psm dialogs.
Doug