| 1 |
On Friday 04 Sep 2015 08:54:19 Peter Weilbacher wrote: |
| 2 |
|
| 3 |
> Are you sure that diving right into about:config is the best way? In |
| 4 |
> SeaMonkey, take a look under Preferences -> Privacy & Security -> |
| 5 |
> Certificates. Under "Manage Certificates..." you can import your own |
| 6 |
> certificates which I think is the right way to proceed (although I |
| 7 |
> haven't tried that in a while). In the same dialog, you can also |
| 8 |
> manually add exceptions before you even go to the server. |
| 9 |
> Firefox and Thunderbird have similar dialogs. |
| 10 |
> |
| 11 |
> Peter. |
| 12 |
|
| 13 |
I agree with Peter, it is best you don't disable what is after all a security |
| 14 |
warning mechanism. |
| 15 |
|
| 16 |
In Firefox you are not able to add an exception if you use a Private window |
| 17 |
(Ctrl+Shift+P). Otherwise you should be able to. Alternatively, have you |
| 18 |
tried adding an exception to the server certificate manually as suggested by |
| 19 |
Peter? |
| 20 |
|
| 21 |
You can: |
| 22 |
|
| 23 |
Add your self-signed server certificate in your Server certificates seamonkey |
| 24 |
tab. Updating the seamonkey version ought to retain any certificates you have |
| 25 |
uploaded there. You can also set an exception in the Server's tab. If you do |
| 26 |
not have the server certificate already on your filesystem, you can obtain it |
| 27 |
with: |
| 28 |
|
| 29 |
openssl s_client -connect www.google.com:443 -showcerts |
| 30 |
|
| 31 |
(replace www.google.com with your server of course). |
| 32 |
|
| 33 |
Or, you can try adding it in the RootCA tab and edit its trust there. |
| 34 |
-- |
| 35 |
Regards, |
| 36 |
Mick |
Archives