On Thu, Jun 22, 2017 at 11:40:44AM -0400, Ryan Tate wrote: > I am perplexed by the challenge of containing Twitter use in Qubes. > <snip> > > If I had to pick from the default VMs, I would probably put Twitter in > “untrusted” due to the risks on the read side, even though the account itself > is sensitive and ideally you would not put such write capabilities in a "wild > west” environment like “untrusted." Perhaps better is to just make a > “twitter” vm to keep the damage of any compromise contained to the Twitter > account itself. Most ideal, in the future, would be to combine this last > approach with a Qubes browser add-on and force each non-twitter link to open > in another VM, either disposable or the “untrusted”. > > (Has anyone figured out a better approach?)
Hi Ryan, I use Twitter in a Whonix Workstation template-based Disposable VM. Open links in a different disposable VM. hth jmp -- J.M. Porup www.JMPorup.com -- 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/20170622154957.GB909%40fedora-23-dvm. For more options, visit https://groups.google.com/d/optout.
