Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Solution to code signature/Autofill/Keychain incompatibility? -> not quite' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Solution to code signature/Autofill/Keychain incompatibility? -> not quite
Authored by: petersconsult on Oct 28, '09 04:49:14PM
I just successfully re-signed the beta with codesign.

to do this, you need to create a Code Signing certificate in Keychain Access, see here:
http://developer.apple.com/mac/library/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html#//apple_ref/doc/uid/TP40005929-CH4-SW2

then you open Terminal (do *not* 'sudo su' for this!) and type:
codesign -s CertificateName -f PathToSafariBeta
I hope this helps!
Peter

[ Reply to This | # ]
Code Signing = Solution to code signature/Autofill/Keychain incompatibility?
Authored by: Camel on Nov 11, '09 05:41:44PM

Peter,

Are you saying that by creating a Code Signing certificate in Keychain Access and entering the relevant lines in Terminal that you fix Safari 4 beta's compatibility with Keychain? Autofill values in the browser are not only complete but remembered in Keychain?

Please advise. I'm going to try this out on another machine tomorrow. Sadly, I just noticed that Safari 4.0.4 still doesn't have a progress bar, etc.

Thanks for your work on this.

Camel



[ Reply to This | # ]
Code Signing = Solution to code signature/Autofill/Keychain incompatibility?
Authored by: petersconsult on Nov 12, '09 07:44:10AM
Hi Camel,
Yes, that is indeed what i'm saying. I've made a copy available http://www.mediafire.com/?mjxg1cwscjn
That way you can see for yourself :-)
Cheers,
Peter

[ Reply to This | # ]
Code Signing = You are Da Man
Authored by: Camel on Nov 12, '09 11:44:03AM

Peter,

I've downloaded your file and followed your instructions. It works great! Using Safari_beta on 10.6.2 with the latest version of Safari (4.0.4) in the Applications folder everything works fine: Autofill/Keychain works again, everything is zippy now and it loads in 64-bit. I could not have asked for more, thank you very much.

IMO, as you have achieved full compatibility - unless anyone says otherwise? - you should repost this hint.

Bravo!



[ Reply to This | # ]
Code Signing = Ben Da Man, You Da Man!
Authored by: petersconsult on Nov 13, '09 04:02:50AM
Hi again Camel,
That's very nice of you, but all the glory rightfully goes to Ben Rockhold.
I just flipped through the developer docs to the chapter on CodeSigning, so if thanks are due, they must be given to Apple's good documentation :-)
If Ben or Rob would like to re-post all of the good info in this hint+thread, and include the file as a demo, I think that it'd be a good idea, but i can't rightfully do it myself...
Be Well!
Peter

[ Reply to This | # ]
I don't mean to insist
Authored by: petersconsult on Nov 14, '09 03:20:02PM
I doubt anyone is still reading this, but there was one last problem with this configuration:
If Safari and SafariBeta were not running, no matter how often you told the "internet preferences" that SafariBeta was your choice, clicking a link in, say, Mail, would open it in Safari (current).
So, I just went into the version.plist file and changed the CFBundleIdentifier from com.apple.safari to com.apple.Safari_beta
also changed CFBundleName to Safari_beta
Finally, I made a duplicate of the preference file (~/Library/Preferences/com.apple.safari) and called it, you guessed it, com.apple.Safari_beta
Now Safari_beta is treated as a proper app by the MacOS 10.5 or 10.6.
I will post the new app asap
Be Well,
Peter

[ Reply to This | # ]