| Summary: | Enable sasl in pidgin | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jybz <j.biernacki+mga> |
| Component: | RPM Packages | Assignee: | Pascal Terjan <pterjan> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | pterjan, surfzoid |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA7TOO | ||
| Source RPM: | pidgin-2.14.1-4.mga8.src.rpm, pidgin-2.13.0-4.mga7.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: |
Screenshot using pidgin-2.14.1-5.mga8
Debug OutPut With SASL dependancy |
||
|
Description
Jybz
2021-02-10 17:51:00 CET
Created attachment 12329 [details]
Screenshot using pidgin-2.14.1-5.mga8
I have uploaded pidgin-2.14.1-5.mga8 to updates_testing and verified that the option appears, but did not try to connect.CC:
(none) =>
pterjan can you provide an mga 7.1 rpm ? or should have rebuild it my self? CC:
(none) =>
surfzoid I have now tested it and will upload the same fix to Mageia 7. pidgin-2.13.0-5.mga7 is currently building Thank you Pascal for this immediate solution. The screenshot was a good idea. The update will need an Advisory. Assigning this to you until it is ready for QA; you have already fixed it! @Jybz @Eric Can you report back on the update; if it works, that will save QA work. Please say whether for 64 or 32 bit. Assignee:
bugsquad =>
pterjan thanks pascal i'm runing 64 bit mga 7.1 just by curiosity, that was the flag SASL during compil? okay, i made the update and see the check box, i only check SASL author, not the allow plain text. Connection to irc Chanel i had is okay. I'm not sure of how to check SASL used. perhaps we can see that here : pidgin -v|termbin https://termbin.com/2eyt ooops sorry, my bad, i'm tired pidgin -d|termbin https://termbin.com/c2bq Your logs show connection succeeding to gimpnet but not to freenode, maybe it hadn't finished yet? When connecting to freenode I get some lines about trying various the SASL methods. However I decided to test on another machine and it failed to connect when I enabled SASL because none of the methods were accepted. From the logs, Freenode accepts: PLAIN,ECDSA-NIST256P-CHALLENGE,EXTERNAL So I installed sasl-plug-plain and then it worked, we should probably require or at least recommend it from pidgin. I have uploaded a new build with added Requires. Yes Pascal,termbin has truncated the log. You could required sasl plugins since by default it is not checked in pidgin Created attachment 12331 [details]
Debug OutPut With SASL dependancy
Hi,
i did an urpmi pidgin to update with last testing, SASL wasn't asked as dependancy, only :
pidgin 2.13.0 6.mga7 x86_64
pidgin-bonjour 2.13.0 6.mga7 x86_64
pidgin-client 2.13.0 6.mga7 x86_64
pidgin-i18n 2.13.0 6.mga7 noarch
pidgin-meanwhile 2.13.0 6.mga7 x86_64
pidgin-perl 2.13.0 6.mga7 x86_64
pidgin-plugins 2.13.0 6.mga7 x86_64
pidgin-silc 2.13.0 6.mga7 x86_64
pidgin-tcl 2.13.0 6.mga7 x86_64
After, i used urpmi update GUI from MCC, and saw 2 or 3 SASL rpms and 1 purple, i unchecked all other update test and install the concerned.
And more important, sorry, :-) pidgin working :-) Yes the log confirms it worked: (14:00:07) irc: Now trying with CRAM-MD5 PLAIN LOGIN ANONYMOUS (14:00:07) irc: Using SASL: CRAM-MD5 (14:00:08) irc: Unrecognized message: :verne.freenode.net 908 surfzoid PLAIN,ECDSA-NIST256P-CHALLENGE,EXTERNAL :are available SASL mechanisms (14:00:08) irc: Now trying with PLAIN LOGIN ANONYMOUS (14:00:08) irc: Using SASL: PLAIN (14:00:10) irc: Unrecognized message: :verne.freenode.net 900 surfzoid surfzoid!surfzoid@82-65-11-107.subs.proxad.net surfzoid :You are now logged in as surfzoid. Ideally pidgin would be made smarter, parse the list of available mechanisms instead of logging it as "Unrecognized message" and connect using a supported method rather than trying all installed methods, but at least it works. Last chance to assign this to QA if you want this released for Mageia 7. |