The LUKS issue was all about getting a root shell as opposed to being
able to defeat LUKS or get the keys or decrypt the data. I know this was
a bit misreported in the press.
A bigger issue is if /boot is not encrypted. And with modern GRUB there
is no need for it not to be. Someone could then
On 28/12/2016 21:33, Marek Marczykowski-Górecki wrote:
> Interesting, do you have that touchpad really as a USB device? If so,
> it's probably not supported by InputMouse service - probably we need
> InputTouchpad, or sth like this.
That's a good question. It's an Acer laptop. The usbVM shows it
On 03/01/2017 04:35, Otto Kratik wrote:
> I am using Qubes R3.2. Suddenly almost all of the KDE shortcuts
> usually found under applications-> system tools have completely
> vanished. I have no konsole, file manager, system settings etc. Only
> four remain:
I can't help but I had this happen once
Right shift key doesn't seem to work in windows HVM but is fine in Linux
Vms. Weird. Ideas?
--
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
After switching to pvgrub2 and distro kernel within VM I'm seeing alerts
from time to time about dmroot crashing (something like 'sorry, dmroot
seems to have crashed').
Also to install kernel-devel I had to use allowerasing to install it as
package 1000:4.4.31-11.pvops.qubes was blocking it.
Oh forgot to add. I did try setting the NetVM for the Windows HVM to
sys-net to no avail. Thought that might give a non-NAT'd direct connection.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
So I have iTunes in a Qube -- the best place for it IMHO ;-).
I'd like to be able to use AirPlay. Since I'm not bridged and the
AirPlay protocol uses mDNS/DNS-SD I need a way for the multicast to work
from a Qube without violating any of the Qubes careful network design.
e.g. One idea is to
Hi all,
My touchpad doesn't work now that I've started using a usbVM. If I
attach a USB mouse I get a prompt asking me if I wish to allow it. For
the touchpad no prompt and it doesn't work even if I set the RPC policy
for InputMouse to allow.
Thoughts?
--
You received this message because you
I've noticed this problem a few times now:
If the screen is locked for too long (this problem doesn't seem to occur
if I unlock the screen a short time after the screen locking) when I
unlock the screen the VMs that were running are now in a yellow state.
There is an error message about error
Will qubes-dom0-update work for Qubes users not using the testing
repositories?
--
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
On 2016-11-19 11:54, Andrew David Wong wrote:
On 2016-11-16 13:31, Fred wrote:
A good time to ask if Qubes encrypts /boot in it's LUKS setup. I've
not
checked myself.
By default, Qubes does not encrypt /boot. Traditionally, that's
because doing so would render the
system unbootable. However
On 16/11/2016 20:10, Loren Rogers wrote:
> Clicking the "Update VM System" button with dom0 selected seems like it
> starts, but it doesn't really go anywhere.
I recall reading something about this issue in the Qubes Wiki. IIRC,
they suggested to run the command manually from the command line;
On 16/11/2016 19:10, berthold_...@web.de wrote:
> Does this affect QubesOS?
>
> https://threatpost.com/cryptsetup-vulnerability-grants-root-shell-access-on-some-linux-systems/121963/
>
Looks like a fairly low priority to me. You can get initramfs shell in a
Busybox and have access to /boot (on
On 16/11/2016 00:31, Marek Marczykowski-Górecki wrote:
>> Is there any way to debug this further? Have any steps been
>> missed?
>
> Check if u2mfn module was built automatically. Simply login on the
> template console and check `modinfo u2mfn`. If it's not there, build
> it using `dkms
Thanks!
I'll stop trying to get DispVMs working for now then.
--
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
On 14/11/2016 21:32, Unman wrote:
> Is there anything in /var/log/libvirt/libxl logs?
The following;
2016-11-14 20:38:15 GMT libxl: error: libxl_pci.c:1041:libxl__device_pci_reset:
The kernel doesn't support reset from sysfs for PCI device :01:00.1
2016-11-14 20:40:12 GMT xc: error:
On 14/11/2016 17:56, Unman wrote:
> I'm not aware of any particular issues, although there have been some
> reports of issues with customisation.
Here is what I get after removing and recreating. No errors and the save
file says it was created OK. I found an xterm command to run in dom0 to
try
On 14/11/2016 13:46, Unman wrote:
> For future reference, I think the sys-net started because there were
> OTHER qubes downstream set to autostart, e.g sys-firewall. If they are
> still starting they will trigger the sys-net. So you need to either set
> the netvm to none for them or stop them
Are there any known issues with the DispVM in Qubes 3.2 that I should be
aware of?
I cannot get it to work. I have also tried recreating it two ways based
on the default template *and* choosing a different non-default one.
i.e
qvm-create-default-dvm fedora-23 and qvm-create-default-dvm
On 12/11/2016 08:27, Alex wrote:
> Try editing /var/lib/qubes/qubes.xml and set "autostart" to False
> instead of True for the sys-net vm
I had actually found this file and tried setting the autostart attribute
but the VM still auto-started.
I also tried editing the sys-net XML file directly
I made a change to the PCI devices for the sys-net VM and now Qubes
hangs on boot when starting this vm.
I've tried using the installation image to get to system rescue via the
troubleshooting link in the installer. I can get into my system this way
but I'm unsure what to change as removing the
I followed the instructions here
https://www.qubes-os.org/doc/managing-vm-kernel/ for using the VM
kernel.
So in short:
in dom0: sudo qubes-dom0-update grub2-xen
in fedora-23 template vm: sudo yum install qubes-kernel-vm-support
grub2-tools
in fedora-23 template vm: installed a distro
22 matches
Mail list logo
