Earlier quoted context omitted.
> you also need a program that can decrypt/encrypt that format that's just a self-extracting archive, which is a very common idea and easily created as well (very popular with both shareware distribution). The problem is that you have to trust the extracting code to not install anything else malicious. The browser provides the perfect sandbox - you cannot install malware into the system via javascript in the browser,…
And you have to trust that running processes on dish aren't going to make a copy of it. Or that it won't end up stuck in the cache. This is (theoretically) only decrypted in memory (your browser may save a preview image of the tab, I believe Firefox mobile does this, not sure about desktop browsers)
Password protect a static HTML page
291–294 of 294 posts
Re: Password protect a static HTML page
#292Earlier quoted context omitted.
Client side decryption has the benefit that no machine or router in the middle can view or cache the decrypted page without the password.
You mean, unless they tamper with the Javascript to capture the password (or the derived key).
Re: Password protect a static HTML page
#293Earlier quoted context omitted.
I would call any server side or client side code which alters the HTML non-static. A static HTML page is just an HTML file which is stored on the server and displayed as-is in the browser.
That’s not a generally accepted as the definition of a static page. https://docs.aws.amazon.com/AmazonS3/latest/userguide/Websit... > You can use Amazon S3 to host a static website. On a static website, individual webpages include static content. They might also contain client-side scripts. By contrast, a dynamic website relies on server-side processing, including server-side scripts, such as PHP, JSP, or ASP.NET. Am…
Re: Password protect a static HTML page
#294Earlier quoted context omitted.
Leave it to full-stack devs to take care of cryptography
As a newer dev later in life, I love to learn about inter-disciplinary snobbery/riffing. I learned some of what I know from a full stack dev, who was convinced anyone who couldnt do everything "was shit" and "should be something easier like a web developer or IT guy" instead. I'm excited to learn that pure disciplines also look down on full stack devs