Opened 13 years ago

Closed 7 years ago

Last modified 6 years ago

#1055 closed Defect (Duplicate)

Server password keychain entries have no username

Reported by: narge Owned by: timothy
Component: Colloquy (Mac) Version: 2.3 (Mac)
Severity: Major Keywords:
Cc:

Description

Colloquy does not store usernames in server keychain entries; JVConnectionInspector supplies nil as the account name when accessing server passwords. If the username and password are the only properties that differ between two saved connections, then the same keychain entry will be used for both.

This breaks proxies / bouncers that use the username & server password to distinguish between proxied connections to different servers, including znc (and probably dircproxy, though I haven't tried it).

Change History (6)

comment:1 Changed 13 years ago by narge

The obvious solution is to use [editUsername: stringValue] instead of nil as the account name, but that might conflict with existing keychain entries for nickserv passwords.

comment:2 Changed 10 years ago by jane

  • milestone set to Colloquy 2.4
  • priority changed from Normal to High
  • Severity changed from Normal to Major
  • Version set to 2.3 (Mac)

This needs fixed.

comment:3 Changed 7 years ago by zach

  • Resolution set to Duplicate
  • Status changed from new to closed

#1885 is how Mobile Colloquy solved this problem.

comment:4 Changed 6 years ago by mpdwibble@…

Uh, this issue doesn't appear to actually have been fixed--the only assertion I see going through the linked 'solution' is to make a different hostname/subdomain for the bouncer server for each account, which is absurd.

I'm on 2.4.3 (6011) and I'm getting this same problem. Is this seriously going to be left with such a kludgy workaround?

comment:5 Changed 6 years ago by mpdwibble@…

Uh, this issue doesn't appear to actually have been fixed--the only assertion I see going through the linked 'solution' is to make a different hostname/subdomain for the bouncer server for each account, which is absurd.

I'm on 2.4.3 (6011) and I'm getting this same problem. Is this seriously going to be left with such a kludgy workaround?

comment:6 Changed 6 years ago by anonymous

same here, i always manage to forget about this till i have to setup a fresh account

Note: See TracTickets for help on using tickets.