[qubes-users] HCL - ASRock B450 Pro4
HCL Report, ASRock B450 Pro4 with AMD Ryzen 5 3400G CPU. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABOFDF5swsdMVFeQPwx4iKnjh3NZdUWFn8irSyGTNsu8JHGRDg%40mail.gmail.com. Qubes-HCL-ASRock-B450_Pro4-20220424-080559.yml Description: application/yaml
[qubes-users] Whonix-14 "Failed to start Tor Browser"
I just updated to Whonix-14, and I'm getting an error code 255 when I try to start it. When I start it with Debug enabled, I'm seeing: ./start-tor-browser --debug XPCOMGlueLoad error for file /home/user/.tb/tor-browser/Browser/libxul.so: ./TorBrowser/Tor/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /home/user/.tb/tor-browser/Browser/libxul.so) Couldn't load XPCOM. Anybody else see this problem? Anybody have a fix? -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9fd9266b-2137-4277-b05c-e1dc1787c7d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes Domains.py Widget Seems Wedged
I'm seeing an oddity with this widget. At random, some VMs show the update indicator as continuously spinning. It appears to show a VM always starting, but qvm-ls in dom0 shows the VM as started. In a nutshell, the widget seems to be unsure of the VM's state. Anyone else seeing this? Is there a workaround/fix I can try? Oh, I am running Qubes 4.0. Bill Bormann -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a87aeada-61d3-4df5-bb81-cfa3a477fd2f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Issues with Yubikey 4 input
I have a FIDO U2F Yubico Security Key that I use for authentication to Gmail and Facebook. In my situation, I decided to use a single VM for two factor authentication. Here's what I did: 1. Find a free USB controller. I didn't want to use the same one as my keyboard or mouse. Your board specs and the lsusb utility are your friends in the hunt. Check out the Qubes document "Assigning Devices to VMs" for the gory details of discovering the PCI device assignments to your USB controllers. 2. In the VM you plan to use the key, you'll want to assign the PCI device for your free hub to that VM. That's accomplished by firing up Qube settings for the VM and selecting the devices tab. Scroll down to the available device and move it to the selected box. 3. You might have to configure strict reset (or disable strict reset) for the USB controller. 4. Start the VM. One gotcha: the VM won't run in PVH mode once you make this assignment. But, my Yubikey lights up when Gmail or Facebook need the second factor, and it works as advertised. On Friday, March 9, 2018 at 12:34:06 PM UTC-5, Jon R. wrote: > Hello, > > I've scoured around the mailing lists / SO / Reddit and haven't come across a > solution to this yet. I'm running 4.0 (R4.0) and when I attempt to use my > Yubikey it's seemingly not picking up any input on the button press. > > It's detecting the USB properly and I can attach it fine: > > [cloe@dom0 Desktop]$ qvm-usb > BACKEND:DEVID DESCRIPTION USED BY > sys-usb:2-1 Yubico_Yubikey_4_OTP+CCID > > [cloe@dom0 Desktop]$ qvm-usb attach work sys-usb:2-1 > > [cloe@dom0 Desktop]$ qvm-usb > BACKEND:DEVID DESCRIPTION USED BY > sys-usb:2-1 Yubico_Yubikey_4_OTP+CCID work > > However upon button presses on the Yubikey in the "work" domain there is no > action. I've tested this in gedit, the terminal and elsewhere to no avail. > > > Can someone point me in the right direction as to what may be happening? I've > successfully attached storage devices and other smart card related devices > without any issue so it seems to be isolated to the Yubikey itself. I've > tried 2 separate Yubikey 4's and an older version to no avail. > > > Thank you for your time. > > > - Cody -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7e00edc7-3c2a-462e-98c6-443dd1af7d36%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Yubico FIDO U2F Security Key and Qubes
> oh, you make a good point. I indeed made an assumption that it was about > lock-out by the "reading guides" line, and I somehow missed the line > regarding Google and Facebook services. I must then have misunderstood, I > apologize. > > I just tested the Yubi key I got laying around, it works in sys-usb, or > whereever the controller is located, be it dom0 or another AppVM with a > working USB controller. But it doesn't seem like either the qvm-usb (or its > GUI counterpart in the menu-widget introduced in Qubes 4, works. At least it > doesn't appear on my system. > > But it works wherever the USB controller is located, just not in the VM's > that are virtually linked with qvm-USB and the GUI-widget counterpart. > > As such, one can probably estimate the Yubi key working, if one has a working > USB controller to spare, and that USB controller can feasibly be passed > directly to the AppVM. But it can be tricky to find hardware that allows > passthrough, especially considering the drivers are often not made for it, as > well as there aren't terribly many products with multiple controllers on them > to pick between. On laptops, it's hard to know in advance how many > controllers there are, as it's not a marketing information, nor something > frequently found in product reviews, quite frustrating. But if determined, > can probably get extra USB controllers to spare, but it might be on the > expensive side if making a mistake, like buying a computer that only had one > controller, or the extra controller can't be passed through. > > But if one has a system with extra USB controllers, and it works to pass an > USB controller directly into the AppVM (test other USB applications work), > then the Yubi key should naturally work too. > > Perhaps there are easier work-arounds, or maybe the qvm-usb/GUI-widget it > works on other systems. This is exactly what I was hoping. I'm not planning to use it for luks or Qubes user login, but as a second authentication factor when I log into Gmail or (shudder) or decide to catch up on Facebook. It turns out I do have a spare controller. Time to bring up sys-usb. -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/66ea85e2-440c-4e2b-8ad8-87cdeb9b3f64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Yubico FIDO U2F Security Key and Qubes
On a lark, I purchased a Yubico FIDO U2F Security key. It's an inexpensive USB token that can be used for two-factor authentication for Gmail and Facebook, among others. I'd like to use it on my Qubes RC4 system. I've read the USB documentation, but thought I'd see if somebody else running Qubes has managed to get this working as advertised on their system. The current path that seems most promising is to bring up SYS-USB, but I have some concerns about doing this since my keyboard and mouse are both usb devices. Can anyone reply with a "hand waving" set of steps I should follow? I would greatly appreciate hearing your solution. -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0e44c37a-9c73-44b4-beff-657272342062%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] What happened to domain manager in 4?
On Friday, December 8, 2017 at 12:09:41 AM UTC-5, Chris Laprise wrote: > On 12/07/2017 12:17 PM, 'Tom Zander' via qubes-users wrote: > > On Thursday, 7 December 2017 14:17:52 CET Franz wrote: > >>> On another note what would it take ($$$) for someone to create this back > >>> on 4 as an option for the community (obviously theres quite a few of us) > >>> that want this to install? > >>> > >>> Im not rich by any means living in one bedroom apt and work from home > >>> but > >>> this does help me with work and would donate towards getting this done. > >> that is an interesting approach, developers can make programs, but > >> non-developers can pay for others to do it. I offer $5000. > > Hi guys, > > > > I've investigated the possibilities today about how this can be done from a > > purely technical point of view. > > > > It seems possible, and to test this I am writing a very simple app that > > retrieves the current Qubes and their status from the central qubes system. > > Just as a proof-of-concept. > > > > Looks promising so far! > > There is the question of whether someone should try porting the original > Qt-based Qubes Manager to R4.0. I mention this since the biggest > complaint so far is not having a _comprehensive_ UI; Updating QM for the > new Qubes API could be the most direct path to addressing that need. > > I'd like to know what people think... > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 Glad you asked. I'd prefer the development team focus on the security and stability of the 4.0 release candidate system and not divert any resources to the old 3.2 manager. The CLI is fine as far as I'm concerned. -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5605c2ca-ca7c-4857-b930-2aa16592927b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - ASRock FM2A88M Pro3
Been running Qubes 4.0-rc2 since it was released. DOM0 uptime is currently sitting at 17 days. I'm chasing a few problems with the DVMs, but otherwise I am very happy with the stability of the release candidate. -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bba2f7f6-3e6c-456a-b19b-b86c6d507762%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-ASRock-FM2A88M_Pro3_-20171123-091136.yml Description: Binary data
Re: [qubes-users] Re: Qubes 4.0rc2 install on corebooted Lenovo G505s (AMD)
I also experienced problems with item 2. The progress meter would simply stop and the system would appear to be locked up. I was installing RC2 to a USB stick. Amazingly, the system was actually making progress despite what the meter was reporting. By coincidence, my attention was diverted and I had to walk away from the system. When I returned, it was ready for the next installation step. -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/71e45a21-b3bc-467d-9cec-351592582c4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
I had this problem as well. However, the problem vanished when I adjusted the qrexec_timeout setting to 120 via qvm-prefs for the desired VMs. This kind of makes sense, since I'm doing my RC2 testing from a usb stick (color me cautious). -- 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 this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/227ac3ab-6c00-40ae-a2e0-e82f2e5bc35f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
