Commit 7bfb25c6 authored by Tails developers's avatar Tails developers
Browse files

Add idea.

parent 825fbec1
......@@ -14,7 +14,12 @@ This can be implemented this way:
store_passphrase_timeout=10
passphrase_grab=1
Alternatively, we could try to backport Wheezy's Claws Mail and see if
Another way to fix the problem is to replace Seahorse's GnuPG agent
with the regular `gpg-agent`.
See the dedicated [[ticket|todo/regular_GnuPG_agent]].
A last method could be to backport Wheezy's Claws Mail and see if
it fixes the problem.
[[!tag todo/code]]
**Next thing to do**: [[!taglink todo/wait]] for a decision regarding
Seahorse vs. regular GnuPG agent.
Both [[todo/support_OpenPGP_smartcards]] and
[[todo/fix_claws-mail_with_gpg]] have / are problems caused by
Seahorse, that are fixed by replacing its agent with the regular
GnuPG one and [[!debpts pinentry-gtk2]].
Implemented in `feature/regular-gnupg-agent`.
What would we lose, exactly, by doing that?
[[!tag todo/discuss]]
......@@ -6,13 +6,11 @@ Plans
Next things to do
-----------------
1. [[!taglink todo/research]] how to support hardware despite the
Seahorse bug ([[!gnomebug 530439]]):
- is it an option to only document the
1. how to support hardware despite the Seahorse bug ([[!gnomebug 530439]]):
- Let's [[!taglink todo/wait]] for a decision regarding
[[Seahorse vs. regular GnuPG agent|todo/regular_GnuPG_agent]].
- else, is it an option to only document the
`GPG_AGENT_INFO=` workaround?
- is it an option to replace Seahorse, for the GnuPG agent role,
with good ol' `gpg-agent` and either [[!debpts pinentry-gtk2]]
or [[!debpts pinentry-qt4]]? What would we lose, exactly?
Done
----
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment