Dépôt pour Privatebin implémentation Chapril. https://paste.chapril.org/
Go to file
El RIDO 8b38e26735 add codeclimate settings 2016-07-06 13:20:14 +02:00
cfg introduce new zerobincompatibility option, replacing the base64 one, if it is enabled, delete tokens use sha256; added per paste salt with server salt fallback; this resolves the points 2.2 & 2.9 in #103 2016-07-06 11:37:13 +02:00
css small code style improvements, trying to get phpunit with hhvm to work in travis 2016-07-05 17:23:25 +02:00
doc Link to HTTPS PHPDoc site 2016-07-03 17:46:10 +02:00
i18n Improve plural forms 2016-07-02 10:17:09 +02:00
img Minify images with https://tinypng.com/ 2016-07-03 17:52:08 +02:00
js small code style improvements, trying to get phpunit with hhvm to work in travis 2016-07-05 17:23:25 +02:00
lib introduce new zerobincompatibility option, replacing the base64 one, if it is enabled, delete tokens use sha256; added per paste salt with server salt fallback; this resolves the points 2.2 & 2.9 in #103 2016-07-06 11:37:13 +02:00
tpl updating showdown library, adding support for tables and strikethrough, 2016-05-22 16:18:57 +02:00
tst introduce new zerobincompatibility option, replacing the base64 one, if it is enabled, delete tokens use sha256; added per paste salt with server salt fallback; this resolves the points 2.2 & 2.9 in #103 2016-07-06 11:37:13 +02:00
.codeclimate.yml add codeclimate settings 2016-07-06 13:20:14 +02:00
.csslintrc add codeclimate settings 2016-07-06 13:20:14 +02:00
.editorconfig Add editorconfig file 2016-07-03 14:21:05 +02:00
.eslintignore add codeclimate settings 2016-07-06 13:20:14 +02:00
.eslintrc add codeclimate settings 2016-07-06 13:20:14 +02:00
.gitattributes improving git archive output 2015-09-19 17:38:04 +02:00
.gitignore adding support for automatic code coverage generation into codacy 2016-07-05 17:01:26 +02:00
.htaccess.disabled Add a (disabled by default) .htaccess file to block out robots and other link scanning agents. 2016-02-16 17:36:28 +05:30
.travis.yml adding codeclimate coverage reporting to travis 2016-07-06 12:09:19 +02:00
CHANGELOG.md Updated credits and changelog 2015-11-29 18:23:38 +01:00
CREDITS.md Add line break 2016-07-03 18:10:01 +02:00
INSTALL.md updating database documentation 2015-11-01 17:10:36 +01:00
LICENSE.md compiling license file, resolves #85 2016-05-21 09:18:00 +02:00
README.md Add Travis badge 2016-07-04 14:00:49 +02:00
composer.json adding codeclimate coverage reporting to travis 2016-07-06 12:09:19 +02:00
favicon.ico Add favicon 2015-11-29 17:50:50 +01:00
index.php incrementing version 2016-05-21 09:15:52 +02:00
robots.txt Revert order change 2016-07-03 13:09:47 +02:00

README.md

ZeroBin 0.22

Build Status Codacy Badge

ZeroBin is a minimalist, opensource online pastebin where the server has zero knowledge of pasted data.

Data is encrypted/decrypted in the browser using 256 bit AES.

This is a fork of ZeroBin, originally developed by Sébastien Sauvage. It was refactored to allow easier and cleaner extensions and has now much more features than the original. It is however still fully compatible to the original ZeroBin 0.19 data storage scheme. Therefore such installations can be upgraded to this fork without loosing any data.

What ZeroBin provides

  • As a server administrator you don't have to worry if your users post content that is considered illegal in your country. You have no knowledge of any of the pastes content. If requested or enforced, you can delete any paste from your system.

  • Pastebin-like system to store text documents, code samples, etc.

  • Encryption of data sent to server.

  • Possibility to set a password which is required to read the paste. It further protects a paste and prevents people stumbling upon your paste's link from being able to read it without the password.

What it doesn't provide

  • As a user you have to trust the server administrator. If the server you use does not use HTTPS (which is not recommend!) you also have to trust your internet provider and any country the traffic passes not to inject any malicious javascript code. All ZeroBin installation should use HTTPS. Ideally secured by HSTS and HPKP using a certificate either validated by a trusted third party (in most cases Certificate Authorities) or self-signed by the server operator, validated using a DNSSEC protected DANE record.

  • The "key" used to encrypt the paste is part of the URL. If you publicly post the URL of a paste that is not password-protected, everybody can read it. Use a password if you want your paste to be private. In this case make sure to use a strong password and do only share it privatly and end-to-end-encrypted.

  • A server admin might be forced to hand over access logs to the authorities. ZeroBin encrypts your text and the discussion contents, but who accessed it first might still be disclosed via such access logs.

  • In case of a server breach your data is secure as it is only stored encrypted on the server. However the server could be misused or the server admin could be legally forced into sending malicious JavaScript to all web users, which grabs the decryption key and send it to the server when a user accesses a ZeroBin.
    Therefore do not access any ZeroBin instance if you think it has been compromised. As long as no user accesses this instance with a previously generated URL, the content cannot be decrypted.

Options

Some features are optional and can be enabled or disabled in the configuration file:

  • Password protection

  • Discussions

  • Expiration times, including a "forever" and "burn after reading" option

  • Markdown format support for HTML formatted pastes

  • Syntax highlighting for source code using prettify.js, including 4 prettify themes

  • File upload support, images get displayed (disabled by default, possibility to adjust size limit)

  • Templates: By default there is a bootstrap CSS and a "classic ZeroBin" theme and it is easy to adapt these to your own websites layout or create your own.

  • Translation system and automatic browser language detection (if enabled in browser)

  • Language selection (disabled by default, as it uses a session cookie)

Further resources

Run into any issues? Have ideas for further developments? Please report them!