Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Right now, it appears that I can really only query for InternetPasswords, but I need access to SecKeys, SecIdentity, and SecCertificates.
Also, technically, SecKeyChain should be an instance class because you can use SecKeychainCreate() and SecKeychainDelete() to create and delete keychains.
This becomes important because some of the Security APIs take a handle to the keychain as well.
Since I just noticed someone else is interested in this, this is some work I've done to manually bind these APIs that I started working on for my project (until I gave up and decided not to use Apple's keychain):
I'm not sure how correct some of it is as I never tested some of it (a lot of it has been tested because the code was more-or-less lifted from code Michael and I wrote for MonoDevelop, but there's a fair bit of new stuff as well).
Can you provide more color as to what things we need?
Sebastian added a bunch of that stuff recently as well. Check out master and see what's missing.
Looks pretty comprehensive and I don't see anything obvious missing. Will be hard to know for sure until I try to port monodevelop and md-addins over to using Xamarin.Mac's keychain APIs to do certificate lookups, but from what I can tell it looks like everything I need is covered.
I will close for now then. Feel free to poke on #mac or open another bug as needed.
As per comment 4 it looks like that this issue is fixed and working fine, and everything I need is covered, also in comment 5 Chris confirmed for the same.
So as of now I am closing this issue, if any one face this issue so feel free to reopen it again or file separate bug for the same .