ProofMode: Verified Visuals (A CameraV-inspired Micro App)
Java Shell
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.idea separate core proofmode service into library Mar 14, 2018
.tx add transifex configuration Nov 8, 2017
android-libproofmode improve ProofMode API and clean up code Aug 14, 2018
app improve ProofMode API and clean up code Aug 14, 2018
art small change to PgpUtils class to support password (eventually) May 25, 2017
docs new supporting files Feb 24, 2017
gradle/wrapper
java-opentimestamps
samples/sample-proof-1 Update 1487917842390batchproof.csv Feb 24, 2017
.gitignore update gitignore Jun 1, 2018
.travis.yml
LICENSE
README.md update description Feb 24, 2017
_config.yml Set theme jekyll-theme-tactile Feb 22, 2017
build.gradle update gradle and dependency strategy Jun 1, 2018
gp-code-of-conduct.md
gradle.properties improvements to libProofMode use and setup Jun 1, 2018
gradlew first major check-in Oct 6, 2016
gradlew.bat first major check-in Oct 6, 2016
make-release-build update mrb to gradle Aug 9, 2017
settings.gradle

README.md

Overview

ProofMode is light, minimal "reboot" of our full encrypted, verified secure camera app, CameraV (https://guardianproject.info/apps/camerav). Our hope was to create a lightweight, almost invisible utility, that you can run all of the time on your phone, that automatically extra digital proof data to all photos and videos you take. This data can then be easily shared through a "Share Proof" share action, to anyone you choose.

While we are very proud of the work we did with the CameraV and InformaCam projects, the end results was a complex application and proprietary data format that required a great deal of investment by any user or community that wished to adopt it. Furthermore, it was an app that you had to decide and remember to use, in a moment of crisis. With ProofMode, we both wanted to simplify the adoption of the tool, and make it nearly invisible to the end-user, while making it the adoption of the tool by organizations painless through simple formats like CSV and known formats like PGP signatures.

Design Goals

  • Run all of the time in the background without noticeable battery, storage or network impact
  • Provide a no-setup-required, automatic new user experience that works without requiring training
  • Use strong cryptography for strong identity and verification features, but not encryption
  • Produce "proof" sensor data formats that can be easily parse, imported by existing tools (CSV)
  • Do not modify the original media files; all proof metadata storied in separate file
  • Support chain of custody needs through automatic creation of sha256 hashes and PGP signatures
  • Do not require a persistent identity or account generation

What It Does

  1. User installs ProofMode app
  2. ProofMode app automatically generates a private/public OpenPGP keypair as a persistent "proof" identity within the app
  3. When the user takes a photo or video, ProofMode wakes up, signs the new media file with their private key
    • Additionally, a sensor data snapshot is taken to gather correlating proof. This is saved as a CSV file, and also signed with the OpenPGP key.
  4. If the user wants to share a specific photo or video as "proof", they can just select the "Share Proof" option from the Android global share menu from the Gallery or Photos app.
    • This will then re-share the media file, plus all the related proof files and digital signatures, to the app of the users choice, along with a summary of when the file was created, what the public key identity is, and so on.
    • The user can also select multiple photos and videos to "Share Proof" for, and create a batch of data, with correlating sensor data for all media files, combined together in a single log of an "event"
  5. The user can also choose to publish their public key on pgp.mit.edu directory from within the app menu, or directly share their public key with anyone who would need it for verifying digital signatures.
  6. As the receiver of a ProofMode data set, you can verify the media file was not tampered with, verify the public key idenity of who signed the files, to see if it is consistent with what you expect, and examine all the correlating sensor data around the event, for extra context and evidence.
    • The CSV data can easily be imported into any spreadsheet or visualization type tool to create maps, charts, graphs, and other means of understanding the values included, over time, especially across multiple proof points of media

Screenshots

Screenshot Screenshot Screenshot

Contributions