public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] broken seamonkey :(
Date: Thu, 03 Sep 2015 20:23:03 -0500	[thread overview]
Message-ID: <55E8F277.2020707@gmail.com> (raw)
In-Reply-To: <87egifm5rx.fsf@heimdali.yagibdah.de>

lee wrote:
> Fernando Rodriguez <frodriguez.developer@outlook.com> writes:
>
>> On Thursday, September 03, 2015 9:53:39 PM lee wrote:
>>> Hi,
>>>
>>> since quite a while, seamonkey and its relatives are completely broken
>>> when it comes to use self-signed certificates.  They just refuse the
>>> connection to the server, blocking you from accessing your email.
>>>
>>> Is there still no solution for this problem?  I'm totally fed up with it
>>> by now.  At work, I have frozen seamonkey at version 2.31 and
>>> thunderbird at some outdated version that still works with the
>>> certificates.  Googling for a solution doesn't reveal one, either.
>>>
>>> Now I need seamonkey to access the email, and I can't very well turn it
>>> back to an outdated version just for that.
>>>
>>> BTW, if this won't be fixed, what are the replacements?
>> This[1] is for firefox but should work similarly. Scroll all the way down to 
>> "bypassing the warning". There's also an about:config option, I *think* it's 
>> this one[2].
> Thank you.  The problem is that it doesn't let me add an exception. Only
> the older versions do that.  All options to add an exception are
> disabled.
>
> There is 'browser.ssl_override_behavior', the value of which is
> 2. Guessing by what that means from [2], that should allow me to add an
> exception.
>
> 'browser.xul.error_pages.enabled' is enabled.  There's also
> 'browser.xul.error_pages.expert_bad_cert', which is disabled.  Let's see
> what that does ...  still cannot add an exception when I enable it.  [3]
> would indicate that it's advisable to set it to "true".
>
> Restarting seamonkey after changing it doesn't help.
>
> There's nothing wrong with the certificate, either.  Older version work
> just fine with it.  Mutt works fine with it.  Gnus works fine with it.
> Evolution works fine with it.  All of those are more recent than
> seamonkey 2.31.
>
> I could resort to unencrypted connections on the LAN to be able to
> upgrade the browsers and MUAs --- for security reasons, ironically ---
> but some ppl with laptops need to be able to connect from anywhere over
> the internet.  So omit all security and use VPN for those to make things
> more secure by not using self-signed certificates but insecure
> connections?
>
>
> [3]: http://kb.mozillazine.org/Browser.xul.error_pages.expert_bad_cert
>
>> [1] https://support.mozilla.org/en-US/kb/connection-untrusted-error-message
>> [2] http://kb.mozillazine.org/Browser.ssl_override_behavior


I'm using seamonkey-2.33.1-r1 and I have not run into this problem.  If
you would like, I can check some settings and compare them to mine to
see if it would help fix yours.  Just let me know what you need. 

Surely this can be fixed.  Maybe I did something and don't recall it??

Dale

:-)  :-) 


  parent reply	other threads:[~2015-09-04  1:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 19:53 [gentoo-user] broken seamonkey :( lee
2015-09-03 20:10 ` Fernando Rodriguez
2015-09-03 23:39   ` lee
2015-09-04  0:08     ` Fernando Rodriguez
2015-09-04  1:23     ` Dale [this message]
2015-09-04  7:54     ` Peter Weilbacher
2015-09-04 10:43       ` Mick
2015-09-04 19:50         ` lee
2015-09-04 20:25           ` Fernando Rodriguez
2015-09-04 23:05             ` lee
2015-09-05  0:43               ` Fernando Rodriguez
2015-09-05 12:06                 ` lee
2015-09-05  1:08               ` Fernando Rodriguez
2015-09-05 10:14                 ` Mick
2015-09-05 16:22                   ` lee
2015-09-05 17:16                     ` Mick
2015-09-06 14:29                       ` lee
2015-09-06 18:35                         ` Mick
2015-09-12 11:54                           ` lee
2015-09-06 19:17                         ` Fernando Rodriguez
2015-09-13 14:23                           ` lee
2015-09-05 13:06                 ` lee
2015-09-05 17:09                   ` Mick
2015-09-05 21:40                     ` Fernando Rodriguez
2015-09-05 22:24                       ` Mick
2015-09-06 13:18                         ` lee
2015-09-06 13:03                       ` lee
2015-09-06 18:44                         ` Fernando Rodriguez
2015-09-06  2:45                     ` lee
2015-09-06 18:12                       ` Mick
2015-09-12 11:20                         ` lee
2015-09-12 11:23                   ` [gentoo-user] SOLVED: " lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E8F277.2020707@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox