Search Results for "everything"

...We will demonstrate some simple build recipes for Linux, Mac, and Windows operating systems. These recipes assume a newly installed system with default installs of dependency packages. The Windows instructions install everything in your current directory (where you run the build process). The AWS Encryption SDK for C can be used with AWS KMS, but it is not required. For best results when doing a build with AWS KMS integration, do not install aws-c-common directly. Build and install the AWS SDK for C++, which will build and install aws-c-common for you (see the C++ SDK dependencies here).

...Whether you're managing personal passwords or organizing team credentials, KOSH provides multi-layered military-grade encryption and an intuitive interface to keep everything safe.

Easy and fast file sharing from the command-line. This code contains the server with everything you need to create your own instance. Transfer.sh currently supports the s3 (Amazon S3), gdrive (Google Drive), storj (Storj) providers, and local file system (local). For easy deployment, we've created a Docker container. For the usage with a AWS S3 Bucket, you just need to specify the following options, provider, aws-access-key, aws-secret-key, bucket, and s3-region.

...It has tools that we scrapped together over our last few projects, and that we found were hard to implicate. So what we did was boil them down for your ease of use. Not everything is super glamorous, and there is nothing in this library you cant already do yourself, the idea is simply to take one thing out of your hands, so that you can focus on coding the important stuff. See features for some examples of code you'll find in BTCore.

This is the extended euclidean algorithm implemented in haskell. It will put every single step of the algorithm in a file and show the actual result and everything in between.

Zero-knowledge, decentralized password manager. No email, no account, no server that can read your vault: everything is encrypted on your device with XChaCha20-Poly1305 and Argon2id before it leaves, then stored on IPFS as content-addressed fragments. Metadata is encrypted too: device names, sync data and beneficiary info never exist in plaintext on any server. Sync runs on encrypted CRDTs with no server involved in the merge. Recovery is Shamir Secret Sharing (3-of-5) across five channels, no trusted third party. ...