Thank you for pointing in the right direction. It was my fault in the script
for dom0. It failed in some way, causing other scripts not being called. I am
sorry for that. Now, I have a quick fix, but I should make it more robust.
On the keyboard: I had an idea about authenticated USB keyboard pr
Le lundi 12 septembre 2016 07:28:08 UTC+2, Fanilo a écrit :
> Hi,
>
> The Windows HVM is started bus is not responding after QWT
>
> The windows desk is not displayed.
>
> The icons in the menu launch the windows apps but fail.
>
> The logs are attached.
>
> As recommanded :
> The HVM does not
On Saturday, September 10, 2016 at 1:44:02 AM UTC-4, joseph.y...@gmail.com
wrote:
> I installed Qubes 3.2-rc3 on my Lenovo P50 (Xeon ECC laptop)
>
> It works, but I had to disable RAID in the bios and use lvm striping.
>
> The raid disks don't seem to show up at all. The bios doesn't have a sto
> A malicious guest administrator can crash the host, leading to a DoS.
> Arbitrary code execution (and therefore privilege escalation)
Think this is an example of why it's a good idea to password protect guests?
--
You received this message because you are subscribed to the Google Groups
"qub
On Saturday, 10 September 2016 19:18:10 UTC+1, neilh...@gmail.com wrote:
> I've seen some dispute that a Linux browser exploit even exists.
>
> Like, could you take Chrome or Firefox to a page, and then have a remote
> shell, that loads a file onto the hard drive to monitor everything?
>
> I ca
On Friday, 9 September 2016 18:58:51 UTC+10, Thomas Ernst wrote:
> Hi all,
>
> Does Qubes support NVIDIA GeForce graphics cards? The reason for asking is
> that I am planing to buy a Lenovo ThinkPad T460p Laptop, which has a NVIDIA
> GeForce 940MX 2 GB graphics card.
>
> Best,
>
> Thomas
I h
On Monday, 12 September 2016 00:29:14 UTC+1, neilh...@gmail.com wrote:
> Qubes uses VT-D to protect against DMA attacks on things such as WiFi chip.
>
> But are there any proven DMA attacks against wired networking, i.e.
> Ethernet..?
>
> Hackers can exploit a buffer overflow on the network car
ps.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/CAHEcKzWyyjqa63b2mBU0tfK8G14kBWYft-sGefLisMa2br_S7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Qubes-HCL-Supermicro-C7H170_M-20160911-212422.yml
Description: applic
ps.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/CAHEcKzXES7aOHQFiy8KQcgbFWyWSv2c3DcZ8XtAPm_jgFgvM7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Qubes-HCL-Supermicro-C7H170_M-20160911-212125.yml
Description: application/yaml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Sep 11, 2016 at 02:41:48PM -0700, dlea...@gmail.com wrote:
> I am running Qubes 3.1 on a Librem 13. I am brand new to Linux.
>
> The trackpad is recognized only as a standard mouse. I am trying to figure
> out how to update the driver so th
Qubes uses VT-D to protect against DMA attacks on things such as WiFi chip.
But are there any proven DMA attacks against wired networking, i.e. Ethernet..?
Hackers can exploit a buffer overflow on the network card's firmware, and use
that to take control of the network card, and issue a DMA atta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Sep 11, 2016 at 02:25:29PM -0700, Vít Šesták wrote:
> On Sunday, September 11, 2016 at 11:13:51 PM UTC+2, Marek
> Marczykowski-Górecki wrote:
> > Interesting. Any errors in journalctl?
>
> Nothing interesting found there.
>
> But... Today,
I am running Qubes 3.1 on a Librem 13. I am brand new to Linux.
The trackpad is recognized only as a standard mouse. I am trying to figure out
how to update the driver so that it works like a standard trackpad.
Dom0 via Yum Extender shows driver package as:
xorg-x11-drv-synaptics ver. 1.8.1-6.
On Sunday, September 11, 2016 at 11:13:51 PM UTC+2, Marek Marczykowski-Górecki
wrote:
> Interesting. Any errors in journalctl?
Nothing interesting found there.
But... Today, I started having a similar issue with NetVM. It does not start
NetrowkManager after resume. It looks like the script is j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Sep 11, 2016 at 02:00:15PM -0700, Vít Šesták wrote:
> On Sunday, September 11, 2016 at 10:15:52 PM UTC+2, Marek
> Marczykowski-Górecki wrote:
> > > However, after renaming the /rw/config/suspend-module-blacklist,
> > > rebooting USBVM and s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2016-09-11 23:01, Bob Newell wrote:
> On Sunday, September 11, 2016 at 4:56:32 PM UTC-4, omeg wrote: On
> 2016-09-11 22:36, Bob Newell wrote:
I was able to get my Windows 7 VM running with these
directions (https://www.qubes-os.org/doc/w
On Sunday, September 11, 2016 at 4:56:32 PM UTC-4, omeg wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 2016-09-11 22:36, Bob Newell wrote:
> > I was able to get my Windows 7 VM running with these directions
> > (https://www.qubes-os.org/doc/windows-appvms/), but after adding
> >
On Sunday, September 11, 2016 at 10:15:52 PM UTC+2, Marek Marczykowski-Górecki
wrote:
> > However, after renaming the /rw/config/suspend-module-blacklist, rebooting
> > USBVM and suspend-resume cycle, the USBVM does not see any USB device.
> > (Currently, both controllers are assigned to USBVM a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2016-09-11 22:36, Bob Newell wrote:
> I was able to get my Windows 7 VM running with these directions
> (https://www.qubes-os.org/doc/windows-appvms/), but after adding
> the tools using this command (sudo qubes-dom0-update
> --enablerepo=qubes-do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Sep 11, 2016 at 01:12:12PM -0700, Vít Šesták wrote:
> On Sunday, September 11, 2016 at 9:54:42 PM UTC+2, Marek Marczykowski-Górecki
> wrote:
> > AFAIR only *_pci modules are talking to the hardware, so removing them
> > should be enough. Can
On Sunday, September 11, 2016 at 9:54:42 PM UTC+2, Marek Marczykowski-Górecki
wrote:
> AFAIR only *_pci modules are talking to the hardware, so removing them
> should be enough. Can you check if your approach still works with only
> *_pci?
Got it, partially. The /usr/lib/qubes/prepare-suspend scr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Sep 11, 2016 at 12:41:31PM -0700, Vít Šesták wrote:
> On Sunday, September 11, 2016 at 8:52:36 PM UTC+2, Marek Marczykowski-Górecki
> wrote:
> > In fact those modules (besides USBIP) should be blacklisted by default.
> > Take a look at /etc/
On Sunday, September 11, 2016 at 8:52:36 PM UTC+2, Marek Marczykowski-Górecki
wrote:
> In fact those modules (besides USBIP) should be blacklisted by default.
> Take a look at /etc/qubes-suspend-module-blacklist. Maybe it doesn't
> work for some reason? Or the file wasn't updated (and the new on i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Sep 11, 2016 at 11:17:54AM -0700, Vít Šesták wrote:
> Qubes 3.2, essentially the same situation. Plus I am concerned also about
> dom0 USB, because I have external keyboard and touchpad.
>
> Since there are similar issues in dom0, which is
On Sunday, September 11, 2016 at 8:17:54 PM UTC+2, Vít Šesták wrote:
> In dom0, I've created /usr/lib64/pm-utils/sleep.d/53usb file and registered
> it in /usr/lib/systemd/system/qubes-suspend.service
Oops, forgot to include link to the files:
https://gist.github.com/v6ak/1a1f90f9f07f03d8c9c812d
Qubes 3.2, essentially the same situation. Plus I am concerned also about dom0
USB, because I have external keyboard and touchpad.
Since there are similar issues in dom0, which is more close to bare metal than
domUs, I suspect that those are issues would not be mitigated by calling
standard sus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-09-11 08:15, Bob Newell wrote:
>
>>
>> You should be able to right-click on the VM in Qubes Manager and
>> click "Remove VM."
>>
>
> That makes sense. Is there an equivalent terminal command?
>
Yes, it's:
qvm-remove [options]
For ava
>
> You should be able to right-click on the VM in Qubes Manager and
> click "Remove VM."
>
That makes sense. Is there an equivalent terminal command?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop rec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-09-11 06:19, Bob Newell wrote:
> I was following the directions on this page:
> https://www.qubes-os.org/doc/hvm/
>
> I was installing windows. Unfortunately, somehow the computer entered
> sleep mode and when it resumed it would not install
On Monday, September 5, 2016 at 4:24:09 PM UTC-7, Marek Marczykowski-Górecki
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Thu, Jun 23, 2016 at 09:31:46PM +0200, Niels Kobschaetzki wrote:
> > On 16/06/23 00:28, Marek Marczykowski-Górecki wrote:
> > > On Wed, Jun 22, 2016 at 11
I was following the directions on this page: https://www.qubes-os.org/doc/hvm/
I was installing windows. Unfortunately, somehow the computer entered sleep
mode and when it resumed it would not install. I couldn't find the command to
delete the VM. I would recommend adding the command to the wind
5e4-a6524cc28cd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Qubes-HCL-ASUSTeK_COMPUTER_INC_-UX303LAB-20160911-144952.yml
Description: Binary data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Sep 11, 2016 at 01:31:12PM +0200, Rafał Wojdyła wrote:
> On 2016-09-11 03:00, Andrew David Wong wrote:
> > On 2016-09-10 16:12, 3n7r0...@gmail.com wrote:
> >> On Wednesday, August 17, 2016 at 12:43:27 AM UTC, Andrew David
> >> Wong wrote:
> >
Hum thank you. I didn't do that but somehow it works now.
--
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 post to thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2016-09-11 03:00, Andrew David Wong wrote:
> On 2016-09-10 16:12, 3n7r0...@gmail.com wrote:
>> On Wednesday, August 17, 2016 at 12:43:27 AM UTC, Andrew David
>> Wong wrote:
>>>
>>> So, as Marek said, in this particular case, the updated package
>
Video drivers AFAIK differ in those three versions:
3.0 seems to have Fedora 20 drivers
3.1 has some updated drivers, despite being based on Fedora 20
3.2 is based on Fedora 23
However, I can see little-to-no benefits of Wayland for Qubes:
In dom0, it might be some differences in GPU support. Thi
36 matches
Mail list logo
