crypto-js VS umd

The default settings seem to be at fault here, not the implementation it self.

> This is because it both defaults to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and defaults to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993

The fix: https://github.com/brix/crypto-js/commit/421dd538b2d34e7c24a...

crypto-js

CryptoJS 官方說明文件：GitHub。

You might use the .env file, which sits inside a server, to store important passwords and keys to databases and APIs. Keeping it in text inside a .env is risky as it may get exposed if the server is compromised. To avoid this issue, one should use Encryption and Decryption. There are a couple of tools and libraries which offer similar functionality. You can try any of those, but we recommend using CryptoJS or Forge.

Edit: They are likely using this version: https://github.com/brix/crypto-js/releases/tag/3.1.5

The Crypto-JS library should be able to decode this. The docs show a simple method, and I'm using it like so:

crypto-js

I kept searching and stumbled accross Staticrypt. This looked pretty promising. This is based on the crypto.js library and will take a full HTML page and encrypt it. The user will then need to enter the password for the script to un-encrypt it. It sounded pretty neat. I plugged in some HTML code and a password to the site to test it out, and sure enough, it spat out an encrypted page. It looked promising enough to look further into.

Don't even have to change any logic just encrypt on write and decrypt on read with something like this: https://github.com/brix/crypto-js

Check out this fascinating GitHub project for more examples of UMD formats.

UMD (Universal Module Definition) is a set of tricky patterns to make your code file work in multiple environments.

Exports in a umd format so the library works everywhere.

A module format is the syntax we use to define a module. Different module formats such AMD, CommonJS, UMD and System.register have emerged in the past and a native module format is now available since ES6.

Supports circular references

To make UMD build available on both browsers and Node.js, set globalObject option to 'this'.

A modular system that your compiled application will use. You can choose: None, CommonJS, AMD, System, UMD, ES6, ES2015, ES2020 or ESNext. For backend apps/packages ES6 or CommonJS is suitable depending on Node.js version you want to support. For frontend apps ES6 is also suitable. And for support of older browsers and isomorphic applications, UMD is definitely worth choosing.