Re: [gentoo-user] broken seamonkey :(

[lee <lee@yagibdah.de>]

Fernando Rodriguez <frodriguez.developer@outlook.com> writes:

> On Saturday, September 05, 2015 1:05:06 AM lee wrote:
>> >> 
>> >> It doesn't work.  I've imported the certificate now at home, and no
>> >> matter what trust I set or whatever I do, I cannot connect, and I cannot
>> >> add an exception.
>> 
>> I can (have to) do with seamonkey 2.30 at work and mutt at home.  This
>> isn't a long-term solution because it forbids updating the web browser
>> and email clients for everyone at work ever since.
>> 
>> Is this a bug of seamonkey?  I could make a bug report in that case.
>
> Adding the CA certificate and ticking all trust options does work but it seems 
> not all self-signed certs have one.

It worked at work and didn't work at home.  It's weird.

> If when you run openssl s_client -connect 
> host:443 -showcerts it list more than one cert then you want to import the 
> last under authorities.

As far as I can tell, it shows only one certificate.  When I import it,
it shows up correctly.

> You can try backing up and deleting your profile directory, if it works with a 
> new one either go through all the ssl about:config settings and compare them or 
> just start over with new settings and import bookmarks, etc. If you both have 
> the same version then it must not be a change or bug.

It's not that.  I've tried it at work with a seamonkey on a windoze 7 VM
with a seamonkey that had only been used for web browsing and for which
I haven't changed any settings that could be even remotely related to
this.

The inability to add an exception is consistent over at least 5 totally
different machines, Linux and windoze, with at least seamonkey and
thunderbird.  On at least two of these machines, older versions like
seamonkey 2.30, simply let me add an exception while newer versions
don't.  Update seamonkey on the terminal server, create a new user, try
to set up seamonkey so that they can access their email, and you cannot
add an exception.  You have to revert to 2.30, add the exception, and
then you can go back to 2.33.1 and it works because the exception was
added.

So this must either be a bug of seamonkey and its relatives, or a
default setting that has changed with newer versions, or something needs
to be done with all(!) self-signed certificates, or adding exceptions
has been disabled intentionally, which would require another way to do
it because they cannot expect everyone to somehow change their perfectly
fine certificates or to buy signed ones.


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.