Re: [qubes-users] AEM failure after upgrade

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 loke...@gmail.com: > The AEM package was upgraded recently (probably because of this > thread: > https://groups.google.com/forum/#!topic/qubes-users/3ZkmS5v7E38), > and after I installed the updated version, AEM stopped working > completely. > >

[qubes-users] Re: heads up, qubes 3.2 still vuln to cve-2016-4484 (minor severity)

On Thursday, July 13, 2017 at 10:36:25 PM UTC-7, qubester wrote: > So, to exploit this, someone would need physical access to the computer > at risk? physical or any network available OOB. heres an example of what can go wrong https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5689 on a

Re: [qubes-users] Re: Just realized one of the major disadvantages of Qubes OS...

This thread should be renamed ipv6, and there was such a thread in qubes-devel. one of the issues is what to do when moving from an ipv6 enabled network to one without. netvm can easily note the difference and adapt, but weather your bridging or natting, all the appvms wont know any better and

[qubes-users] Install issues Sager / Clevo laptop (7700k/GTX1080)

Booting the installer goes to text based install. Then complains about no LUKS password set for drive when I select destination drive. I then came across this thread: https://groups.google.com/forum/m/#!msg/qubes-users/-9qRHSkwfy8/CCx08nnTVEAJ Followed this to a T with my edited ks file. Got it

[qubes-users] HCL - Lenovo Yoga 900 for BIZ 80SD

Hello, after some painful troubles I have it running with Qubes 3.2. As might be expected there are some issues: Touchpad/Touchscreen do not work. I could not even find a touchpad USB device. It worked in the Qubes 4.0 preview. No Wifi after resume. Reloading the iwlwifi module did not help.

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

Was just reading through the qubes docs. You can delete your current sys-usb and make a new sys-usb and make it an appVM(sys-usb). Then you could attach it to a sys-firewall or sys-net . Im not 100% sure this will help but it is worth a try. Sorry I don't have time to write out the

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

On Saturday, 2 May 2015 15:04:38 UTC-4, Noah Vesely wrote: > I just PM'd you one. You don't need to give me anything in return. pm me one too -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving

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

Please can someone also send one to me! Very, very appreciated!! Thank you a million! -- 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] Re: off topic - invite codes to 'riseup'

On Tuesday, 28 October 2014 14:26:49 UTC-4, 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 for two invite codes needed to sign up to anonymous >

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

On Tuesday, 28 October 2014 14:26:49 UTC-4, 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 for two invite codes needed to sign up to anonymous >

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

Actually I do have the qubes-proxy-usb installed on my sys-usb (that's how I'm able to use my mouse) however I'm not sure if the qubes-proxy-usb can be used to pass the HW wallet. How I'm I suppose to pass my Ledger nano s or trezor via the proxy? > > On 14 July 2017 at 15:40 Patrik

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2017 02:19 PM, Mr. DONG wrote: > Unfortunately that doesn't work either. > > The "qvm-usb -l" doesn't show my legder nano s. In fact I can only > see it attached on the sys-usb, not on dom0. > > The qvm-usb list output shows no difference

Re: [qubes-users] i3 not working on two screens

On Fri, Jul 14, 2017 at 04:07:15AM -0700, zioasterb...@gmail.com wrote: > Yes, by "separating them" i mean to extend the desktop to two screens, > since now I see them mirrored (i.e. the eternal one is a copy of the > laptop's display) You can use xrandr to set up the different display outputs.

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

Unfortunately that doesn't work either. The "qvm-usb -l" doesn't show my legder nano s. In fact I can only see it attached on the sys-usb, not on dom0. The qvm-usb list output shows no difference either I attach or not the HW wallet. The only way I can attach to another appvm is if I attach

[qubes-users] Re: Debian Buster repo

On Friday, June 23, 2017 at 11:04:01 PM UTC+4:30, Dominique St-Pierre Boucher wrote: > Hello, > > Anyone switched their template from Stretch to Buster? I want to try but > there is no qubes repo for it!! > > Dominique Hi Dominique. I cloned my Debian Stretch template last night and gave it

Re: [qubes-users] i3 not working on two screens

Yes, by "separating them" i mean to extend the desktop to two screens, since now I see them mirrored (i.e. the eternal one is a copy of the laptop's display) I adopted the solution listed here, but with no success at all (it just changed the border of the windows in i3)

[qubes-users] [marma...@invisiblethingslab.com: [qubes-devel] Fedora 25 template for Qubes 3.2]

Good news everyone! /noor - Forwarded message from Marek Marczykowski-Górecki - From: Marek Marczykowski-Górecki To: qubes-devel Date: Thu, 13 Jul 2017 22:49:53 +0200 Subject:

Re: [qubes-users] i3 not working on two screens

On Thu, Jul 13, 2017 at 12:37:27PM -0700, zioasterb...@gmail.com wrote: > Hi, > I've just tried i3 on qubes3.2 but there is an issue with my external > monitor. I cannot separate them, even when I split and dispose > properly the screen in the settings, as you can see in the image. The > screens

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2017 02:54 AM, 'Essax' via qubes-users wrote: > Have you tried these steps: > > 1) Attach hardware wallet to sys-usb 2) Go to the dom0 Gui and and > right click on the appVM you want to attach it to. 3) In the box > that opens scroll down

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2017 09:45 AM, loke...@gmail.com wrote: > On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki > wrote: > >> Oh, it isn't listed in updates-status[1], so I completely forgot. >> Probably it was uploaded to testing before

Re: [qubes-users] How can I test that my AEM configuration is correct?

On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki wrote: > Oh, it isn't listed in updates-status[1], so I completely forgot. > Probably it was uploaded to testing before introducing that system. Of > course it should be migrated to current, will do. I updated to the latest AEM,

Re: [qubes-users] Re: Just realized one of the major disadvantages of Qubes OS...

On 07/14/2017 05:30 AM, motech man wrote: > On Thursday, July 13, 2017 at 12:05:34 PM UTC-5, geoff.m...@gmail.com > wrote: >> A bit of thread necromancy here, but - if you're using a smartphone >> in the US with mobile data, there's a *very* good chance you're >> already using IPv6. >> [...]>> >>

Re: [qubes-users] Re: How do I upgrade to Fedora 26?

On 07/14/2017 12:59 AM, Salmiakki wrote: > But those should work in 3.2 just fine, right? > Probably not; both because forcing the repository to the 4.0 will try to upgrade a lot of other system components, so the actual update may involve very convoluted command lines to avoid anything but the

Re: [qubes-users] Re: How do I upgrade to Fedora 26?

On 07/14/2017 01:00 AM, Salmiakki wrote: >> The problem is that there are no yum sources for qubes-related things >> for fedora 26, as Foppe said, so the upgrade will likely fail and, in >> case you manage to complete the upgrade, you will be left with a >> non-updatable set of qubes software for