____ __ ____
/ __ \____ _____ ____/ /_ ____ / / /_
/ /_/ / __ `/ ___/ ___/ __ \/ __ \/ / __/
/ ____/ /_/ (__ |__ ) /_/ / /_/ / / /_
/_/ \__,_/____/____/_,___/\____/_/\__/
The open-source password management solution for teams
(c) 2015-2016 Bolt Softwares Pvt. Ltd.
(c) 2017 Passbolt SARL
https://www.passbolt.com
Passbolt is distributed under the Affero General Public License v3
Passbolt is an open source password manager for teams. It allows you to securely share and store credentials. For instance, the wifi password of your office, the administrator password of a router or your organisation's social media account passwords, all of them can be secured using passbolt.
Passbolt is different from the other password managers because:
- It is primarily designed for teams and not individuals
- It is free & open source
- It is respectful of privacy
- It is based on OpenPGP, a proven cryptographic standard
- It is easy to use for both novices and IT professionals alike
- It is extensible thanks to its RESTful API
Find out more: https://www.passbolt.com
You can try a demo of passbolt at https://demo.passbolt.com.
You will need to install a plugin, you can find some help here: https://www.passbolt.com/help/start/firefox
You can install passbolt on your own machine. Follow the instructions on the website here: https://www.passbolt.com/help/tech/install
Please check out CONTRIBUTING.md for more information on how to get involved!
Please only use github to report bug or make a pull request.
If you want to make a feature request or if you are having an issue when installing your own passbolt instance you should seek help first from the community here: https://community.passbolt.com/
If you've found a security-related issue in passbolt, please don't open an issue on GitHub. Instead contact us at security@passbolt.com. In the spirit of responsible disclosure we ask that the reporter keep the issue confidential until we announce it.
The passbolt team will take the following actions:
- Try first to reproduce the issue and confirm the vulnerability.
- Acknowledge to the reporter that we have received the issue and are working on a fix.
- Get a fix/patch prepared and create associated automated tests.
- Prepare a post describing the vulnerability and the possible exploits.
- Release new versions of all affected major versions.
- Prominently feature the problem in the release announcement.
- Give credit in the release announcement to the reporter if they so desire.