As of 2017, Web Cryptography Working Group Working Group is now closed. Maintenance for the W3C Recommendation happens under the supervision of the Web Security Interest Group. But, this community group is still working for future discussion for Web Crtypto. … Continue reading
I gathered candidates of webcrypto use cases in our wiki page: http://www.w3.org/community/webcryptoapi/wiki/Use_Cases. If you have any comments and addings, please don’t hesitate to edit this page. As following is list:
1 Use Case Index
1.1 Primary features
1.1.1 Secure messaging
1.1.2 Encrypted web applications
1.1.3 Storing local storage
1.1.4 Encrypted bill
1.1.5 Client authentifications
1.2 Secondary features
1.2.1 Financial Transaction: Online bank
1.2.2 Credit card process
1.2.3 SSL VPN
1.2.4 Handling S/MIME mail
1.2.5 Handling XML Encryption
Tomorrow (Monday) W3C Web Cryptography workgin group will be doing a public telecon. This will most useful for those who are new to W3C process or are interested in the Working Group and are considering joining but have questions about … Continue reading
I started a draft of Korea WebCrypto UseCase. If you’re interested in financial transations with web cryptography API or Korean experts for security areas. Wiki page: http://www.w3.org/wiki/KoreaWebCryptoUseCase MOTIVATION Over 15 million personal certificates are issued and renewed in every year … Continue reading
Beyond HTTP Authentication: OAuth, OpenID, and BrowserID Time and Location March, 29th 2012 Thursday lunchtime (1130 to 1300) in room 252A just between the SCIM BoF and OAuth WG as part of IETF83 in Paris. Problem Statement While OAuth has … Continue reading
There are some of new features for Web crypto API. Some of things are useful: Netflix’s WebCrypto usecase– content protection and key management Data compression API– there are many packaging method for web apps. In fact, most of app packaging … Continue reading
As following is my reply for “Korean bank” use-case – Rejected? by Anders Rundgren. In conclusion, I think new charter includes Korean usecase too.
2011/12/8 Anders Rundgren
> This use-case (in order to be meaningful) covers all aspects of a key's life:
> from enrollment, to usage, renewals and revocation.
This can be separated primary and secondary area. Mos impoartant part of
Korean use-cases is generationg of *digital signature* with user
certificate in anywhere. Key management can be served by third party
extensions or oneself in key manament option in browers.
> I do not think this group is properly equipped to deal with such a wide scope
> but if somebody wants to take it up, please do!
If someone can afford to try to do, I think it can be do this in working
group too. Many crypto-geeks can be volunteers. BTW, where is VeriSign? :)
> Experiences from other consortium's like the Information Card Foundation
> indicates that the interest in publicly dealing with on-line banking technology
> is moderate; it has always been a "consultant paradise".
You're right. There are many companies to support banks technically in
Korea too. But, many counties have already "law" for digital signature,
http://en.wikipedia.org/wiki/Digital_signatures_and_law. It means it's
standards area in web applications too.
There is several use-cases for web crypto api. Harry Halpin wrote: The ability to select credentials and sign statements can be necessary to perform high-value finanicial transactions as well as secure identity-related claims personal data. The provisioning and use of … Continue reading
According to Harry Halpin, there is a new HTML version of chater. It was added “secondary features” and “out of scope”. The primary features in scope are encryption, decryption, digital signature generation and verification, hash/message digest algorithms, confidentiality algorithms, key … Continue reading
Now many discussions are goning on scopes of Web Cryptography working group charter. I think many of use-cases in cryptography API focused in certificate authority service with personal certificates. But, this is hard to consider another working group because of … Continue reading