Yes, that's pretty much it. Once you do that, you interact with it
as you would other keystores. Of course, there are gotchas and
details about working with it that need elaboration. That will happen
with release notes, mostly documenting the gotchas.
This step is unnecessary, as the KeychainStore is just a
representation of the current user's default keychain. In fact, the
stream argument is ignored altogether. Remember that the keychain
can consist of one or more keychain files. That's what you see when
you open Keychain Access, or when you use 'security list-keychains'.
Having said that, I suppose there's a benefit in having one keystore
represent one keychain file. File an enhancement request and I'll
look into it.
To fill it out a bit.
The security command looks like it is intended to replace certtool
eventually, it also looks like a little more meta in it's handling
of the keychain files themselves.
certtool is more oriented towards looking at certificates you get
from a third party or create yourself using openssl. But yes, I do
see some overlap between the two. You might want to look at the
apple-cdsa group -- the security team monitors that group and can
answer more of your questions there.
I doesn't look to handle the internationalization characters real
nicely. Any quick suggestions to clean that up would be appreciated.
What do you mean here? The KeychainStore? security tool? certtool?
Scott
------------------
Scott Kovatch
Apple Computer
Java Runtime Classes
Cleveland Hts, OH
email@hidden
I am Scott Kovatch, and I approved this message.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
