From: Anders R. <and...@gm...> - 2013-08-23 13:09:15
|
On 2013-08-23 14:06, Jean-Michel Pouré - GOOZE wrote: > Le vendredi 23 août 2013 à 13:39 +0200, NdK a écrit : >> Your bank asks access to your token. You grant it the right to create >> keys and from this moment it cak create new keys "on your token" when >> needed. I think this step is closer to the acceptance of a cookie. If the issuer also provides a KMK (Key Management Key) during provisioning, keys can be updated although the user must still actually browse to the issuer site. However, one can imagine automatic updates based on attributes supplied with keys. This would work analogous to SW updates. > What you call a "bank" can later access your keyring and add > information. Enrollment process is direct from provider to final > consumer without SO-Officer. Final consumer may not be aware of security > considerations. With Facebook, Google and various online services, there > is a tendency to "overclick" when a flow of information is send to final > user. And who is controlling the security provider and in which country > is situated what you call "cloud" and what is the legislation? Does the > legislation of provider apply or legislation of the user? > > The "bank" is asking for my laptop and tells me "Ok, we can take care of > your laptop, go and have a beer while we add keys in your laptop, under > our own laws". This system is designed to replace passwords, not giving external parties access to your computer. Cheers Anders > Just my 2 cents. > > Kinds regards, > > > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Opensc-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensc-devel > |