You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after investigation, the problem here for me was actually server-side (discovered since the API responses had no key or fingerprint) - it was freedomofpress/securedrop#4909. Once I deleted the lock file mentioned in the issue key generation started to work again on the server-side and replies could be sent on master.
Description
Replies are failing to send on master, this is Qubes only
Steps to reproduce
Expected behavior
Reply sends 🌈
Actual behavior
Reply does not send due to the source fingerprint not getting imported into sd-gpg
Comments
I think this was probably introduced in a recent merge because when I was working on #578 this was working on master
The text was updated successfully, but these errors were encountered: