Re: [gentoo-user] broken seamonkey :(

[lee]

Mick <michaelkintzios@×××××.com> writes:

> On Friday 04 Sep 2015 08:54:19 Peter Weilbacher wrote:
>
>> Are you sure that diving right into about:config is the best way? In
>> SeaMonkey, take a look under Preferences -> Privacy & Security ->
>> Certificates. Under "Manage Certificates..." you can import your own
>> certificates which I think is the right way to proceed (although I
>> haven't tried that in a while). In the same dialog, you can also
>> manually add exceptions before you even go to the server.
>> Firefox and Thunderbird have similar dialogs.
>>
>>    Peter.
>
> I agree with Peter, it is best you don't disable what is after all a security
> warning mechanism.
>
> In Firefox you are not able to add an exception if you use a Private window
> (Ctrl+Shift+P).  Otherwise you should be able to.  Alternatively, have you
> tried adding an exception to the server certificate manually as suggested by
> Peter?
>
> You can:
>
> Add your self-signed server certificate in your Server certificates seamonkey
> tab.  Updating the seamonkey version ought to retain any certificates you have
> uploaded there.  You can also set an exception in the Server's tab.  If you do
> not have the server certificate already on your filesystem, you can obtain it
> with:
>
>  openssl s_client -connect www.google.com:443 -showcerts
>
> (replace www.google.com with your server of course).
>
> Or, you can try adding it in the RootCA tab and edit its trust there.

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 think I need to be able to add an exception through the dialog that
pops up when trying to connect since that's the only way that there's a
chance that it will work.


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