I just published R.I.S.K.S. (https://19hundreds.github.io/risks-workflow <https://19hundreds.github.io/risks-workflow>). The source repo is https://github.com/19hundreds/risks-workflow <https://github.com/19hundreds/risks-workflow> .
I've been searching for a viable system for managing my own secrets since a while and I'm still on it. Inspired by Snowden's experience with journalists, projects like Enough (https://enough.community/ <https://enough.community/>) and determined to contribute the way I can against digital abuses (monitoring, tapping etc.) I decided to sum up what I know in a step-by-step guide providing a reasonable setup (hopefully) for defending user's secrets. I don't know if many feel the need for such a guide but I crafted it in the hope to be helpful to the vast majority of the audience. I'd greatly appreciate any feedback, comment, critic and advice driven to improve R.I.S.K.S. --- 1900 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/LX4F0AN--3-1%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
