Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
monkeysign
monkeysign
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • monkeysphere
  • monkeysignmonkeysign
  • Issues
  • #42

Closed
Open
Opened Sep 14, 2016 by Jerome Charaoui@lavamindOwner

Keep camera frame containing qr-code for safekeeping

It would be awesome if Monkeysign would, by default, keep a copy of qr-codes containing fingerprints of keys being signed.

Here's a little snippet demonstrating how to use OpenCV and zbar to do that: https://0xacab.org/snippets/4

As a bonus, it uses zbar data to visually identify the qr-code containing the fingerprint in the saved image. This probably eliminates an attack scenario where a bad qr-code would be placed behind the user in an attempt to have the wrong key signed.

Obviously, the difficult part is integrating this in a the GTK UI. Probably this will be easier after #21 is fixed.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Monkeysign 3.0.0
Milestone
Monkeysign 3.0.0
Assign milestone
Time tracking
None
Due date
None
Reference: monkeysphere/monkeysign#42