Bug 397576 - Konversation fails to join protected channels
Summary: Konversation fails to join protected channels
Status: RESOLVED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.7.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
: 397917 399098 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-08-18 10:28 UTC by kdebuac.rhn
Modified: 2020-03-29 06:45 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
log file (2.67 KB, text/plain)
2018-08-18 10:29 UTC, kdebuac.rhn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kdebuac.rhn 2018-08-18 10:28:49 UTC
Identification takes place after /join commands, preventing Konversation from joining some saved channels automatically.

Steps to reproduce:

- Save a server and a channel with +r mode (e.g. #coreboot on Freenode)
- Connect to the server

Actual result:

- Channel not joined

Expected result:

- Channel joined, just like the unprotected ones
Comment 1 kdebuac.rhn 2018-08-18 10:29:56 UTC
Created attachment 114474 [details]
log file
Comment 3 kdebuac.rhn 2018-08-18 11:44:12 UTC
Thanks, this workaround works.
Comment 4 Christian (Fuchs) 2018-08-18 12:38:22 UTC
(In reply to kdebuac.rhn from comment #3)
> Thanks, this workaround works.

This is not a workaround, but rather the proper solution. 

Delaying autojoins would be a workaround, since there is no well defined standard that would tell you when you identified, so you'd either have to blindly wait or poll, which both is far from ideal. 

SASL was made for this and should be used on networks that do support it  (most bigger ones, by now)
Comment 5 kdebuac.rhn 2018-08-18 12:50:55 UTC
I called this a workaround, cause it's a proper solution for a particular variation of the problem: how to log into networks which support SASL, or how to set up an IRC server.

From what you're saying, there might be no proper solution for networks which only support nickserv, but then any solution is a workaround. Granted, I didn't specify the auth mechanism.
Comment 6 Christian (Fuchs) 2018-08-18 12:53:35 UTC
(In reply to kdebuac.rhn from comment #5)

> From what you're saying, there might be no proper solution for networks
> which only support nickserv, 

There indeed isn't.

> but then any solution is a workaround. 

You specifically asked for freenode, mind, and we do support SASL since quite a long time.

With your line of argumentation you could also call SSL/TLS a workaround instead of a solution, because e.g. not every website is reachable via https. In my opinion it's dangerous to call proper solutions which people should adapt to "workarounds", as it gives the idea that there might be something better (coming). 

Fuchs
Comment 7 Kai Uwe Broulik 2018-08-27 09:56:24 UTC
*** Bug 397917 has been marked as a duplicate of this bug. ***
Comment 8 Kai Uwe Broulik 2018-08-27 09:57:06 UTC
SASL is *the* solution. Closing.
Comment 9 Christian (Fuchs) 2018-09-26 11:06:02 UTC
*** Bug 399098 has been marked as a duplicate of this bug. ***
Comment 10 Peter Simonsson 2020-03-29 06:45:16 UTC
Git commit 74f707e2532d598ee616a9b288a0ee22d43630fb by Peter Simonsson, on behalf of Christian Christiansen.
Committed on 29/03/2020 at 06:45.
Pushed by psn into branch 'master'.

Changed default auto join from NickServ to SASL.

Summary:
NickServ often doesn't function well with auto join, so changed
default to SASL PLAIN. Included message for NickServ, recommending
SASL.
Related: bug 400362, bug 382924

Reviewers: #konversation, psn

Reviewed By: #konversation, psn

Subscribers: psn, #konversation

Tags: #konversation

Differential Revision: https://phabricator.kde.org/D28329

M  +1    -1    src/identity.cpp
M  +5    -3    src/identitydialog.cpp

https://commits.kde.org/konversation/74f707e2532d598ee616a9b288a0ee22d43630fb