Keychain Experience?

[Frank Engel]

I seriously doubt that an eMail account could be set up through the  
keychain; only the password would be stored there.  The external I am  
developing is quite simple, and is set up for only "application" type  
passwords, while I believe Apple's Mail program uses "internet" type  
passwords -- they are handled by different keychain functions.

Also, in order to work "nicely" with Mail, you will need to add Mail to  
the ACL for the keychain entry.  From what I am seeing, none of this is  
very difficult; you should probably start with Apple's keychain  
introduction:

http://developer.apple.com/documentation/Security/Conceptual/ 
keychainServConcepts/index.html


If you have any familiarity with C programming (it doesn't take much),  
and if you have the Xcode tools installed, and the Rev externals SDK  
(which is a free DL from Rev's site), it should be a fairly simple  
matter to set this up -- as long as the security issue I listed below  
can be overcome.


On Nov 11, 2004, at 11:25, RGould8 at aol.com wrote:

> Hmmmm - - - so you're working on a Rev external that controls  
> keychains?   I
> might be interested in that.   I need to be able to add an email  
> account to
> AppleMail without actually launching AppleMail.   From what I can  
> tell, the only
> safe way to do this is via keychains, due to the encryption when  
> storing the
> password to a new account.   Any idea if your external could be used  
> for such
> a thing?
>
> In a message dated 11/10/04 4:54:13 PM, fde101 at fjrhome.net writes:
>
>
>> Okay, now I am experimenting with accessing the Mac OS X Keychain from
>> an External in Rev.  It seems to be working fine, except for one  
>> slight
>> problem:
>>
>> My standalone and the stack running under Rev are recognized by the
>> Keychain Services as being the same app!
>>
>> If I understand this correctly, this means that *ANY* Rev stack (at
>> least, any Rev stack built with that version of Rev) will be able to
>> access the same keychain data that my stack would on the same  
>> machine. 
>> Needless to say this is quite insecure.  I suspect it might have
>> something to do with the fact that the Rev engine is used in both  
>> cases
>> as the basic "application" part of the program.
>>
>> Does anyone have any experience with this, or know how to work around
>> this problem?  It might take an enhancement request to get this fixed,
>> not sure...
>>
>>
>> Thank you!
>>
>> -----------------------------------------------------------
>> Frank D. Engel, Jr.  <fde101 at fjrhome.net>
>>
>> $ ln -s /usr/share/kjvbible /usr/manual
>> $ true | cat /usr/manual | grep "John 3:16"
>> John 3:16 For God so loved the world, that he gave his only begotten
>> Son, that whosoever believeth in him should not perish, but have
>> everlasting life.
>> $
>>
>>
>>
>> ___________________________________________________________
>> $0 Web Hosting with up to 120MB web space, 1000 MB Transfer
>> 10 Personalized POP and Web E-mail Accounts, and much more.
>> Signup at www.doteasy.com
>>
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
-----------------------------------------------------------
Frank D. Engel, Jr.  <fde101 at fjrhome.net>

$ ln -s /usr/share/kjvbible /usr/manual
$ true | cat /usr/manual | grep "John 3:16"
John 3:16 For God so loved the world, that he gave his only begotten  
Son, that whosoever believeth in him should not perish, but have  
everlasting life.
$



___________________________________________________________
$0 Web Hosting with up to 120MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at www.doteasy.com