GPG Key Handling

Bug #1670151 reported by Kenneth Loafman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
New
Medium
Unassigned

Bug Description

In order to provide the best security, duplicity should use the key fingerprint when talking with the gpg process. It should allow the user to specify the short key (8-char), long key (16-char) and the fingerprint (40-char) on the command line and convert to fingerprint when needed.

This follows GNU's best practices for handling keys between processes.

Changed in duplicity:
milestone: 0.8.00 → 0.8.01
Changed in duplicity:
milestone: 0.8.01 → none
Changed in duplicity:
status: In Progress → New
assignee: Kenneth Loafman (kenneth-loafman) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.