deeplow
deeplow
@legoktm squash completed and commit messages revised / with context added.
A test was failing. I force-pushed to fix it.
Upstream feedback [has been requested](https://gitlab.torproject.org/tpo/core/arti/-/issues/2213#note_3281972). I've been juggling other things and haven't managed to reply yet. If someone has interest and cycles. Otherwise I'll try to get to it next...
(adding to the board just so we remember to check in on this. It's not to actually tackle this one)
I have followed [up on the thread](https://gitlab.torproject.org/tpo/core/arti/-/issues/2213#note_3282273) now, but feel free to send in anything that I may have missed.
I have opened https://github.com/freedomofpress/securedrop-workstation/issues/1312 as a potential follow-up.
I should also add that I do see a few scenarios where `sd-log` would be useful: - for log parsing / analysis (in dom0 we don't want to do any...
Good point. I added that to the list of "current properties of sd-log": > realtime - Logs are saved rigth away with no ability for sudden VM shutdowns to corrupt...
> My question is to understand the attack surface now in dom0 versus the attack surface later. So now we pass through the qrexec or whatever communication daemon, and then...
Fair point. I think a simple user log-viewer interface with a simple button to share logs (https://github.com/freedomofpress/securedrop-workstation/issues/529) could be a pragmatic way to avoid telling people to do things in...