[qubes-users] Graphics support?

I'm contemplating a new computer, either laptop or all-in-one desktop, on which I'll run Qubes. Looking at https://www.qubes-os.org/doc/system-requirements/ I find: : Intel IGP (strongly preferred) :: Nvidia GPUs may require significant troubleshooting. :: AMD GPUs have not been formally tested,

Re: [qubes-users] Has anyone had a qube compromised?

On Sun, Sep 06, 2020 at 06:55:01PM +0200, Qubes wrote: > On 9/6/20 5:32 PM, unman wrote: > > On Sun, Sep 06, 2020 at 11:12:31AM -0400, Demi M. Obenour wrote: > > > In all of my time using QubesOS, I have never had reason to believe > > > that a qube was compromised. Has anyone here had a qube

[qubes-users] Re: For a Windows VM?

On Monday, September 7, 2020 at 10:08:23 AM UTC+10, Sandy Harris wrote: > > Windows 10 "minus the spyware" > https://ameliorated.info/ > Not sure what you need to do to get access to this

[qubes-users] For a Windows VM?

Windows 10 "minus the spyware" https://ameliorated.info/ -- 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 qubes-users+unsubscr...@googlegroups.com. To view this

Re: [qubes-users] saltstack: user specific pillars in qubes

On Sun, Aug 30, 2020 at 11:36:12AM +0100, lik...@gmx.de wrote: > Hi! > > What's the correct way to use user specific pillars in qubes salt stack? > > My pillars are located in > /srv/salt/user_pillar/ > > To enable during a run them I'm running: > sudo qubesctl --show-output state.highstate >

[qubes-users] Has anyone had a qube compromised?

In all of my time using QubesOS, I have never had reason to believe that a qube was compromised. Has anyone here had a qube compromised? Sincerely, Demi -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop

[qubes-users] Re: Has anyone had a qube compromised?

Seems like a good question, in that it goes to one of the ways I could shoot myself in the foot, and compromise all my security efforts. I thought the point was, after each use of AppVM, close it and start another AppVM. That would make your question to be more like, if one of my AppVM

[qubes-users] Re: For a Windows VM?

On Monday, September 7, 2020 at 10:08:23 AM UTC+10, Sandy Harris wrote: > > Windows 10 "minus the spyware" > https://ameliorated.info/ Looks at though you need to join their Telegram group to get access to the download. Have I go that right? -- You received this message because you are

Re: [qubes-users] Has anyone had a qube compromised?

On 9/6/20 5:32 PM, unman wrote: On Sun, Sep 06, 2020 at 11:12:31AM -0400, Demi M. Obenour wrote: In all of my time using QubesOS, I have never had reason to believe that a qube was compromised. Has anyone here had a qube compromised? Sincerely, Demi I have had occasion to set a honeypot

Re: [qubes-users] Has anyone had a qube compromised?

On Sun, Sep 06, 2020 at 11:12:31AM -0400, Demi M. Obenour wrote: > In all of my time using QubesOS, I have never had reason to believe > that a qube was compromised. Has anyone here had a qube compromised? > > Sincerely, > > Demi > I have had occasion to set a honeypot and use Qubes as a

Re: [qubes-users] Special template to isolate less trusted software?

I do this, but I use a squid proxy setup from rustybird to cache updates. Starting up and shutting down VMs still takes the same amount of time though. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop

Re: [qubes-users] Special template to isolate less trusted software?

My (perhaps naive) approach is to just use flatpak local install in the AppVM. I don't have to mess with bind-dirs. I have a couple different AppVMs where I have such proprietary software away from anything I want to keep safe/private. I'm curious why people are talking about reinstalling on

Re: [qubes-users] Special template to isolate less trusted software?

(By "local install" I mean per-user install) -- 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 qubes-users+unsubscr...@googlegroups.com. To view this discussion on

Re: [qubes-users] saltstack: user specific pillars in qubes

I personally have pillars in /srv/pillar/tops_d and added the top file /srv/pillar/_tops/base/tops_d.top. The top file includes relative paths from /srv/pillar/ with a dot instead of a slash: base: '*': - tops_d.statefile1 - tops_d.statefile2 - tops_d.statefile3 -