Closed Bug 344327 Opened 18 years ago Closed 18 years ago

Secondary keychains are apparently not searched

Categories

(Camino Graveyard :: OS Integration, defect)

Product:
Camino Graveyard
Component:
OS Integration
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
Camino1.5

People

(Reporter: dkulp_bugzilla, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.4) Gecko/20060613 Camino/1.0.2 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.4) Gecko/20060613 Camino/1.0.2 "Keychain Access" allows for the creation of multiple keychains, with varying levels of security. One may want to create a keychain for storing non-sensitive web passwords that is separate from your login keychain. The login keychain may lock after a certain number of minutes or on sleep, but the new keychain remains open. Anyhow, Camino is apparently only checking the login keychain instead of all keychains, which is what Safari does. Reproducible: Always Steps to Reproduce: 1. Tell Camino to remember an Internet Password 2. In Keychain, move that password to a different Keychain than "Login". 3. Return to site using Camino. Camino will not know the password. Actual Results: Camino loses the password. Expected Results: Camino should know the password because its on a keychain.
Can someone who's more familiar with the Keychain APIs confirm that this is an artifact of our ancient Keychain API support? (I.e., we'll get this for free when we upgrade APIs?) cl
That's what it sounds like from the docs.
Confirming and marking dependent on bug 172842 (the Keychain Services API bug). cl
Status: UNCONFIRMED → NEW
Depends on: 172842
Ever confirmed: true
hm, that's weird, why should camino keep track of moved passwords? How exactly do you "move" a password? In 10.3-, that's def impossible. if by "moving" we mean "delete the old and create a new one", there's no reason why camino should be keeping track of this. i have 3 diff keychains, and camino pulls passwords from all of them.
Keychain bugs -> 1.2.
Target Milestone: --- → Camino1.2
reading this a second time, i'm almost certain that the problem here is not the location of the keychain item but its creator instead. Camino does NOT read keychain items that it did not create itself. it doesn't matter where these items are located, login keychain or not. Therefore the title of this bug should be something like "Keychain items created outside of Camino not recognized"
(In reply to comment #6) > Camino does NOT read keychain items that it did not create itself. it doesn't > matter where these items are located, login keychain or not. That's not a correct statement.
David, are you able to reproduce this with recent nightly builds? I expect that the keychain rewrite solved this.
I tested this and it appears to work now. Thanks.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Moving fixed "1.2" bugs to 1.1 where they were really fixed. Filter on CaminoFixed1.1 for bugmail purposes.
Target Milestone: Camino1.2 → Camino1.1
You need to log in before you can comment on or make changes to this bug.