Page Comparison

...

1. The password hash will be set before the AES encrypted content (bas64 encoded length 344)

2. The password hash will be used and it will be encrypted using RSA (due to javascripts readability of code this is the only solution so the CB can decrypt that hashed password and nobody else)

   1. Using RSA allows to provide every CB with its own secure key while attaching the public key to the CB data in CARA

   2. RSA is efficiently secure

   3. If the password has to be changed a new private/public key pare will be generated

      1. New public password will be distributed by a CARA minor update

      2. The CB will use the new private password and has a fallback for the old one (He has to test against all old passwords because of possible older files)

3. The public key for encrypting the password will be selected by the chosen CB for the report

4. The attachment of the password is only activated by request of the CB

...