- Creation of CMS-Container
- Creation of the random AES key and AES encryption of data in the browser
- Creation of the ASN.1 structure of the CMS container
- Parsing a CMS-Container
- Parse the ASN.1 structure of the CMS container
- Extraction of the encrypted Content Encryption Key
- Extraction of the encrypted data, the algorithm in use etc.
- Decryption of the encrypted data with the encrypted Content Encryption Key
- CryptoJS provides AES and DES encryption and support for the computation of HMAC-Codes. Further CryptoJS provides PBKDF2 for key derivation and offers multiple Hash function. In this project we use CryptoJS for encrypting and decrypting the data to be stored in the CMS container.
- jsrsasign is used for creating the ASN.1 structure of the CMS container. In addition jsrsasign supports parsing of X.509 certificates and thereby simplifies the creation of the ASN.1 structure IssuerAndSerialNumber.
- asn1js offers an ASN.1 parser for decoding DER oder BER encoded ASN.1 data structures. This project uses asn1js for parsing CMS containers.
- jQuery is used for DOM manipulation within the demo application. The jQuery Plugin jQuery Base64 is used for encoding and decoding Base64 data.
The developed proof-of-concept application is not a complete implementation of the CMS standard. Below you can find several limitations of our implementation:
- We currently only support the data type EnvelopedData combined with KeyTransRecipientInfos.
- Further only one RecipientInfo for each CMS container is supported. Our implementation can be easily extended to support multiple RecipientInfo data structures.
- We use AES in CBC mode to encrypt the data. Our implementation can be easily extended to support further encryption algorithms and modes.
- The Content Encryption Key is encrypted in a separate Java application. Therefore the encrypted key and the decrypted result have to be exchanged manually between the Java application and the web application. In order to use this component on the server-side (e.g. when using mechanisms for central key storage) a transport mechanism and methods for matching the right key with regard to the Recipient Info data structure have to be implemented.
- Currently we use Math.rand() as used in CryptoJS for generating random encryption keys. However, Math.random() cannot be considered as a cryptographic strong Random Number Generator. If the implemented components are to be used for protecting critical data in a real world scenario, alternatives for Math.random() have to be integrated. Possible alternatives are provided by W3C Crypto API, Clipperz or SJCL.
It has to be noted, that using cryptography in the web browser raises some security concerns. For more information we recommend the following articles:
- http://tonyarcieri.com/whats-wrong-with-webcrypto (EN)
|Final Report (German only)||1.0||2014-10-27|