Hemmelig is available at https://hemmelig.app
You enter https://hemmelig.app, write your sensitive information, expire time, optional password, and click create a secret link. You share the secret link. The receiver of the link opens it, writes the optional password, and retrieves the sensitive information.
When a secret link is created, it gets its unique encryption key that is not saved to the database and only will be part of the URL. This is how the encryption works: encrypt(DATA, YOUR_UNIQUE_ENCRYPTION_KEY). The encryption of the text and files is done in the client; this means the server will get the encrypted information, and nothing in clear text.
- Client side encryption
- Encrypted sensitive information sharing
- Encrypted file upload for signed in users
- Secret lifetime
- Set max views per secret
- Optional encryptet title
- Optional password protection
- Optional IP address restriction
- Encrypted key is part of the URL, and not saved to the database for an extra layer of security
- It will detect if the secret is base64 encoded, and add a button to convert it to plain text on read
- Self-hosted version. Keywords: Regulatory compliance
- hemmeligapp/hemmelig:bleeding-edge (pushed on every commit to main)
- hemmeligapp/hemmelig:weekly (pushed every week on Friday)
- hemmeligapp/hemmelig:daily
- hemmeligapp/hemmelig:v3.4.0 (see the github tags)
- hemmeligapp/hemmelig:latest (pushed on releases)
If you have to follow some sort of compliance, and have to self-host, https://hemmelig.app is available as a docker image. The following is the bare minimum to run the docker image.
# To use this image you need a redis database enabled.
# Example:
#
# $ docker run -p 6379:6379 --name some-redis -d redis
#
docker run -p 3000:3000 -d --name=hemmelig \
-e SECRET_REDIS_HOST=127.0.0.1 \
-v /var/tmp/hemmelig:/var/tmp/hemmelig/upload/files # this is how you mount a local directory if you choose to use disk upload, and not do/s3
hemmeligapp/hemmelig:latestHave a look at the Dockerfile for a full example of how to run this application.
| ENV vars | Description | Default |
|---|---|---|
SECRET_LOCAL_HOSTNAME |
The local hostname for the fastify instance | 0.0.0.0 |
SECRET_PORT |
The port number for the fastify instance | 3000 |
SECRET_HOST |
Used for i.e. set cors to your domain name | "" |
SECRET_REDIS_HOST |
Override this for your redis host address | "" |
SECRET_REDIS_PORT |
The redis port number | 6379 |
SECRET_REDIS_TLS |
If the redis instance is using tls | false |
SECRET_REDIS_USER |
Your redis user name | "" |
SECRET_REDIS_PASSWORD |
Your redis password | "" |
SECRET_MAX_TEXT_SIZE |
The max text size for the secret. Is set in kb. i.e. 256 for 256kb. | 256 |
SECRET_JWT_SECRET |
Override this for the secret signin JWT tokens for log in | good_luck_have_fun |
SECRET_FILE_SIZE |
Set the total allowed upload file size in mb. | 4 |
SECRET_ENABLE_FILE_UPLOAD |
Enable or disable file upload | true |
SECRET_USER_DISABLE |
Disable user registration | false |
SECRET_FORCED_LANGUAGE |
Set the default language for the application. | en |
SECRET_DO_SPACES_ENDPOINT |
The Digital Ocean Spaces/AWS s3 endpoint | "" |
SECRET_DO_SPACES_KEY |
The Digital Ocean Spaces/AWS s3 key | "" |
SECRET_DO_SPACES_SECRET |
The Digital Ocean Spaces/AWS s3 secret | "" |
SECRET_DO_SPACES_BUCKET |
The Digital Ocean Spaces/AWS s3 bucket name | "" |
SECRET_DO_SPACES_FOLDER |
The Digital Ocean Spaces/AWS s3 folder for the uploaded files | "" |
Have a look at the public/locales/ folder.
$ npm install
# Start the frontend
$ npm run dev
# http://0.0.0.0:3000
Feel free to contribute to this repository. Have a look at CONTRIBUTION.md for guidelines.