Bug 37517 - freenode: set enforce + telepathy-idle/empathy can lead to auth failure
Summary: freenode: set enforce + telepathy-idle/empathy can lead to auth failure
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: idle (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-23 12:59 UTC by jerico
Modified: 2019-12-03 20:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description jerico 2011-05-23 12:59:33 UTC
telepathy-idle: 0.1.10

Steps to reproduce:

/msg nickserv set enforce on
set a false password in your account
try to reconnect
set the correct password in your account
try to reconnect

This produces an "authentication failure" error.

The debug log says:
** (telepathy-idle:18465): DEBUG: _parse_and_forward_one: failed to parse ":anthony.freenode.net NOTICE * :*** No Ident response"
** (telepathy-idle:18465): DEBUG: _parse_message: parsing ":anthony.freenode.net 437 * jerico :Nick/channel is temporarily unavailable"
** (telepathy-idle:18465): DEBUG: _parse_message: parsing ":anthony.freenode.net 451 * :You have not registered"


Workaround:
- connect with a different unregistered nick
- /msg nickserv identify <nick> <correct-password>
- /msg nickserv set enforce off
- log in through empathy/telepathy-idle with the correct password
- /msg nickserv set enforce on
- trying to re-connect through empathy/telepathy works now
Comment 1 GitLab Migration User 2019-12-03 20:09:19 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-idle/issues/29.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.