Task #2129
syncing GPG info to GnuPrivacyGuard for Android
| Status: | New | Start date: | 10/18/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | 0.3 | |||
| Component: |
Description
now that we have rudimentary GnuPG support in KeySync, we could also easily make it copy pubring.gpg to the SD card, which would make it easy to import into Gnu Privacy Guard
Related issues
History
#1 Updated by hans over 4 years ago
- Subject changed from should GnuPG to ChatSecure sync copy pubring.gpg to the device's SD card? to syncing GPG info to GnuPrivacyGuard for Android
- Target version changed from 0.2 to 0.3
Upon thinking about this, we can do a parallel process to the otr_keystore.ofcaes process. Make a file like keyrings.gpgaes that keysync makes by bundling up ~/.gnupg/secring.gpg and ~/.gnupg/pubring.gpg into a single file, then encrypting using AES, and doing the QRCode password. The question is should this all happen at once, and should ChatSecure handle shuffling the files off to GnuPrivacyGuard. Or should there be a separate process where the user scans a separate QRcode using GnuPrivacyGuard.