[qubes-users] Re: Has anyone tried to activate SELINUX in Fedora 25?

2017-09-24 Thread cooloutac
On Sunday, September 24, 2017 at 12:17:33 PM UTC-4, cooloutac wrote: > On Sunday, September 24, 2017 at 12:16:34 PM UTC-4, cooloutac wrote: > > On Thursday, September 21, 2017 at 4:40:42 AM UTC-4, pels wrote: > > > On Wednesday, September 20, 2017 at 2:54:31 PM UTC+2, cooloutac wrote: > > > > On

[qubes-users] Re: Has anyone tried to activate SELINUX in Fedora 25?

2017-09-24 Thread cooloutac
On Sunday, September 24, 2017 at 12:16:34 PM UTC-4, cooloutac wrote: > On Thursday, September 21, 2017 at 4:40:42 AM UTC-4, pels wrote: > > On Wednesday, September 20, 2017 at 2:54:31 PM UTC+2, cooloutac wrote: > > > On Wednesday, September 20, 2017 at 4:41:58 AM UTC-4, pels wrote: > > > > I'd

Re: [qubes-users] Re: Unable to uninstall or reinstall Whonix

2017-09-24 Thread cooloutac
On Saturday, September 23, 2017 at 10:31:08 PM UTC-4, Person wrote: > You were correct (thank you so much!). Apparently I set the Update VM to > "none" in the Global Settings, so it didn't work. Now installing Whonix works > fine. > > However, uninstalling the old templates still does not work.

[qubes-users] Re: How to recover Qubes when keyboard / mice is dysfunctional due to USB qube setup issues?

2017-09-24 Thread cooloutac
On Sunday, September 24, 2017 at 9:25:24 AM UTC-4, Patrick Schleizer wrote: > Quote from https://www.qubes-os.org/doc/usb/ > > > Caution: By assigning a USB controller to a USB qube, it will no > longer be available to dom0. This can make your system unusable if, for > example, you have only one

[qubes-users] Re: How to recover Qubes when keyboard / mice is dysfunctional due to USB qube setup issues?

2017-09-24 Thread cooloutac
On Sunday, September 24, 2017 at 12:23:23 PM UTC-4, cooloutac wrote: > On Sunday, September 24, 2017 at 9:25:24 AM UTC-4, Patrick Schleizer wrote: > > Quote from https://www.qubes-os.org/doc/usb/ > > > > > Caution: By assigning a USB controller to a USB qube, it will no > > longer be available to

Re: [qubes-users] Re: Unable to uninstall or reinstall Whonix

