https://github.com/mpankajarun/file-encryption-and-decryption

This app is an experiment that will allow people to choose files from their computers and encrypt them client-side with a pass phrase.
https://github.com/mpankajarun/file-encryption-and-decryption

cryptography cryptojs javascript

Last synced: 6 days ago
JSON representation

This app is an experiment that will allow people to choose files from their computers and encrypt them client-side with a pass phrase.

• Host: GitHub
• URL: https://github.com/mpankajarun/file-encryption-and-decryption
• Owner: MPankajArun
• Created: 2018-01-04T12:52:23.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2018-01-04T13:00:15.000Z (almost 7 years ago)
• Last Synced: 2024-02-03T23:48:47.108Z (10 months ago)
• Topics: cryptography, cryptojs, javascript
• Language: CSS
• Size: 10.7 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# File Encryption and Decryption

This app is an experiment that will allow people to choose files from their computers and encrypt them client-side with a pass phrase.

 No server-side code will be necessary, and no information will be transferred between client and server. To make this possible we will

 use the HTML5 FileReader API, and a JavaScript encryption library - CryptoJS.

Note that the app doesn't encrypt the actual file, but a copy of it, so you won't lose the original. But before we start, here are a 

few issues and limitations:

Issues and limitations

The 1MB limit

If you play with the demo, you will notice that it doesn't allow you to encrypt files larger than 1mb. I placed the limit, because the

 HTML5 download attribute, which I use to offer the encrypted file for download, doesn't play well with large amounts of data. Otherwise

 it would cause the tab to crash in Chrome, and the entire browser to crash when using Firefox. The way around this would be to use the

 File System API and to write the actual binary data there, but it is supported only in Chrome for now. This is not an issue with the 

 encryption speed (which is quite fast), but with offering the file for download.

What about HTTPS?

When it comes to encrypting data and securing information, people naturally expect the page to be loaded through HTTPS. In this case I

 believe it is not necessary, as apart from the initial download of the HTML and assets, no data is transferred between you and the server - 

 everything is done client-side with JavaScript. If this bothers you, you can just download the demo and open it directly from your computer.

How secure is it?

The library that I use - CryptoJS - is open source, so I believe it to be trustworthy. I use the AES algorithm from the collection, which is 

known to be secure. For best results, use a long pass phrase that is difficult to guess.