update

diff --git a/doc/todo/support_using_Stateless_OpenPGP_instead_of_gpg.mdwn b/doc/todo/support_using_Stateless_OpenPGP_instead_of_gpg.mdwn
index 48f3413b260cd807950415e62948be2162e3ac80..75bebba24738726817681e402c3fc92f09f0fcd1 100644 (file)
--- a/doc/todo/support_using_Stateless_OpenPGP_instead_of_gpg.mdwn
+++ b/doc/todo/support_using_Stateless_OpenPGP_instead_of_gpg.mdwn
@@ -37,6 +37,7 @@ It seems that git-annex would need to prompt for the secret key's password
 itself, since sop doesn't prompt, and feed it in via `--with-key-password`.
 It can detect if a password is needed by trying the sop operation without a
 password and checking for an exit code of 67.
+See [this issue on sop password prompting](https://gitlab.com/dkg/openpgp-stateless-cli/-/issues/64)
 
 git-annex also uses gpg to generate random data for an encryption cipher
 when setting up an encrypted special remote. Of course there are other ways