Closed Bug 372942 Opened 18 years ago Closed 18 years ago

Safari's "Never remember" items are being treated as accounts

Categories

(Camino Graveyard :: OS Integration, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Camino1.5

People

(Reporter: stuart.morgan+bugzilla, Assigned: stuart.morgan+bugzilla)

Details

(Keywords: fixed1.8.1.3)

Attachments

(1 file)

Whee, more keychain bugs! Right now, going to a site that's been Never Remember-ed in Safari causes us to pick up that item and fill the username as "Passwords not saved". We need to check kSecNegativeItemAttr (which I really hope they are setting); probably we won't honor these entries as such for 1.1, but we should definitely skip them.
Attached patch workaroundSplinter Review
> We need to check kSecNegativeItemAttr (which I really hope they are setting); Ah, wouldn't that be great. But of course, they don't, because they like to treat the KS documentation recommendations as a list of things not to do. This just looks for a password consisting only of a space; it seems highly unlikely that anyone would legitimately use (or even be able to use on most sites) that as a password.
Attachment #257681 - Flags: review?(joshmoz)
Comment on attachment 257681 [details] [diff] [review] workaround + // Safari's doesn't bother to set kSecNegativeItemAttr on "Passwords not saved" s/Safari's/Safari/
Attachment #257681 - Flags: review?(joshmoz) → review+
Comment on attachment 257681 [details] [diff] [review] workaround I'll fix the comment on checkin.
Attachment #257681 - Flags: superreview?(mikepinkerton)
Comment on attachment 257681 [details] [diff] [review] workaround sr=pink that's ass.
Attachment #257681 - Flags: superreview?(mikepinkerton) → superreview+
Checked in on trunk and MOZILLA_1_8_BRANCH.
Status: NEW → RESOLVED
Closed: 18 years ago
Keywords: fixed1.8.1.3
Resolution: --- → FIXED
Filed a bug report with Apple, rdar number 5058948.
If you mean about them not setting kSecNegativeItemAttr, I already did (5045684).
I also included that they should set kSecInvsibleItemAttr in my report (it's suggested by the kSecNegativeItemAttr docs for this very situation).
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: