Skip to content

Perspectives Roadmap

Dave edited this page Jun 28, 2016 · 12 revisions

This page outlines the plans for Perspectives features that are relevant and visible to users, both short-term and long-term. It will be updated whenever features are completed or plans change (see the top of the page to note the time of last update).

Features and fixes are tracked using GitHub Issues. This page is meant to simply collect and group the overall state of current issues to show our current priorities.

Questions, comments, and suggestions about the Perspectives Roadmap should be sent to the mailing list.

Current short-term priorities

  1. Client #143 Fix getRecentBadCerts behaviour -- lambdor
  2. Client #132 Add distrust all Authorities button -- lambdor
    1. additional features
  3. Server #46 Make default notaries more responsive/set up nginx proxies on default notaries -- daveschaefer
  4. Server #45 Scanner refactoring. Multipe issues that need fixing. -- daveschaefer
    1. This would be much easier and faster if we refactored the scanner component so it was easier to test
  5. Server #30 Extract certificate data to separate database table. This is required to keep our database sizes sane, especially if we will be storing more than one type of certificate fingerprint -- daveschaefer
  6. Server #22 Fix server to display use SHA256 hashes -- daveschaefer
    1. Add a database field to store SHA256 hashes
    2. Have the scanner begin calculating and both storing both hashes
    3. Set a new way to request the SHA256 hash type when asking a server for info
  7. Upgrade existing servers to use the new hash code. Let them begin gathering data. -- daveschaefer
    1. Upgrading the heroku notaries will be easier. Upgrading the aws notaries will be more difficult, and they will have to go through two schema upgrades (2.x -> 3.0, and 3.0 -> newest).
  8. Client #149 Client support for SHA256 hashes. -- lambdor

Medium-term

Medium-term items are not listed in any particular priority.

Long term priorities

Long-term items are not listed in any particular priority.

  • Port Perspectives to Chromium/Chrome
    1. Extract browser-specific code to its own set of javascript objects (so code is organized and maintainable). This will probably be a by-product of the tabinfo_restrcturing merge.
    2. Requires functionality from Chrome first: the ability for extensions to retrieve the certificate for the current site
    3. Set up script that converts Firefox-style localized strings to Chrome-style localized strings (should create and release a separate library for this and then use it)
  • Client #126 Real-time view for notary results
  • Client #76 Restartless extension