484740 - Camino fails to recognize httpAuth Keychain items added by Keychain Scripting on Intel

Status: RESOLVED WONTFIX

(Camino Graveyard :: OS Integration, defect)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Attachment: Example script

I'm not sure this is actually a Camino bug, but Safari does do it successfully, and it's frustrating my password migration script, so here we go.

STR:
1) Add a Keychain item for an httpAuth realm using Keychain Scripting
2) Visit the realm in Camino
--> Camino fails to ask to access the Keychain or fill any values in the sheet
3) Visit the same realm in Safari
--> Safari asks to access the Keychain and logs in

Run the attached script and then visit http://www.ardisson.org/alqahira/auth/ to check this out.

This WFM on 1.6.7pre on PPC and fails on 1.6.7pre and 2.0b3pre on Intel, so I suspect there's an endian bug somewhere.

Comment 1

[Stuart Morgan]

The older keychain API has (had? what OS version are you testing?) an endian bug (see bug 335295), so maybe it's using that. Can you look at the auth type for that item as reported by the "security" command-line tool? Searching by host is generally the easiest way to get the item you want.

Although we should still be checking for both, so maybe that's not it...

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

To summarize from irc: On 10.5 (so presumably on 10.4, too) both Keychain Scripting *and* "security" write endian-afflicted data for the authentication type, so on Intel Macs Camino can't read any[1] keychain entries that have been created programmatically, while Safari can.

[1] For the 'form' and 'dflt' types we use; we do have endian support for the old 'httd' type from bug 335295.

Comment 3

[Chris Lawson (gone)]

Smokey asked me if it would be reasonable to refactor the code to account for the fact that all types can be wrong-endian, and I think that sounds like a good approach, in case someone wants to tackle this and needs ideas.

Comment 4

[Gordon P. Hemsley [:GPHemsley]]

This bug has been buried in the graveyard and has not been updated in over 5 years. It is probably safe to assume that it will never be fixed, so resolving as WONTFIX.

[Mass-change filter: graveyard-wontfix-2014-09-24]