npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ashiteam/ashi-aes-node

v1.0.5

Published

AES node encription/decription library for my use

Downloads

14

Readme

AshiTEAM AES

A helper class for my use to encrypt/decrypt binary data and string data and files using a password.

Installing

Install using npm

npm i @ashiteam/ashi-aes-node --save

The password to use for encryption/decryption can be passed in the constructor or as an optional parameter to the encrypt/decrypt functions.

To use, first import, create a variable and use as follows


import { AshiAesNode } from '@ashiteam/ashi-aes-node';

const aes = new AshiAesNode('my password');
const data =
'This is a test string to encrypt. This is a test string to encrypt. This is a test string to encrypt. This is a test string to encrypt';
const encData = aes.encryptString(data);
const decData = aes.decryptString(encData);

console.log(encData);
console.log(data);
console.log(decData);
console.log(decData == data ? 'All good' : 'ERROR');

To encrypt binarry data, use the encryptData & decryptData functions. You can pass in a Buffer and get back a Buffer to and from these functions.


const encBinaryData = aes.encryptData(binaryData);
const decBinaryData = aes.decryptData(encBinaryData);

To pass the password to the functions, do as follows


import { AshiAesNode } from '@ashiteam/ashi-aes';

const aes = new AshiAesNode('');

const encData = aes.encryptString(data, 'password to use');
const decData = aes.decryptString(encData, 'password to use');

To encrypt/decrypt files, do as follows


import { AshiAesNode } from '@ashiteam/ashi-aes';

const aes = new AshiAesNode('password to use');

const enc = aes.encryptFile(inFilePath, outFilePath);
await enc; // or use .then
const dec = aes.decryptFile(inFilePath, outFilePath);
await dec; // or use .then

Some Implementation Details

The key used for encryption/decryption is a 256 bit key generated using pbkdf2 using a random salt of 16 bytes long using 100 iterations. The 100 iterations is the default, this however can be changed to a different value by setting the iterations property.

When encrypting:

  • The random salt is stored as the firs 16 bytes of the output.
  • A randome iv of 16 bytes is generated and used and stored as the second 16 bytes of the output.
  • The encrypted data is stored starting from the 32nd byte

When decrypting:

  • The salt from the first 16 bytes are used to generate the key
  • The second 16 bytes are used as the initial vector (iv)

Note

Data encrypted using other tools or languages (such as Java, C#, ...) can be decrypted by this code (and vice versa) provided the salt & iv are stored as the first 32 bytes, and the key is generated as mentiond above.

Authors

  • Asanga Weerapura - All work

License

This project is licensed under the MIT License.

Acknowledgments

  • node-forge
  • buffer
  • @ashiteam/ashi-aes