2017-09-24 Thread Person
It seems that the VMs have already been replaced. Which is good considering that then I don't need to delete the old templates. However, the system didn't automatically give me an anon-Whonix or sys-Whonix templates, so I tried making some for myself. (I'm not sure if there is a easier or

Re: [qubes-users] Anyone disabled the Intel ME yet?

2017-09-24 Thread cooloutac
On Thursday, September 21, 2017 at 12:08:41 PM UTC-4, Hugo Costa wrote: > On Thursday, 21 September 2017 07:23:01 UTC+1, Alex wrote: > > Replying to this thread to report that somebody DID ACTUALLY find an > > exploitable vulnerability in the latest IME 11+, and they will be > > sharing nothing

[qubes-users] Re: Anyone disabled the Intel ME yet?

2017-09-24 Thread filtration
cooloutac: > On Sunday, September 24, 2017 at 8:24:44 PM UTC-4, cooloutac wrote: >> On Thursday, September 21, 2017 at 12:08:41 PM UTC-4, Hugo Costa wrote: >>> On Thursday, 21 September 2017 07:23:01 UTC+1, Alex wrote: Replying to this thread to report that somebody DID ACTUALLY find an

Re: [qubes-users] Re: Unable to uninstall or reinstall Whonix

2017-09-24 Thread cooloutac
On Sunday, September 24, 2017 at 3:59:28 PM UTC-4, Person wrote: > It seems that the VMs have already been replaced. Which is good considering > that then I don't need to delete the old templates. > > However, the system didn't automatically give me an anon-Whonix or sys-Whonix > templates, so

Re: [qubes-users] Anyone disabled the Intel ME yet?

2017-09-24 Thread cooloutac
On Sunday, September 24, 2017 at 8:24:44 PM UTC-4, cooloutac wrote: > On Thursday, September 21, 2017 at 12:08:41 PM UTC-4, Hugo Costa wrote: > > On Thursday, 21 September 2017 07:23:01 UTC+1, Alex wrote: > > > Replying to this thread to report that somebody DID ACTUALLY find an > > > exploitable

[qubes-users] Screen freezing and input problems in AppVMs

2017-09-24 Thread Michael Strasser
Hi! I've been experiencing some strange issues recently, which I can't really pin down on anything in particular. * I've been getting a frozen screen after random periods of time when I've been using two different monitors. Usually the only solution is to kill my machine. * Sometimes (again

[qubes-users] Re: Some HVM systems don't pickup IP from DHCP

2017-09-24 Thread yuraeitha
On Thursday, November 5, 2015 at 4:00:22 AM UTC, Pete Howell wrote: > I've noticed on several installs, that the system would not pickup an IP > address and had to have one hardcoded.  Does anyone know why this happens? I had a similar issue when I installed Android 7.1 on Qubes OS, it did not

[qubes-users] How to recover Qubes when keyboard / mice is dysfunctional due to USB qube setup issues?

2017-09-24 Thread Patrick Schleizer
Quote from https://www.qubes-os.org/doc/usb/ > Caution: By assigning a USB controller to a USB qube, it will no longer be available to dom0. This can make your system unusable if, for example, you have only one USB controller, and you are running Qubes off of a USB drive. How can one recover

Re: [qubes-users] Re: Painless USB attach/detach

2017-09-24 Thread Yethal
W dniu niedziela, 24 września 2017 15:03:45 UTC+2 użytkownik Sean Hunter napisał: > Yeah. Grep | cut -f1 from that script is similar to the awk line I use except > that I also only print the first match (if there are multiple matches) > whereas that script will print all of them which I think

[qubes-users] Salt vcpus bug in 4.0rc1

2017-09-24 Thread Sean Hunter
Hi there, I think changes to remove vcpu option etc from qvm-create in 4.0 haven't been synced into the saltstack modules yet. If I create an x.top file like this base: dom0: - x ...and an x.sls file like this x: qvm.present: - name: x - template: fedora-25 - label: blue -

Re: [qubes-users] Pointer lock API

2017-09-24 Thread Alex
On 09/24/2017 04:50 AM, Nagaev Boris wrote: > Hey! > > I noticed that Quake3 almost works in Qubes 3.2, but has one > annoying issue: the pointer is unmanageable. It looks like the > pointer has the "memory" about its previous position: e.g. when I > move it left, the game continues moving right.

[qubes-users] Re: how to make a docker host templatevm

2017-09-24 Thread yuraeitha
On Sunday, September 24, 2017 at 10:12:03 AM UTC, pixel fairy wrote: > On Sunday, September 24, 2017 at 3:02:50 AM UTC-7, yura...@gmail.com wrote: > > > This looks exciting, I definitely will have a look at it when Qubes 4.0-RC2 > > has been released, with more up-to-date templates. > > i wrote

Re: [qubes-users] Pointer lock API

2017-09-24 Thread yuraeitha
On Sunday, September 24, 2017 at 11:15:28 AM UTC, Leo Gaspard wrote: > On 09/24/2017 04:50 AM, Nagaev Boris wrote: > > Hey! > > > > I noticed that Quake3 almost works in Qubes 3.2, but has one annoying > > issue: the pointer is unmanageable. It looks like the pointer has the > > "memory" about

[qubes-users] Is it damaging to increase each 2GB VM storage beyond the drive limit?

2017-09-24 Thread yuraeitha
Heya, TL:DR Is there anything wrong with pushing VM partitions beyond the physical drive size, as long as data doesn't exceed the physical drive size (which it can't for obvious reasons). Corruption? Backup size? Privacy? or just no code available yet to tailor VM sizes to unique drive

[qubes-users] Re: Screen freezing and input problems in AppVMs

2017-09-24 Thread yuraeitha
On Sunday, September 24, 2017 at 8:52:32 AM UTC, Michael Strasser wrote: > Hi! > > I've been experiencing some strange issues recently, which I can't > really pin down on anything in particular. > > * I've been getting a frozen screen after random periods of time when > I've been using two

[qubes-users] Re: Salt vcpus bug in 4.0rc1

2017-09-24 Thread yuraeitha
On Sunday, September 24, 2017 at 10:53:12 AM UTC, Sean Hunter wrote: > Hi there, > > I think changes to remove vcpu option etc from qvm-create in 4.0 haven't been > synced into the saltstack modules yet. > > If I create an x.top file like this > base: > dom0: > - x > > ...and an x.sls

[qubes-users] Re: how to make a docker host templatevm

2017-09-24 Thread yuraeitha
On Friday, September 22, 2017 at 9:47:59 AM UTC, pixel fairy wrote: > heres how to make a docker host templatevm. have fun. > > https://gist.github.com/xahare/6b47526354a92f290aecd17e12108353 > > Should this be added to the qubes docs? This looks exciting, I definitely will have a look at it

[qubes-users] Painless USB attach/detach

2017-09-24 Thread Sean Hunter
Hey there, I was trying out attaching usb devices to qubes and thought this might be useful to other people. If you have a device with a complicated description (eg a Yubikey) it can be a pain to figure out what device ID it's being attached to in sys-usb so you can use qvm-usb attach to send

Re: [qubes-users] Re: Painless USB attach/detach

2017-09-24 Thread Sean Hunter
Yeah. Grep | cut -f1 from that script is similar to the awk line I use except that I also only print the first match (if there are multiple matches) whereas that script will print all of them which I think will cause problems if you have a device attached multiple timex. Sent from my phone.

Re: [qubes-users] Re: Painless USB attach/detach

2017-09-24 Thread Sean Hunter
> On 24 Sep 2017, at 14:26, Yethal wrote: > > W dniu niedziela, 24 września 2017 15:03:45 UTC+2 użytkownik Sean Hunter > napisał: >> Yeah. Grep | cut -f1 from that script is similar to the awk line I use >> except that I also only print the first match (if there

[qubes-users] Re: Privacy in Qubes

2017-09-24 Thread cooloutac
On Friday, September 22, 2017 at 9:39:31 PM UTC-4, Person wrote: > These are all very good tips, but to be honest, I'm not actually doing > anything too serious on Qubes so tracking is not that bad (but privacy is > still valuable). > > How would changing the web user agent fare? I tried it,

[qubes-users] Updating WiFi Drivers

2017-09-24 Thread flaviosanchez
Hello. How do I make changes to this path "/usr/lib/modules/(uname -r)/kernel/drivers/net/wireless"? I would like to place lwfinger's compiled driver (https://github.com/lwfinger/rtl8188eu) in that directory to get my NIC card to work properly. -- You received this message because you are