Closed Bug 1717545 Opened 3 years ago Closed 3 years ago

IRCv3.1: Implement SASL with PLAIN mechanism

Categories

(SeaMonkey :: Chat, enhancement)

enhancement

Tracking

(seamonkey2.53+ fixed)

RESOLVED FIXED
seamonkey 2.90
Tracking Status
seamonkey2.53 + fixed

People

(Reporter: iannbugzilla, Assigned: iannbugzilla)

References

(Blocks 1 open bug)

Details

(Whiteboard: SM2.53.10)

Attachments

(2 files, 3 obsolete files)

Blocks: 1710311
Attached patch 1717545-irc-sasl-CAP-2539.patch (obsolete) — Splinter Review

[Triage Comment]
r/a=me

Attachment #9228229 - Flags: review+
Attachment #9228229 - Flags: approval-comm-release+
Attachment #9228229 - Flags: approval-comm-esr60+
Attached file networks.json

I use a customized networks.json (see attachment) to connect preferably to European servers of libera, and by secure connection. I also use built-in SASL connection with SeaMonkey 2.53.9b1pre (Gianopoulos).

The fact that ChatZilla stores passwords in the password manager separately for each server and port within the network means that when the remote disconects me, and cZ tries to connect to the next server in the list, I get a password prompt hidden by the browser window, Ctrl-6 (Window→IRC Chat) stops working and I have to use the keyboard's "Windows" key to place all windows temporarily side-by-side, select the popup and answer it (or else, temporarily minimize the browser). By the time I have answered the popup, of course the remote has timed me out, so I get one more reconnect but at least with ChatZilla on top.

I don't have this problem with NickServ because I have a "ns identify mypassword" command (which doesn't get echoed in the ChatZilla window) as a network start-up command (in the "Lists" tab of the network preferences). (N.B. I'm the only user of this computer.) Having both SASL and NickServ identification is no problem because if the first one succeeds, the second one just says I'm already identified.

P.S. To view the text of my new attachment, don't click "Details" — click the text of the attachment in comment #2.

Sm 2.53.9b1pre 20210630210003 (and possibly yesterday's)

The popup now appears on top of everything (a mixed blessing), but since the "username" it stores in the Password Manager is not my services account name but my nickname, it makes a difference whether I'm starting SeaMonkey (nickname "tonymec") or reconnecting after a timeout (nickname "tonymec|away") so I cannot even expect that someday all servers/ports defined for libera in my networks.json will be "known" and that the prompts will disappear.

Depends on: 1713470
Attachment #9229309 - Attachment mime type: application/json → text/plain

Changes since last version:

  • Store passwords against network URL and username rather than server URL and nickname.
Attachment #9228229 - Attachment is obsolete: true
Attachment #9232955 - Flags: review?(frgrahl)
Attachment #9232955 - Flags: approval-comm-release?
Attachment #9232955 - Flags: approval-comm-esr60?

Changes since last patch:
Correct msg.sasl.password string to use username rather than nickname

Attachment #9232955 - Attachment is obsolete: true
Attachment #9232955 - Flags: review?(frgrahl)
Attachment #9232955 - Flags: approval-comm-release?
Attachment #9232955 - Flags: approval-comm-esr60?
Attachment #9235248 - Flags: review?(frgrahl)
Attachment #9235248 - Flags: approval-comm-release?
Attachment #9235248 - Flags: approval-comm-esr60?

Also fix pref.sasl.plain.enabled.help

Attachment #9235248 - Attachment is obsolete: true
Attachment #9235248 - Flags: review?(frgrahl)
Attachment #9235248 - Flags: approval-comm-release?
Attachment #9235248 - Flags: approval-comm-esr60?
Attachment #9235249 - Flags: review?(frgrahl)
Attachment #9235249 - Flags: approval-comm-release?
Attachment #9235249 - Flags: approval-comm-esr60?

Comment on attachment 9235249 [details] [diff] [review]
1717545-irc-sasl-CAP-v1_3-25310.patch

LGTM

Attachment #9235249 - Flags: review?(frgrahl)
Attachment #9235249 - Flags: review+
Attachment #9235249 - Flags: approval-comm-release?
Attachment #9235249 - Flags: approval-comm-release+
Attachment #9235249 - Flags: approval-comm-esr60?
Attachment #9235249 - Flags: approval-comm-esr60+

Pushed by frgrahl@gmx.net:
https://hg.mozilla.org/comm-central/rev/36caa928508a
IRCv3.1: Implement SASL with PLAIN mechanism. r=IanN

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Whiteboard: SM2.53.10
Target Milestone: --- → seamonkey 2.90
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: