Re: [qubes-users] HDMI-related threats in Qubes OS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-04-01 13:58, Vít Šesták wrote: > Hello, > I've realized that HDMI offers not only graphical/sound output, but also many > inputs. Well, some inputs are expected (listing of available output modes > etc. works AFAIK even with VGA), but

Re: [qubes-users] for people using MAC randomization (debian 9 tmpl): you might want to avoid hostname leaks via DHCP too

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-04-09 15:25, Joonas Lehtonen wrote: > Hi, > > if you setup MAC randomization via network manager in a debian 9 > template as described here: > https://www.qubes-os.org/doc/anonymizing-your-mac-address/ > you still leak your hostname. > >

[qubes-users] Re: coldkernel status update

On 04/09/2017 09:49 AM, Patrick Schleizer wrote: > Reg Tiangha: >> Thanks for all the hard work! WillyPillow just pointed out to me today >> on the qubes-devel mail list that installing busybox and updating >> initramfs in Whonix is all you need to do to get it to boot with >> coldkernel, >

Re: [qubes-users] realized why I always lose sound in the vms

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-04-05 22:55, Jean-Philippe Ouellet wrote: > On Wed, Apr 5, 2017 at 11:29 PM, cooloutac wrote: >> The sound mixer app I installed xfe in mutes things when I lower the volume >> all the way by accident. Never realized

[qubes-users] Re: USB installer did not use existing EFI system partition on NVME drives

On Saturday, April 8, 2017 at 11:22:09 PM UTC-7, jay...@gmail.com wrote: > I am unsure if this is primarily an issue with Qubes or the Anaconda > installer. > > Issue observed while installing in UEFI mode. BIOS was set to use AHCI > (otherwise, the "nvme disk" is not reported to the installer

Re: [qubes-users] Simple Dom0 password manager for an imperfect-but-strong security upgrade?

On Sunday, April 9, 2017 at 2:55:01 PM UTC-4, cooloutac wrote: > I gotta say the dvm template always gets messed up too. So i also only > consider it untrusted tasks now. but the vault vm is great imo. > > Maybe you should post in user devel the people there are not as noob as me. You type to

[qubes-users] for people using MAC randomization (debian 9 tmpl): you might want to avoid hostname leaks via DHCP too

Hi, if you setup MAC randomization via network manager in a debian 9 template as described here: https://www.qubes-os.org/doc/anonymizing-your-mac-address/ you still leak your hostname. Once your MAC address is randomized you might also want to prevent the disclosure of your netvm's hostname to

[qubes-users] i3 current state 2017 on Qubes 3.2

Hello, I tried to install i3 windows manager from current Qubes repository (non testing) and i3-settings-qubes package (before i3 started first time). And I have problems : - i3 wizard manager start, although i3-settins-qubes packed already on the system (is it correct behavior?) - Qubes

[qubes-users] Re: Why is there no built-in nvidia driver support? aka GTX 980 issues

On Saturday, April 8, 2017 at 12:31:18 PM UTC-4, cooloutac wrote: > On Friday, April 7, 2017 at 2:51:11 AM UTC-4, sl98077 wrote: > > On Thursday, March 9, 2017 at 11:56:52 PM UTC-5, cooloutac wrote: > > > Just to add you won't get any benefit from the Nvidia card. Qubes only > > > uses it for

Re: [qubes-users] Simple Dom0 password manager for an imperfect-but-strong security upgrade?

I gotta say the dvm template always gets messed up too. So i also only consider it untrusted tasks now. but the vault vm is great imo. Maybe you should post in user devel the people there are not as noob as me. -- You received this message because you are subscribed to the Google Groups

Re: [qubes-users] HDMI-related threats in Qubes OS

On Sun, Apr 9, 2017 at 9:42 AM, Vít Šesták wrote: > > * DDC (PIN 15+16) – needed for getting the resolution etc., present even in > current version of VGA. While there is some attack surface, it seems to be > rather small. Note

Re: [qubes-users] Re: Why is there no built-in nvidia driver support? aka GTX 980 issues

On Sat, 8 Apr 2017 09:31:18 -0700 (PDT) cooloutac wrote: > On Friday, April 7, 2017 at 2:51:11 AM UTC-4, sl98077 wrote: > > On Thursday, March 9, 2017 at 11:56:52 PM UTC-5, cooloutac wrote: > > > Just to add you won't get any benefit from the Nvidia card. > > > Qubes only

[qubes-users] Re: off topic - invite codes to 'riseup'

I too need two invite codes. Thanks in advance. :) On Tuesday, October 28, 2014 at 11:56:49 PM UTC+5:30, bm-2cu9wcijafoqtf6...@bitmessage.ch wrote: > Dear qubes-users, > > I am long time qubes follower and user. I apologize in advance if anyone > feels this request is spam. > > I am looking

Re: [qubes-users] Re: coldkernel status update

Reg Tiangha: > Thanks for all the hard work! WillyPillow just pointed out to me today > on the qubes-devel mail list that installing busybox and updating > initramfs in Whonix is all you need to do to get it to boot with > coldkernel, busybox will be installed on Whonix 14 by default.

Re: [qubes-users] HDMI-related threats in Qubes OS

Well, there seems to be a cheaper way to do roughly the same. In a nutshell, you just ensure there is no wire for those two things: * HEAC+ (audio return channel plus ethernet). HEAC+ is optional and thus safe to remove. * CEC (remote control input) – This one is a bit more tricky. While CEC is

Re: [qubes-users] Re: Windows 7 installation stops

Hello, What version of Qubes and which Windows 7 version (home/pro/32bit/64bit) are you using? I've successfully installed Windows 7 on Qubes 3.1 and 3.2 Make sure to add at least 2GB RAM to the windows VM. Following the excellent Qubes Documentation I found out that if you create a Windows HVM

Re: [qubes-users] Simple Dom0 password manager for an imperfect-but-strong security upgrade?

>usability is not a good reason to add or change anything. I suggest you switch to running Lynx on OpenBSD then. I guarantee you're running all kinds of horribly insecure stuff on whatever you're using to read this right now. Usability has always been a top priority in Qubes and that is a

[qubes-users] USB installer did not use existing EFI system partition on NVME drives

I am unsure if this is primarily an issue with Qubes or the Anaconda installer. Issue observed while installing in UEFI mode. BIOS was set to use AHCI (otherwise, the "nvme disk" is not reported to the installer or the live usb I used to look at the disk contents). Manual partitioning does not