Search Results for "encrypt file"

Reproxy is a simple edge HTTP(s) server / reverse proxy supporting various providers (docker, static, file, consul catalog). One or more providers supply information about the requested server, requested URL, destination URL, and health check URL. It is distributed as a single binary or as a docker container. Both HTTP and HTTPS are supported. For HTTPS, static certificates can be used as well as automated ACME (Let’s Encrypt) certificates. An optional assets server can be used to serve static...

High performance, extensible, minimalist Go web framework. Highly optimized HTTP router with zero dynamic memory allocation which smartly prioritizes routes. Build robust and scalable RESTful API, easily organized into groups. Automatically install TLS certificates from Let's Encrypt. HTTP/2 support improves speed and provides better user experience. Many built-in middleware to use, or define your own. Middleware can be set at root, group or route level. Data binding for HTTP request payload...

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. If you specify the s3-region...

Fast files encryption (AES-GCM) package and command-line tool built for speed with Go ⚡ Examples: - Encrypt a path with default options > safelock-cli encrypt path_to_encrypt encrypted_file_path - Decrypt a file > safelock-cli decrypt encrypted_file_path decrypted_files_path - If you want it to run silently with no interaction > echo "password123456" | safelock-cli encrypt path_to_encrypt encrypted_file_path --quiet

krab is a "semi secure" keystore that satisfies the IPFS keystore interface, allowing it to be used natively with many existing IPFS implementations, and tools. It stores keys on disk in a badger datastore, encrypting the keys before being stored in the datastore. Each time a key is fetched, it is decrypted first. A single password is used to encrypt all keys.