While implementing software to generate .seb files from our LMS im running into issues when decrypting the generated seb file in the browser. After searching online how to debug this, I found someone having a similar issue: https://sourceforge.net/p/seb/discussion/844844/thread/7fa9aa292d/?limit=25#3bf8.
First of al, do we need to prefix the ciphertext with the header described on the github pages? Should this then be included on the documentation website?
Happy to open a PR to update the documentation if this is the case.
While implementing software to generate .seb files from our LMS im running into issues when decrypting the generated seb file in the browser. After searching online how to debug this, I found someone having a similar issue: https://sourceforge.net/p/seb/discussion/844844/thread/7fa9aa292d/?limit=25#3bf8.
First of al, do we need to prefix the ciphertext with the header described on the github pages? Should this then be included on the documentation website?
Happy to open a PR to update the documentation if this is the case.