Open Bug 1720878 Opened 1 year ago Updated 9 months ago

Can't add a TLS exception for IRC server

Categories

(SeaMonkey :: Chat, defect)

SeaMonkey 2.53 Branch
defect

Tracking

(Not tracked)

People

(Reporter: jobbautista9, Unassigned)

References

Details

User Story

Workaround is to add an override via about:config, network.security.ports.banned.override should include 6697 (if the pref does not exist it needs to be created as a string).

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.8

Steps to reproduce:

Try connecting to an IRC server which has a certificate whose Common Name(s) do(es)n't match the domain name of your IRC server. You can use datapacket.hk.ircnet.net port 6697 as a testcase. Then add an exception

Actual results:

The "Add Security Exception" window returns a No Information Available error.

Expected results:

Should be able to proceed with adding an exception.

Depends on: 1720879

The issue is that Gecko, as default, blocks port 6697 see:
https://searchfox.org/mozilla-central/source/netwerk/base/nsIOService.cpp#103
so unless you add an entry for 6697 into network.security.ports.banned.override via about:config the certificate cannot be retrieved.

There is the same issue for certificate exceptions for mailnews, see bug 1694023

Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → All
See Also: → 1694023
Duplicate of this bug: 1738597
User Story: (updated)
You need to log in before you can comment on or make changes to this bug.