Re:Show HN: Password-Protect My File
by michaelt on Wednesday March 05, 2014 @01:30PM
(#7348757)
If a user doesn't trust Dropbox, why would they trust passwordprotectmyfile.com?
I know it claims the file doesn't leave your computer, and that might be true right now, but in five minutes if I visit the page the code could have changed. And it would hardly be user-friendly to ask users to check the minified javascript before using it.
Re:Show HN: Password-Protect My File
by chrisfarms on Wednesday March 05, 2014 @01:27PM
(#7348736)
As soon as my file is readable by javascript it could be sent anywhere by your code. I'm not saying you do, but it could. Therefore this adds an unnecessary risk. I would have to disconnect my machine from the network and clear all the browser storage before reconnecting to even begin to think this was safe.
Just to be clear: I'm not saying it's useless, just that if the file I was encrypting was so important that I needed to encrypt it, doing it in a sandbox that is directly connected to an untrusted third-party wouldn't be a very bright move.
Re:Show HN: Password-Protect My File
by sobel on Wednesday March 05, 2014 @01:38PM
(#7348834)
It's all in one html file, so it will work disconnected from the internet. Download or save the page, turn off your internet, open it in a browser, and encrypt with peace of mind (although the javascript could still use off-line storage and then next time you're online on the page access it, I guess).
Re:Show HN: Password-Protect My File
by herge on Wednesday March 05, 2014 @02:21PM
(#7349133)
I really like this. Especially the self-contained html file you send around afterwards.
You should recommend people to download the html and then save it instead of using the page itself. Maybe make a big download button. Also, remove google analytics from the self-contained version, that way the page should never download/upload anything from the network.
Re:Show HN: Password-Protect My File
by chrisxcross on Wednesday March 05, 2014 @02:10PM
(#7349044)
It's the same as using
openssl aes-256-cbc -in plaintext -out ciphertext
That's as easy and convenient as it can get for me. But it might be helpful if I have to send an encrypted file to someone not able to use openssl or gpg. It's pretty cool to combine an encrypted file with the tools needed to decrypt it :)
I know it claims the file doesn't leave your computer, and that might be true right now, but in five minutes if I visit the page the code could have changed. And it would hardly be user-friendly to ask users to check the minified javascript before using it.
[0] https://github.com/louissobel/ppmf
Just to be clear: I'm not saying it's useless, just that if the file I was encrypting was so important that I needed to encrypt it, doing it in a sandbox that is directly connected to an untrusted third-party wouldn't be a very bright move.
You should recommend people to download the html and then save it instead of using the page itself. Maybe make a big download button. Also, remove google analytics from the self-contained version, that way the page should never download/upload anything from the network.
I'm not too familiar with GnuPG, so I don't know if that's different.
It uses, among others, the Blob API so will not work on older browsers.