On Monday, 26 March 2018 18:25:19 UTC-4, Chris Laprise wrote:
> On 03/26/2018 05:08 PM, sevas wrote:
> > Ah, I mean to change the values of each color.
> >
> > I want my green to be #00ffae and by blue to #00!
> >
> > Vibrance!
> >
>
> IIRC, you can't edit the Xfce4 Qubes colors, but for K
Something unrelated completely corrupted my system. dom0 got hosed and I was
not able to recover. So I have reinstalled qubes from scratch, but this time I
am using a software raid on 2 nvme pcie drives.
Qubes 4 set up does allow for an encrypted raid the graphical setup. It does
not create
On Wednesday, 15 August 2018 06:52:02 UTC-4, awokd wrote:
>
> > $ qvm-create --verbose Win10 --class StandaloneVM --property
> > virt_mode=hvm --property kernel='' --property memory=4096 --property
> > maxmem=4096 --label=red --root-copy-from Win10.raw
>
> How large is the root created when you
I love the new options. It works great to open 3 luks volumes on boot now. 2
of which have an LVM volume group for qubes, the 3rd just an extra ext4 volume.
Two questions:
1) Can you execute multiple cryptsetup commands at the same time? It has to
wait a few seconds for each one in sequence,
Thanks. I'll try it.
What's the best to add the UUID? I assume edit the grub.cfg directly. But
will kernel updates overwrite? Do I need to edit something else and run dracut
-f?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe
> Please note that the current version will probably not work with a default
> qubes LUKS-on-LVM installation. But if some experienced user is willing to
> help testing i'll try to come up with a version that supports this too.
>
> Besides the yubikey/luks stuff the module handles the rd.qubes.
I use a custom dracut module from the2nd, ykluks, so I don't know about how to
modify it to unlock multiple volumes.
Also, I may want to stick with LUKS instead of ecryptfs because yubikey support.
Can you elaborate on the steps for using Btrfs during install of Qubes, the
documentation is still
On Tuesday, 14 August 2018 07:04:09 UTC-4, Brendan Hoar wrote:
> On Monday, August 13, 2018 at 5:47:06 PM UTC-4, joev...@gmail.com wrote:
> > Are you sure they are using Yubikey's "Static Password" slot? That is the
> > only component that enumerates as a USB keyboard. The normal yubikey setup
I have to work with VMWare images often, so I would like them to be run in
Qubes.
They gave me a Windows 10 and a Kali vmware virtual machines.
Many people, including myself, have tested these as working in VMWare Player.
There isn't a problem with the source.
The vmx files only points to the i
I have to work with VMWare images often, so I would like them to be run in
Qubes.
They gave me a Windows 10 and a Kali vmware virtual machines.
Many people, including myself, have tested these as working in VMWare Player.
There isn't a problem with the source.
The vmx files only points to the
> That's a TemplateBasedHVM and InputKeyboard is running, but (as you say)
> not allowed - I advised creating a HVM (Standalone) and you'll see it works.
> You refer to this case below.
It's not InputKeyboard that is the problem, it is Qubes-Gui. StandaloneVMs Not
based on a Template, won't h
On Monday, 13 August 2018 17:13:06 UTC-4, Chris Laprise wrote:
> On 08/13/2018 04:47 PM,
> > Related question.
> >
> > If I installed Qubes and used LUKS encryption (I have to run cryptsetup
> > openLuks just to see the LVM inside)... then I add physical drives to my
> > Volume Group, and star
Related question.
If I installed Qubes and used LUKS encryption (I have to run cryptsetup
openLuks just to see the LVM inside)... then I add physical drives to my Volume
Group, and start adding more AppVMs to the pool, that starts writing to the
PV...
Is the data on the new drive, encrypted?
Ca
On Monday, 13 August 2018 16:13:06 UTC-4, Chris Laprise wrote:
> On 08/13/2018 06:48 AM, 'awokd' via qubes-users wrote:
> > On Mon, August 13, 2018 7:59 am,
> >
> >> Should I mount each LV
> >> and attempt to import the root.img and private.img files? How would I
> >> mount those to get to the f
Qubes OS 4.0
Well, I broke my Qubes.
I was messing with a large vmdk converted to raw image, expanded to 100G on a
Volume Group that could not handle it.
Some errors did pop up, but with the space filled up, I could not do anything.
After reboot, no vms would start.
After attempting to repair us
On Sunday, 12 August 2018 09:59:57 UTC-4, Unman wrote:
> On Fri, Aug 10, 2018 at 11:00:30AM -0700, :
> > On Friday, 10 August 2018 11:31:08 UTC-4, Unman wrote:
> > > On Fri, Aug 10, 2018 at 07:39:45AM -0700,
> > > > Both /etc/qubes-rpc/policy/qubes.InputKeyboard and InputMouse, should
> > > > s
On Friday, 10 August 2018 11:31:08 UTC-4, Unman wrote:
> On Fri, Aug 10, 2018 at 07:39:45AM -0700,
> > Both /etc/qubes-rpc/policy/qubes.InputKeyboard and InputMouse, should say
> > something like this.
> >
> > sys-usb dom0 allow,user=root
> >
> > Yes, If you have a sys-usb set up, then the US
Both /etc/qubes-rpc/policy/qubes.InputKeyboard and InputMouse, should say
something like this.
sys-usb dom0 allow,user=root
Yes, If you have a sys-usb set up, then the USB keyboard will attach there
first. More specifically, the USB Host Controller that the USB keyboard is
plugged into is at
On Wednesday, 8 August 2018 13:34:14 UTC-4, Arnulf Maria Bultmann wrote:
> Hello,
> I use my yubikey besides other things as a password safe. under windows there
> is no problem to use the yubikey to type in the password into keepass.
> Now I want to use the yubikey for thesame procedure under qu
something like a custom PAM module... but with
Challenge/Response, my solution was to use the built-in pam_exec.so to run a
very short script when authenticating.
The only dependency is to install ykpers on sys-usb as it uses ykchalresp.
https://gist.github.com/Joeviocoe
In RC4.0... After suspend/resume
Any monitors that were inverted or rotated, will be black.
The mouse does move across the screen... but no objects move on this screen.
Refreshing the configurations by toggling to another terminal (ctrl-alt-f2)
then back again (ctrl-alt-f1), or changing the resol
Great, thank you so much.
Can you please update https://www.qubes-os.org/doc/releases/4.0/schedule/
Thanks again
--
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 Friday, 2 February 2018 01:03:14 UTC-5, ThierryIT wrote:
> Le jeudi 1 février 2018 18:01:21 UTC+2, awokd a écrit :
> > On Thu, February 1, 2018 3:46 pm, ThierryIT wrote:
> > > What am I doing wrong ?
> > >
> > >
> > > I have a Yubikey4 U2F + CCID.
> > > Not detected with "qvm-block"
> > > Detec
qvm-usb command shows you how to attach USB devices to VMs. There is no GUI
method like there is for block devices.
Remember, Yubikey is not a storage/block device. It is a USB that acts more
like a HID keyboard.
Mine works on 3.2 just fine using sys-usb, then attaching to whatever VM nee
P.S.
Can you please update https://www.qubes-os.org/doc/releases/4.0/schedule/
--
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...@googlegrou
Great news. Thank you.
I would prefer a fully functional Qubes Manager since a widget that requires
mouse click or hover is a pain in the butt to keep as a running dashboard.
That is what I like about the 3.2 version... that I can keep it in one of my
extra monitors. Seeing CPU spikes withou
On Thursday, 26 October 2017 13:37:10 UTC-4, Anirban Kar wrote:
> My Hardware:
> Processor- AMD Athlon X2 5200
> Mobo- Asrock 960GC-GS FX
> RAM- DDR2 800 MHz 2× 2GB
> HDD - Seagate 250 GB SATA 7200 rpm
>
>
> I can install and use Qubes 3.2 without any hassel but facing a hardware
> incompatibil
On Thursday, 26 October 2017 13:37:10 UTC-4, Anirban Kar wrote:
> My Hardware:
> Processor- AMD Athlon X2 5200
> Mobo- Asrock 960GC-GS FX
> RAM- DDR2 800 MHz 2× 2GB
> HDD - Seagate 250 GB SATA 7200 rpm
>
>
> I can install and use Qubes 3.2 without any hassel but facing a hardware
> incompatibil
On Wednesday, 25 October 2017 15:59:47 UTC-4, Yethal wrote:
>
> Code is on GitHub, nothing's stopping you from forking/sending a pull request
Please refrain from "just do it yourself" responses in the Qubes-Users group
forum.
People here are not developers, which has its own group forum. Thi
On Sunday, 22 October 2017 08:56:55 UTC-4, the2nd wrote:
> Regarding the other questions/problems.
>
> 2) If you want to unlock the luks device without yubikey you can use the
> steps from the "Something went wrong :(" section, skipping step 4. This
> should disable the ykluks module and re-ena
On Monday, 23 October 2017 23:42:56 UTC-4, the2nd wrote:
> Is there only one line? Or one line per uuid? Can you provide the complete
> Output?
>
>
> Regards
> the2nd
>
>
>
> Am 24.10.2017 5:31 vorm. schrieb "Ron Qubed" :
>
> On Sunday, October 22, 2017 at 6:56:55 AM UTC-6, the2nd wrote:
>
On Monday, 23 October 2017 11:37:13 UTC-4, Olesia K wrote:
> hello Qubes users
>
> I am trying to get windows tools installed on Qubes4.0 RC1. I a getting an
> error message when I do so.
>
> Input:
> sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
> qubes-windows-tools
>
> Res
On Saturday, 5 August 2017 11:20:27 UTC-4, the2nd wrote:
> Hi,
>
> i switched to Qubes OS 3.2 on my notebook some weeks ago. Besides some issues
> i had it works very well.
>
> One problem was to get the installer to install qubes on LVM-on-LUKS. I
> preferred this over the default LUKS-on-LVM
On Thursday, 5 November 2015 05:07:41 UTC-5, Unman wrote:
> On Thu, Nov 05, 2015 at 01:26:34AM -0800, Henri KONSTAIN wrote:
> > Wondering that as well.
> > MAC and IP are setup on DHCP server but the Qubes install did not 'take' it.
> > Had to enter manual entries in IPV4 Settings.
> >
> > On Thu
On Wednesday, 26 August 2015 19:55:46 UTC-4, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Wed, Aug 26, 2015 at 04:32:12PM -0700, Eric Shelton wrote:
> > A lot of the time in an HVM, out of the box X11 fails to either use the
> > QEMU VESA display a
On Saturday, 5 August 2017 11:20:27 UTC-4, the2nd wrote:
> Hi,
>
> i switched to Qubes OS 3.2 on my notebook some weeks ago. Besides some issues
> i had it works very well.
>
> One problem was to get the installer to install qubes on LVM-on-LUKS. I
> preferred this over the default LUKS-on-LVM
On Monday, 18 September 2017 23:32:53 UTC-4, cooloutac wrote:
> On Sunday, September 10, 2017 at 6:02:24 PM UTC-4, joev...@gmail.com wrote:
> > On Monday, 29 August 2016 01:34:11 UTC-4, Raphael Susewind wrote:
> > > > while initially I thought it would be interesting to try, the only
> > > > sit
On Monday, 29 August 2016 01:34:11 UTC-4, Raphael Susewind wrote:
> > while initially I thought it would be interesting to try, the only
> > situation when yubikey could actually improve security is having to boot a
> > Qubes PC under unavoidable surveilance.
>
> came to the same conclusion - p
38 matches
Mail list logo