Cryption - In-Browser AES File Encryption 🔐 with Data Integrity Check 🔍built with React and Redux

・1 min read

Since I was in need of a file encryption/decryption tool that could do its job in the browser without actually talking to the internet, I created Cryption by using React and Redux as a base. It is open-source and has several features like manipulation check and multi-file-upload.

You can check it out here: https://github.com/lagmoellertim/cryption

DISCUSSION (1)
 

Hi Tim-Luca, I'm sorry if I'm poking holes in the comments of your first post on dev.to but I feel like I should speak up given the very specific tool you developed.

Although the intentions are good and React and crypto are definitely useful skills to acquire I have to say that I'm a bit wary of the idea of a program to encrypt files running in a browser, especially if it uses npm dependencies in the browser that lately have been known to be hi-jackable if left untended for long stretches of time.

Theoretically one could inject a JS that sends the data to a third party or modifies the crypto algorithm by... not crypting :D

Think about it: telling people "do not run this while connected" doesn't mean nobody ever will, even inadvertently.

Also, what happens if there's a bug in your code but the user's browser is still serving the bugged version after the update? I have had instances of browser not updating JS files, especially if running on localhost.

Finally: since you can't control the browser the user executes the app in, how can you be sure they are always using a strong random number generator?

As you can't be sure that the user will abide by your recommendation of running it only when offline, it's hard to be sure of the rest.

You write in the README:

Use on local machine without internet

Realistically... most users's machines are often online, if not 24/7. And if the threat model of a user requires a completely disconnected computer, why bother using an in browser crypto tool at all? Isn't it safer to use a native open source tool with a signed binary and peer reviewing?

Turning off the wifi, running the tool, turning on the wifi doesn't really make it fool proof, even if you as the creator are careful.

Sorry if I'm a bit pessimistic here, I understand that it might be a safe tool for your needs, but it might not be for others and that's a little bit worrying.

It's a perfectly valid experiment though, well done!

:-)

Classic DEV Post from Jan 29

CSS and JS Are at War, Here’s How to Stop It

There are a lot of people who love both JS and UX/CSS. If we stop labeling people just as “JS developers” or “UX developers”, we can achieve a ceasefire in the current “JS vs. CSS” war and achieve a mutually benefiting peace.

dev.to is where software developers stay in the loop and avoid career stagnation.

Sign up (for free)