| Summary: | SSL v2 disabled in galeon 1.3.18 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Lindsay Haisley <fmouse-gentoo> |
| Component: | Current packages | Assignee: | Hanno Böck <hanno> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 1.4 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | https://www.networksolutions.com/en_US/manage-it/index.jhtml | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Lindsay Haisley
2005-01-07 21:47:37 UTC
I should add that galeon has no problem with other secure pages, e.g. https://secure.fmp.com. This is not a bug, it's just galeon's default-behaviour disabling sslv2. You can enable it by typing about:config in galeons address-bar and creating a boolean key called security.enable_ssl2 and set it to "true". But the better solution would probably forcing your provider to enable sslv3. OK, thank you! I guess the basic problem here is that this configuration interface is poorly documented, if at all. I browsed through the Galeon Users Guide and without doing more than digging in the obvious places (the obvious place is "Setting Galein Preferences"), I found nothing about about:config. I inquired about this problem on the gentoo-desktop list and no one there, including a number of gentoo devs, knew about this setting, apparently. If I have any doubt at all that a problem I'm having is a true bug, and not just a config problem, I always inquire on one or more of the gentoo lists first to see if I can track an answer down. I guess the "true bug" here is that about:config isn't well documented, and I or someone should probably file a doc bug on this. If it's documented on the web somewhere, a subsection "Advanced" under "Setting Galeon Preferences" might simply provide a link to same. Apparently these settings (or some of them) are gconf settings, which I thought I checked before filing a bug. Apparently not, so it's my bad on this. As far as getting NSI to switch to SSLv3, I have about as much chance of that as I had of keeping George W Bush from invading Iraq in '03 (and I made some efforts on the latter!). NSI has been notoriously unresponsive and unhelpful on many fronts, which is why they've lost a substantial fraction of their domain name registry business to other, more consumer-friendly registrars. Unfortunately, I still have a few customer domains registered through them and from time to time I have to deal with their account management UI :-( |
