Kevin O'Gorman
Kevin O'Gorman
See also https://github.com/freedomofpress/securedrop-client/issues/1549 and #5104
FWIW I'm more in favour of a call like /sources/since/ rather than one with a hardwired 24h window. This would also be more use for the syncing case, as syncs...
Yup @eloquence, I think first order of business is figuring out if we can safely add a field like "last_interacted".
Future versions of SecureDrop may use JS more extensively (for example for client-side encryption), so this issue is still relevant.
Ongoing work to improve the firewall config/management story is happening in #6384
Keeping this issue - it relates to ongoing packaging improvements being led by @legoktm, it would be great to at least get RC packages built automatically.
I'm super in favour of this! One caveat is that the JI will still not be accessible until our script runs, as some Tor config changes need to be applied....
@eaon see https://github.com/freedomofpress/securedrop/issues/3502 for historical discussion. Also in favour, especially if we can eventually deploy the same package on a hypothetical Qubes admin AppVM.
We have kept the desktop icons working (with kindof a degraded user experience - they don't work or display correctly until the network is up) via a succession of dirty...
This is still valid, and may see some attention as part of packaging changes (moving from deployment from github to deployment as a Debian package).