In category: ← Pastebins

About FlashPaper

A one-time encrypted zero-knowledge password/secret sharing application focused on simplicity and security. No database or complicated set-up required.

Github stats:

Commits: N/A
N/A
N/A
Latest commit: N/A

Deploy this app to Linode with a free $100 credit!

Languages/Platforms/Technologies:

Lincenses:

More about FlashPaper

FlashPaper

A one-time encrypted zero-knowledge password/secret sharing application focused on simplicity and security. No database or complicated set-up required.

Demo

https://flashpaper.io

Picture of Main Page

Installation

Docker (Recommended)

The latest release of FlashPaper is available at ghcr.io/andrewpaglusch/flashpaper. 1. Download docker-compose.yml from this repo 2. Edit docker-compose.yml with your customizations 3. Run docker-compose up -d to start FlashPaper 4. Set up a reverse-proxy in front of FlashPaper that terminates SSL/TLS

Traditional

Requirements: PHP 7.0+ and a web server 1. Download and extract the latest release of FlashPaper to the document root of your web server 2. Copy settings.example.php to settings.php and make customizations to that file 3. Disable access logging in your web server's configuration so nothing sensitive (IP addresses, user agent strings, timestamps, etc) are logged to disk

How It Works

Submitting Secret

<random>--secrets.sqlite sqlite database created (if it doesn't already exist)
<random>--aes-static.key randomized 256-bit AES static key created (if one doesn't exist already)
Random 256-bit AES key created
Random 128-bit IV created
Random 64-bit ID created
ID + AES key hashed with bcrypt
Submitted text encrypted with AES-256-CBC using AES key and random IV
Ciphertext now encrypted with AES-256-CBC using static AES key and random IV
ID and AES key joined (known as k)
Random prune date/time generated using prune->min_days/max_days
ID, IV, bcrypt hash, ciphertext, and prune epoch stored in DB
k value returned to user in one-time URL

Retrieving Secret

k value removed from URL
k value split into two parts: ID and AES key
IV, bcrypt hash, ciphertext looked up in DB with ID from k
k bcrypt hash compared against bcrypt hash from DB (prevents tampering of URL)
Ciphertext decrypted with static AES key and IV
Ciphertext decrypted with AES key from k and IV
Entry deleted from DB
Decrypted text sent to user

Submitting Secrets via the API (with `curl`)

FlashPaper can accept secret submissions through a simple API. The retrieval URL will be returned in a JSON object.

Here's what it looks like to submit a secret with curl:

$ curl -s -X POST -d "secret=my secret&json=true" https://flashpaper.io
{"url":"https://flashpaper.io/?k=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}

Settings

`prune`:

enabled: Turn on/off auto-pruning of old secrets from the database upon page load
min_days/max_days: When a secret is submitted, a random date/time is generated between min_days and max_days in the future. After that date/time has elapsed, the secret will be pruned from the database if enabled is set to true. This is to prevent your database from being filled with secrets that are never retrieved. NOTE: Even if enabled is set to false, the prune value will still be generated and stored in the database, but secrets will not be pruned unless enabled is switched to true.

`base_url`:

FlashPaper will try to generate the secret retrieval URL based on information provided by the upstream webserver. This process isn't always 100% accurate. If the secret retrieval URL that FlashPaper creates isn't correct for your setup (this usually happens when you're using a reverse proxy upstream), you can manually specify the URL that FlashPaper will use. For example: A base_url of "https://foo.com/flashpaper" will result in retrieval URLs like "https://foo.com/flashpaper/?k=xxxxxxxxxxxxx".