1
edit
Changes
→Project News
* '''December 3rd, 2006''' - Phil decided to implement our working code on friday into the current Firefox build. Thanks to MAC1 crashing, a network cable missing from MAC2, and the orange Firefox build for Mac OS X, I didnt accomplish anything.
* '''December 8th, 2006''' - Both MAC1 and MAC2 have been fixed. Myself and Moe began hacking our Keychain code into the Mozilla tree, through the nsPasswordManager.cpp file. This file is primarily used by Firefox to record and retrieve passwords from a flat file system. As we were implementing the code, we realized that FF wont build unless the security framework was included into the build process. Venturing into IRC produced the following results:
:* We have to include the '''-framework Security''' into the build process where ever we are linking in the tree.
:* The following chat was recorded, discussing a new MoCo involvement in the OS X Keychain integration project:
<pre>
20:29 <dolske> ping?
20:31 <dolske> I saw to mention you're working on adding a build flag, and adding the "os x security
framework"?
20:33 <philly> yeah
20:34 <philly> whats up?
20:36 <dolske> What exactly does the latter (OS X) part mean?
20:37 <philly> im working on a project that will add os x keychain support to firefox
20:37 <philly> were trying to get the security framework
20:37 <dolske> ah, that's what I suspected. :-)
20:37 <philly> into the build.
20:38 <dolske> One of the new MoCo guys was startign to look at that too, and I'm starting to whack
passwordmgr with a big stick.
20:39 <philly> yeah.. thats basically what were doing
20:39 <philly> we have working code that add's and retreives keychain items from the keychain manager
20:41 <philly> we have had working code for a while now, but dont know the moz tree well enough to
implement the code.
20:41 <philly> so its a lot of trial and error
20:41 <dolske> You may want to ping Collin Barrett (cbarrett) so you're not duplicating work.
20:41 <philly> will do
20:42 <dolske> Although I think he's not actually starting for a couple of weeks, so I don't know how
much he's around.
20:43 <philly> i'll give me a shout as soon as i see him.. thanks for the info
20:43 <philly> s/me/him/
20:43 <dolske> Looks like timber@lava.net is his current email.
20:44 <dolske> Also... Did you get the build flag added? I'm about to do the same, and was wondering
what was involved. :-)
20:45 <philly> we located flag: -framework Security
20:46 <philly> there could be more
20:47 <dolske> Oh, I thought you were looking at a --enable-moz-foo type flag.
20:47 <philly> yeah.. we dont know if we found the right one
20:48 <philly> i was talking to some of the camino guys about flags
20:48 <dolske> ah.
20:49 <philly> im not sure if those flags are apart of the camino build though.. it appears they know
nothing about the ff build process
20:49 <philly> im a student at seneca college btw.. we have a project page for this
20:49 <dolske> heh, that seems to be a common problem. :-)
20:50 <philly> http://zenit.senecac.on.ca/wiki/index.php/OS_X_Keychain_integration
20:50 <dolske> ah, cool.
20:51 <dolske> oh, Camino already supports Keychain? Hmpf.
20:51 <philly> yeah.. but its not using the latest security framework from apple
20:51 <dolske> ...but they're dropping it? hmm.
20:51 <philly> so they're gonna pull it out
20:51 <philly> otherwise
20:51 <philly> we would be copying some code.. :)
20:51 <dolske> ah, "why" was my next question.
20:52 <dolske> I wonder if they can't use a newer framework because they want to support older OS X
versions?
20:53 <philly> hmm.. i never thought of that
20:53 <dolske> I think FF3 will currently require 10.2 (with 10.3 recommended)
20:56 <philly> yeah.. i think 10.2 is the base for the latest framework
20:56 <philly> there is also a patch that you have to apply
20:57 <philly> bug 360583
21:12 -!- dolske [dolske@moz-46636307.office.mozilla.org ] has quit [Quit: dolske]
</pre>