> returns a static HTML page showing a password prompt that you can now safely upload anywhere Anywhere that you trust, and where the page is hosted securely. For example, a malicious hosting service could alter the password prompt. Or the page as a whole could be put in a frame with a transparent overlay.
(author here) Yeah, or if it's on http someone could MITM and change the script, or if they are malicious extension on the browser the content can be stolen after decryption. That felt implicitly obvious to me, but I think you're right and it wouldn't hurt to put those assumptions in the FAQ. Thanks for the feedback! (If you, or someone else, see other attack vectors, feel free to comment with those)
Password protect a static HTML page, decrypted in-browser in JavaScript
41–48 of 48 posts
Re: Password protect a static HTML page, decrypted in-browser in JavaScript
#42> returns a static HTML page showing a password prompt that you can now safely upload anywhere Anywhere that you trust, and where the page is hosted securely. For example, a malicious hosting service could alter the password prompt. Or the page as a whole could be put in a frame with a transparent overlay.
Clickjacking has been a solved problem for over a decade. Set X-Frame-Options: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-...
Re: Password protect a static HTML page, decrypted in-browser in JavaScript
#43Earlier quoted context omitted.
How do I set this in a shared hosting environment like GoDaddy?
You can set a CSP in the HTML head section using a meta http-equiv tag. It has similar functionality to X-frame-options IIRC.
The old school way is comparing the top level URL with JS and redirecting but there are ways to deal with that
Re: Password protect a static HTML page, decrypted in-browser in JavaScript
#44Earlier quoted context omitted.
(author here) Yeah, or if it's on http someone could MITM and change the script, or if they are malicious extension on the browser the content can be stolen after decryption. That felt implicitly obvious to me, but I think you're right and it wouldn't hurt to put those assumptions in the FAQ. Thanks for the feedback! (If you, or someone else, see other attack vectors, feel free to comment with those)
Would it help to employ the ssl cert in the encryption/decryption process and use it as an IV or so?
Re: Password protect a static HTML page, decrypted in-browser in JavaScript
#45Re: Password protect a static HTML page, decrypted in-browser in JavaScript
#46This is what I'm looking for: a way to put something in public (I'm using Vercel) that "only" me can access (anybody who can decrypt it doesn't need the content that I encrypt).
So you're looking for an authentication and authorization system.
Re: Password protect a static HTML page, decrypted in-browser in JavaScript
#47Re: Password protect a static HTML page, decrypted in-browser in JavaScript
#48https://github.com/blackhillsinfosec/skyhook
Round-trip encrypted file transfer. Uses WASM to decrypt files on the client side.
Aims to bypass IDS.