keychain-announce Mailing List for Keychain Framework
Status: Abandoned
Brought to you by:
wadetregaskis
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Wade T. <wad...@ma...> - 2006-05-20 17:07:03
|
Yep, believe it or not, after about 18 months of trying to get out of it, I've finally actually gone and got top of tree building again. Hooray! :D Even better, I've fixed up the last few HeaderDoc issues, so now the documentation generates cleanly. I've thrown it up on the webpage at http://keychain.sourceforge.net/Documentation/MasterTOC.html for those who want a quick peruse. Wade Tregaskis ICQ: 40056898 AIM, Yahoo & Skype: wadetregaskis MSN: wjt...@st... iChat & email: wad...@ma... Jabber: wad...@ja... Google Talk: wad...@gm... http://homepage.mac.com/wadetregaskis/ -- Sed quis custodiet ipsos custodes? |
From: Wade T. <wjt...@st...> - 2004-08-31 09:36:34
|
I've finally put the Keychain framework into CVS (on Sourceforge). The version in CVS contains a lot of additions since the latest file release - lots of bug fixes as have been reported since that time. There's no guarantee it'll actually build in it's initial import - I'm in the middle of a few things and not likely to finish them soon. But it should be fairly trivial for people to extra new copies of their existing files (ignoring any new ones), so as to get around the problems they've been experiencing. Wade Tregaskis (aim: wadetregaskis, icq: 40056898, msn: wjt...@st...) -- Sed quis custodiet ipsos custodes? |
From: Wade T. <wjt...@st...> - 2003-10-06 12:37:03
|
Just a minor release to fix a fairly substantial set of bugs with the methods for retrieving KeychainItem's and passwords, and to provide an improvement to the methods for setting passwords, in order to allow for existing entries. The latter change will break existing code, since a new parameter has been added to the two relevant methods. Special thanks goes to Mark Ackerman, who both spotted and fixed these problems. On a general note, I apologise for the terrible delay on this release, and how insignificant it is. As usual, the inner workings of the Distributed Objects system are driving me insane, so that's still my current focus point. Wade Tregaskis -- Sed quis custodiet ipsos custodes? |
From: Wade T. <wjt...@st...> - 2003-07-22 03:45:21
|
The framework has been updated, although it's just a work-in-progress update, with no major changes. Keychain events are now posted as notifications, I've added a few extra methods here and there to the existing classes (KeychainItem's now have a proper description method, for example), and patched a few more memory leaks. The first release of Security Manager is up. This app is aimed at end-users, and my intention is to make it the singular app to use with regards to keychain and security operations. At present it simply creates keys, certificates and identities, but this will be expanded in future. I'll probably fold in the functionality of the 'Keychain Demo' project soon. Keychain Logger is a simple CLI app which, as the name suggests, logs keychain events to file. Simple. Included in the logs are time stamps, paths to apps which trigger events, info about the keychain item effected (if any), etc. All the stuff you'd expect. I'll hopefully find time to slap a nice little GUI onto this, so it's fit for public consumption. Wade Tregaskis -- Sed quis custodiet ipsos custodes? |
From: Wade T. <wjt...@st...> - 2003-06-25 08:21:56
|
The 25th June 2003 release is just a working snapshot, and as such some newer things may be incomplete or dysfunctional. Standard disclaimer applies. Other than finally including a proper license definition, new features include [finally] being able to add identities to a keychain, to retrieve all identities regardless of what they provide, and a host of little bug fixes - I zapped a couple of hundred memory leaks which were the result of poor x509 class definitions. Luckily the x509 classes aren't all used yet. The brings me to another point, which is with regards to the x509 classes - yes, they will become [eventually] the standard mechanism for doing things like generating certificates and the like. It's just that at present I'm working on getting simple functionality down pat, and not worrying too much about the design details. A consequence of this is the inevitable changes that will be made some time in future, which will break backward compatability. I'll try to keep these to a minimum - indeed, where possible I'll leave in old methods as deprecated but functional - but please don't say I didn't warn you. The framework mechanism under OS X is quite capable of handling parallel versions, so I don't imagine it will be too difficult a transition for anyone. Wade Tregaskis -- Sed quis custodiet ipsos custodes? |
From: Wade T. <wjt...@st...> - 2003-05-26 12:34:34
|
Just a note that I've posted the latest source up on SourceForge. This update has quite a few unfinished bits and pieces in it, because I wasn't aiming for a particularly well-rounded release - just an update, to fix some noticeable bugs in the previous version. I'm working on x509 support, and have added something like 20 new classes for it, mostly as wrappers around CSSM structures. I'm still puzzling over the memory management behind this, so even though these classes are largely useless at the moment, any tips or bug reports would be greatly appreciated. I've extended a few classes, such as the Keychain class, to allow you to find keychains all over the local computer, including for other users, and open these keychains as you'd expect. These new functions are well tested, although how well they actually work on a network machine remains to be seen. Another thing that's new is two methods of the Certificate class to retrieve and set the default certificate for the current user. Note that these have not been tested - not even a little bit. They may not work at all. Until I get the code working to actually generate a certificate from scratch, I can't very well test much else in this area. On that note - certificate generation - I've been trying to lay the ground work in various places, including the x509 classes previously mentioned. How close I am I don't know, although I may very well add a quick hack for the time being, using code from Apple's certtool. The final thing of note is that the framework has now passed 10000 lines of code - 10019, to be exact. Hooray for arbitrary, meaningless milestones! :) Wade Tregaskis -- Sed quis custodiet ipsos custodes? |
From: Wade T. <wjt...@st...> - 2003-05-14 09:00:50
|
I've updated the Keychain framework on Sourceforge. New in this version is asymmetric encryption/decryption and signing/verifying, as well as limited support for key wrapping - there appears to be a bug in Apple's CSP which is preventing keyed wrapping from working. There's also several methods for generating cryptographically-random data, of any length. This uses the Yarrow algorithm, as used for /dev/random under Darwin. Other than that it's just a whole bunch of little changes here and there. Wade Tregaskis |
From: Wade T. <wjt...@st...> - 2003-05-09 02:24:50
|
I've posted the latest version of the Keychain framework on Sourceforge. Notes: There is a known issue in this version, which is that the validity dates for generated keys are not respected. This is a bug in Apple's Security framework, and should be fixed in the next release of that framework. If that seems to be taking too long - or someone desperately needs validity dates - I may investigate a temporary workaround. Changes: * Key generation now works, for symmetric and asymmetric keys * Category extension to the NSData class allows for symmetric encryption/decryption and MAC generation/verification * Fixed up some of the strings files (missing semicolons, missing entry for CSSM_ALGID_AES, etc) As you can see, I'm keeping up with my promise of fixing up the cryptography side of things. There's a lot of work yet to be done, though. I've also posted a CLI tester application which proves that the various new features work. I'll be building this into a full-featured testing utility as I do more development, so I can verify the functionality of each new release. Wade Tregaskis |
From: Wade T. <wjt...@st...> - 2003-04-16 10:27:55
|
The first public release of the Keychain framework is now available from the project page on Sourceforge. Enjoy! :) Wade Tregaskis |