On 2012-07-26 12:24, David Woodhouse wrote: <snip> > >> My same concerns would apply to private keys. > > An application-specific 'third slot' would certainly address that > concern.
</snip> IMO, private keys is a very different topic because they are not really "owned" by the user and if misused they could hurt not only the user but the RP as well. There seems to be two ways ahead: 1. Let each application manage/own its private keys 2. Let the system manage private keys and limit misuse by ACLs Although #1 may look straightforward, it has a dark side as well: it requires that enrollment is (in some way) programmatically associated with the application. Microsoft is apparently advocating this scheme in Windows 8: http://code.msdn.microsoft.com/windowsapps/Certificate-Enrollment-SDK-7ecf4976/sourcecode?fileId=52037&pathId=541597545 I'm betting on #2 which though requires major changes along the system stack. All schemes have their pros and cons so why should this be any different? :-) Anders -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
