Encryption / Decryption made simple
OpenPGP.js is a Javascript implementation of the OpenPGP protocol. This is defined in RFC 4880.
a secure dotenv–from the creator of `dotenv`
Wrapper for encrypted localStorage and sessionStorage in browser
[](https://travis-ci.org/auth0/node-xml-encryption)
The *client-node* module includes all of the modules you need to use the AWS Encryption SDK for JavaScript with Node.js.
[](https://travis-ci.org/auth0/node-xml-encryption)
OpenPGP.js is a Javascript implementation of the OpenPGP protocol. This is defined in RFC 4880.
Serialized AES-GCM 256 encryption, decryption and key management in the browser & Node.js
Protect asar archive files from extraction
Encrypt your Redux store.
Encrypt your client storage (available for TS & JS)
The AWS Encryption SDK for JavaScript is a client-side encryption library designed to make it easy for everyone to encrypt and decrypt data using industry standards and best practices. It uses a data format compatible with the AWS Encryption SDKs in other
crypto; from kruptein to hide or conceal
cookies module for egg
JS/TS library for encrypting and decrypting file attachments in Matrix
Encryption utilities for Stacks
Ultra-lightweight PDF encryption (7KB) with real RC4 128-bit encryption. Built for edge environments like Cloudflare Workers. Powers PDFSmaller.com's encryption.
Crypto streams for the browser.
Request Cryptography
Password protect a static HTML file without a backend - StatiCrypt uses AES-256 wiht WebCrypto to encrypt your input with your long password and put it in a HTML file with a password prompt that can decrypted in-browser (client side).
<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://github.com/FiloSottile/age/blob/main/logo/logo_white.svg"> <source media="(prefers-color-scheme: light)" srcset="https://github.com/FiloSottile/a
Automatically provisions and installs locally-trusted TLS certificates for Node.js https servers in 100% JavaScript.
React package for the Evervault SDK
PreciousCargo encapsulates a specific best practice when encrypting large (or small) amounts of data, normally to transmit over the wire via a web service. The strategy is not really complex, but it wasn't readily apparent when I was looking for a solution. Therefore I wrote this gem to make it convenient to not only apply this strategy, but to also make this best practice more easily discovered (hopefully).
This is a gem originated from another gem called permalink. Since I often want a permalink that provides no way to tell the database ids, I came up with the idea about encrypting the id and prepending it to the permalink. For more information about FPE(Format Preserving Encryption), please consult the wikipedia. The encryption method of current release is simply RC4-40 with a configurable key. Note, RC4-40 is not a strong encryption algorithm at all, and you shouldn't rely on it to delivery sensitive information. Also, to prevent inconsistance of encryption, and duplication(although the chance is very low) you should keep your key as a secret and never change it. The original implementation of generating permalink involves a infite loop to check uniqueness in database. It's slow, inefficient and most importantly, it still can't prevent race condition. And since we are using a FPE algorithm on the database id, which is garanteed to be unique from database, we don't need to put ourselves in that inefficient loop. Finally, what's the purpose of this gem? It's only a gem that helps hiding your database ids.
NanoAuth is a super stripped down Rails authentication module. It's comprised (so far) of one file that provides some additional methods to be mixed in to your User model. Over the years I kept tweaking code in various projects and continued to see the same boiler plate code for: * authentication a user via User.authenticate(email,password) * encrypt(password) * authenticated?(password) \ So I decided on some down time to pull all this stuff out and make a nice little gem of it.
DRbService is a framework we use at LAIKA for creating authenticated SSL-encrypted DRb services that provide access to privileged operations without the need to give shell access to everyone. There are a few examples in the `examples/` directory of the gem, which are stripped-down versions of the services we actually use. The current implementation is kind of a hack, but I intend to eventually finish a DRb protocol that does the same thing in a more elegant, less-hackish way, as well as a tool that can generate a new service along with support files for one of several different runtime environments. If you're curious, see the `drb/authsslprotocol.rb` file for the protocol. This will replace the current method-hiding code in `drbservice.rb`, but existing services should be able to switch over quite easily. Or that's the intention.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.