- From: Anders Rundgren <anders.rundgren@telia.com>
- Date: Thu, 11 Apr 2013 18:38:21 +0500
- To: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- CC: Samuel Erdtman <samuel@erdtman.se>, "public-webcrypto-comments@w3.org" <public-webcrypto-comments@w3.org>
On 2013-04-11 17:28, Nick Van den Bleeken wrote: Nick, Doesn't your proposal lack of SOP-support? I.e. you leave this part to the user, right? Anders > Hi Samuel, > > You might want to have a look at [1] and if you are more then welcome to send in comments. The API proposal that you find on that page will solve your 'Nexus Personal' use case (some tweaks to the API are still required). I also started an open source implementation of this API to validate the API. It is still in an early stage so far from complete. > > May I add your use cases to [2]? It will be nice if we have a central place for use cases related to Key discovery based on certificates. > > Best regards, > > Nick Van den Bleeken > R&D Manager > www.inventivedesigners.com <http://www.inventivedesigners.com> > > 1: https://github.com/InventiveDesigners/webcrypto-key-certificate-discovery-js/wiki/API > 2: https://github.com/InventiveDesigners/webcrypto-key-certificate-discovery-js/wiki/UseCases > > On 11 Apr 2013, at 00:47, Samuel Erdtman <samuel@erdtman.se <mailto:samuel@erdtman.se>> wrote: > >> Hi, >> >> Relatively early in the webcrypt work I submitted a set of use-cases (to the public list) that where similar to what you sugests but with a clearer focus on certificates and there keys. You can find it here http://lists.w3.org/Archives/Public/public-webcrypto-comments/2012Jul/0000.html. >> >> I have requirements similar to yours but since I submitted my use-cases I have learned a lot and changes my position a bit. I still have these requirements, but I think that it should be coupled to certificates not key attributes, and maybe not in webcrypto. >> >> If I understand the draft that you sent, this discovery mechanism with issuer would not be bound to origin. I think this is wrong since by going outside the SOP we will open pandora's box of security and privacy issues. >> >> One of the things that we would have to consider is that if I can query for the issuer of eIdīs form every site then it would be very easy to track a user, and the issuer of the eId cannot prevent it. In my initial use-case the webpage would not get the key reference but just the signature if the user accepted to sign and something generic none compromising if the user denied the signature. >> >> In a later mail I suggested to bind certificate and keys to a domain with an attribute specifying the domain (posible with wildcard), This would put the issuer in control of the usare of the certificate and keys. >> >> After this I have come more and more to the conclusion that we really should leave smart cards out of webcrypto, for the time being at least. There exists good but propertarian solution for handling smart cards and I thing that to handle smart-cards we would have to have a much wider scoop. I think that we should fokus on solution where we do not need smart cards for example in the nordic countries we are moving away from smart cards for eIdīs and moving towards server-side signares and short lived certificates (one session only) that is issued when the user can provide some other form of strong authentication e.g. OTP. Then we have the mobile situation where smart cards do not suite very well i.e. we need other solutions. Therefor I think that we should let webcrypto solve problems more relevant to the future then smart cards. >> >> Best Regards >> Samuel Erdtman >> Technology Nexus Product Manager >> >> > > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Inventive Designers' Email Disclaimer: > http://www.inventivedesigners.com/email-disclaimer
Received on Thursday, 11 April 2013 13:38:56 UTC