Re: [qubes-users] Valid Concerns Regarding Integrity of Whonix Project

Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Friday, February 15, 2019 10:58 PM, wrote: > Dear Patrick, > > I appreciate your answer and understand your point of view. On the other > side, the issue raised by the law in Australia (and GCHQ asked for that too, >

Re: [qubes-users] Installing snaps in appvms?

On 1/9/19 8:02 PM, Stumpy wrote: On 1/9/19 7:54 PM, Stumpy wrote: On 1/9/19 7:32 PM, Marek Marczykowski-Górecki wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Jan 09, 2019 at 07:11:50PM -0500, Chris Laprise wrote: On 01/09/2019 06:41 PM, Stumpy wrote: On 1/8/19 7:59 PM,

Re: [qubes-users] How does Qubes DNS resolving work?

On Fri, Feb 15, 2019 at 08:12:35AM +0100, ashleybrown...@tutanota.com wrote: > > Please don't top post. Take a minute to make it easier for other users. > > As is clear in another thread, there is a clear warning about DNS on the > > GUI firewall - I find it hard to believe that anyone could miss

[qubes-users] Re: Dom0 some updates always skipped

Em sexta-feira, 15 de fevereiro de 2019 23:03:12 UTC-2, Sergio Matta escreveu: > > Some updates show as always skipped after each qubes-dom0-update run. > > > > How to fix this? > > Maybe "sudo qubes-dom0-update --best --allowerasing" can solve your problem, > if not maybe they are already

[qubes-users] Re: Dom0 some updates always skipped

> Some updates show as always skipped after each qubes-dom0-update run. > > How to fix this? Maybe "sudo qubes-dom0-update --best --allowerasing" can solve your problem, if not, tell us what packages are not installing. -- You received this message because you are subscribed to the

[qubes-users] Dom0 some updates always skipped

https://i.imgur.com/qnH5JNh.png Some updates show as always skipped after each qubes-dom0-update run. How to fix this? Thanks! -- 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

[qubes-users] HCL - Purism Librem 15 v4

%40puri.sm. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Purism-Librem_15_v4-20190215-182240.yml Description: Binary data

Re: [qubes-users] Black screen when booting Qubes 4.0.1 installer via usb

Dan Grant wrote on 2/15/19 4:53 PM: Turns out there's a hardware issue with this laptop so a replacement is being sent. I'll test this again when I get the new one after confirming the general issue has been resolved. I suspect I'll see the same thing, but at least I'll know for sure.

[qubes-users] dom0 update skippet

Some updates show as always skipped after each qubes-dom0-update run. How to fix this? i.imgur [DOTCOM] / qnH5JNh [dot] png Thanks! -- 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,

[qubes-users] [warn] last whonix-gw update, ipv6 and possible VPN leak!

> FWIW, I'm not sure when Qubes started enabling ipv6 by default. I > thought > R4.0 was going to support ipv6 but leave it disabled by default? > Thanks for > fix. I found it! BTW, I have the same question! I never enable ipv6 and it's > my old vpn vm! Maybe I'm compromised? All work like a

Re: [qubes-users] Valid Concerns Regarding Integrity of Whonix Project

Dear Patrick, I appreciate your answer and understand your point of view. On the other side, the issue raised by the law in Australia (and GCHQ asked for that too, like the request of ghost user in all the "encrypted" conversations) is an important security concern and should be taken into

Re: [qubes-users] How does Qubes DNS resolving work?

ashleybrown...@tutanota.com wrote on 2/15/19 7:12 AM: I am new to mailing lists. What does top-post mean? Do you mean don't post the reply at the top of the message and instead at the bottom like this? Much better, thank you. If you want to make sure there is no network communication from

Re: [qubes-users] [warn] last whonix-gw update, ipv6 and possible VPN leak!

On 2/15/19 4:14 PM, 'Evastar' via qubes-users wrote: Hello, Seems after last whonix update my old VPN VM begin leaking traffic. After investigation I found that it's because ipv6 primary connection to whonix-gw. I guess that whonix-gw now supporting ipv6. It leak traffic through ipv6

[qubes-users] [warn] last whonix-gw update, ipv6 and possible VPN leak!

Hello, Seems after last whonix update my old VPN VM begin leaking traffic. After investigation I found that it's because ipv6 primary connection to whonix-gw. I guess that whonix-gw now supporting ipv6. It leak traffic through ipv6 connection to whonix and ignore my default old ipv4 setup.

[qubes-users] Qubes for enterprise usage

Hi all, Did anyone try to use Qubes for enterprise use cases? e.g. for securing access to sensitive resources? How did that end up? Last time I looked at Qubes, it didn't have enterprise manageability features and required users to be familiar with Linux, which is not always the case with

Re: [qubes-users] Effectiveness of the VM compartimentation

On 2/15/19 8:47 AM, nosugarmaxta...@gmail.com wrote: On Friday, 15 February 2019 16:37:17 UTC+11, Chris Laprise wrote: On 2/14/19 10:02 PM, nosugarmaxta...@gmail.com wrote: Hi all, Right now I use Qubes for a bit of fun - setting up VPN's - chaining them, trying to get HVM's up and running,

Re: [qubes-users] Black screen when booting Qubes 4.0.1 installer via usb

On Wed, 13 Feb 2019 17:32:14 -0600 'awokd' via qubes-users wrote Dan Grant wrote on 2/13/19 7:20 AM: > I am able to comment out the mapbs and noexitboot lines in the > [qubes-verbose] section of EFI/BOOT/BOOTX64.cfg, but it is not at all

Re: [qubes-users] Effectiveness of the VM compartimentation

On Friday, 15 February 2019 16:37:17 UTC+11, Chris Laprise wrote: > On 2/14/19 10:02 PM, nosugarmaxta...@gmail.com wrote: > > Hi all, > > > > Right now I use Qubes for a bit of fun - setting up VPN's - chaining them, > > trying to get HVM's up and running, just messing about. I do plan to > >

Re: [qubes-users] Valid Concerns Regarding Integrity of Whonix Project

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * I was advised in private e-mail by @mig5 about this new law before it took effect beforehand, and @mig5 offered to step aside because of it. It was my decision to not to change anything. Below I will explain why. * I might have reacted in a

[qubes-users] How to get qubes-users ml archive

Tutanota interface can't display messages by thread and this was driving me crazy when reading mailing list messages so I switched to elude.in which seems to work like a charm: * clearnet and darknet address * IMAP/POP and SMTP support * works perfectly in Qubes Whonix with Thunderdird + TorBirdy