Privly is a developing set of browser extensions for protecting content wherever it is posted on the internet. This extension allows users to view content on any website, without the host site being able to read the content. For more information on what Privly is, read about us.
Eagle Owl Alpha Version
We are currently fixing bugs and developing the injectable applications to package into the extension. For more information about our development path, please see the central wiki.
The Privly Chrome extension is currently maintained by Sean McGregor, on behalf of the Privly Foundation.
This extension currently supports:
- Contextual Posting: Posting to any website by right-clicking a form element.
- Locally stored applications: The Chrome extension runs no remote-code.
- PlainPost Application: The PlainPost application supports content injection of web pages from any source domain. Note: the injected web pages do not include external media and code.
- ZeroBin Application: The ZeroBin application encrypts content with a key unique to the URL. Anyone with access to both the host page and the content server will be able to decrypt the content. Anyone without access to the server will be unable to decrypt the content.
- Security glyph: Every Chrome extension places a unique security glyph above Privly content when you hover over it.
- Options Page: The extension now has an options page that allows you to select content servers, add to a domain whitelist, and run automated code tests.
- User-defined Whitelists: Users can now add domains to their "whitelist." This means any domain you trust to deliver content will be able to add a layer of privacy on top of your browsing experience.
- Augmented Browsing Toggle: When you turn off Privly, the web page you are viewing will be restored to the un-augmented view.
- Message Interface to Compiled Code: See the nacl branch of the repository.
- Testing Library: The Jasmine testing library is integrated with the extension.
Extension integration test cases are found at test.privly.org. If you have discovered a bug, only open a public issue on GitHub if it could not possibly be a security related bug. If the bug affects the security of the system, please report it privately at privly.org. We will then fix the bug and follow a process of responsible disclosure.
Discussion of system concepts and high level processes are found in the central wiki. If you want to develop an injectable application, look in the privly-applications folder.
Foundation Home
Privly Project Repository List
Development Mailing List
Testing Mailing List
Announcement Mailing List
Central Wiki
Submit a Bug
IRC
Production Content Server
Development Content Server
Download Extension
You can install the latest release version of the extension from Google.
Email:
Community [the 'at' sign] privly.org
Mail:
Privly
PO Box 79
Corvallis, OR 97339
IRC:
Contact the Nick "smcgregor" on irc.freenode.net #privly
Bug:
If you open a bug on this repository, you'll get someone's attention