WardPearce / paaster

  Paaster.io Paaster is a secure and user-friendly pastebin application that prioritizes privacy and simplicity. With end-to-end encryption and paste history, Paaster ensures that your pasted code remains confidential and accessible. Terms of service | Privacy policy   Help translate paaster! Preview Features • End-to-end encryption. • Memory efficient. • File drag & drop. • Shortcuts. • Paste history. • Themes • Delete after view or X amount of time. • Share via QR code. • CLI Tool • i18n support (Contribute). • Automatic or manual language detection. • No dynamically loaded 3rd party dependencies, meaning malicious code must be present at build time. • Use of & Socket.dev to fight against supply chain attacks & vulnerabilities. Deployment Paaster requires s3 for deployment, you can use a hosted solution or self-host using MinIO. Docker compose Reverse proxy Caddy NGINX Minio Install minio mc cli tool Follow guide here Add instance Create bucket Get credentials Object storage providers • iDrive e2 (no free tier anymore) • Wasabi Hot Cloud Storage • Storj (25GB free tier) • Contabo object storage • Cloudflare R2 • Amazon S3 • Google Cloud Storage Security What is E2EE? End-to-end encryption (E2EE) is a zero-trust encryption methodology. When you paste code into Paaster, it is encrypted locally in your browser using a secret that is never shared with the server. Only people you share the link with can view the paste. Can I trust a instance of paaster not hosted by me? No. Anyone could modify the functionality of Paaster to expose your secret key to the server. We recommend using a instance you host or trust. How are client secrets stored? Client secrets are stored with IndexedDB when the paste is created, allowing for paste history. This method of storage makes Paaster vulnerable to malicious JavaScript, but it would require malicious code to be present when the Svelte application is built. How are client secrets transported? Paaster uses URI fragments to transport secrets, according to the Mozilla foundation URI fragments aren't meant to be sent to the server. Bitwarden also has a article covering this usage here. How are server secrets stored? Server secrets are stored with IndexedDB when the paste is created, allowing for modification or deletion of pastes later on. Cipher Paaster uses the following libsodium functions crypto_secretstream_xchacha20poly1305_*, crypto_pwhash & crypto_secretbox_easy, which is implemented using the libsodium-wrappers-sumo library. Requesting features • Open a new issue to request a feature (one issue per feature.) What we won't add • Paste editing. • Paaster isn't a text editor, it's a pastebin. • Paste button. • Paaster isn't a text editor, when code is inputted it will always be automatically uploaded. • Optional encryption. • Paaster will never have opt-in / opt-out encryption, encryption will always be present. Have any questions? Join our Matrix space