Plans password

[pgiraud]

Fixes #15

[l00ptr]

Hi there,

to improve the security and confidentiality of plans, I think it might be worth considering client-side encryption. Encryption at client level could reduce the risk of a malicious user retrieving the data being transferred (for example, between a reverse proxy and explain.dalibo.com).

There are a few project using that kind of encryption (e.g. LUFI, I can try tod find and share more examples if you want.

Best regards,

[pgiraud]

Hi there,

to improve the security and confidentiality of plans, I think it might be worth considering client-side encryption. Encryption at client level could reduce the risk of a malicious user retrieving the data being transferred (for example, between a reverse proxy and explain.dalibo.com).

There are a few project using that kind of encryption (e.g. LUFI, I can try tod find and share more examples if you want.

Thanks. I'll have a look.
Apparently, LUFI relies on Stanford Javascript Crypto Library. But it may be possible to use the Crypto Web API.

[pgiraud]

#51 shows a different implementation (with client-side encryption). This works well. The only possible drawback I see is that it will not be possible (or at least not easy) to post password encrypted plans without the user interface (via cURL for example).

[pgiraud]

As discussed offline, we decided not to encrypt the plans. In the new implementation (8e2e0d9), the password is stored hashed however. It's rather simple but possibly sufficient for now.

End-to-end encryption will possibly be implemented later but would require more important changes.