Re: [qubes-users] Qubes 4.0-rc3

2020-04-16 Thread Manuel Amador (Rudd-O)
On 13/01/2018 03.34, Andrew David Wong wrote: > On 2018-01-12 08:00, 'awokd' via qubes-users wrote: > > On Fri, January 12, 2018 1:09 pm, Holger Levsen wrote: > > >> I'm not so sure, why not use git branches? > > > One reason that comes to mind: > > Segregating the documentation into two different

Re: [qubes-users] Qubes 4.0-rc3

2020-04-16 Thread Manuel Amador (Rudd-O)
On 12/01/2018 14.09, Holger Levsen wrote: > On Fri, Jan 12, 2018 at 01:04:23PM +, 'Tom Zander' via qubes-users wrote: >> On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users wrote: >>> Would it be of value if I went through the published Docs and added these >>> version headers?

Re: [qubes-users] Qubes 4.0-rc3 not installing on Lenovo P71

2018-01-27 Thread joeh9617
On Sunday, January 28, 2018 at 10:30:47 AM UTC+8, awokd wrote: > On Sun, January 28, 2018 2:13 am, xxx wrote: > > I burned the ISO to USB stick then started to install Qubes but got the > > following: > > > > > > [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup > > failure,

Re: [qubes-users] Qubes 4.0-rc3 not installing on Lenovo P71

2018-01-27 Thread 'awokd' via qubes-users
On Sun, January 28, 2018 2:33 am, Yuraeitha wrote: > > Awkward same-time posting x) > But listen to awokd, he has more experience than I do. Not that much more! Unfortunately, on these boot issues most come down to trial and error like you said... -- You received this message because you are

Re: [qubes-users] Qubes 4.0-rc3 not installing on Lenovo P71

2018-01-27 Thread Yuraeitha
On Sunday, January 28, 2018 at 3:30:47 AM UTC+1, awokd wrote: > On Sun, January 28, 2018 2:13 am, joeh9...@gmail.com wrote: > > I burned the ISO to USB stick then started to install Qubes but got the > > following: > > > > > > [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup

Re: [qubes-users] Qubes 4.0-rc3 not installing on Lenovo P71

2018-01-27 Thread 'awokd' via qubes-users
On Sun, January 28, 2018 2:13 am, joeh9...@gmail.com wrote: > I burned the ISO to USB stick then started to install Qubes but got the > following: > > > [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup > failure, AE_NOT_FOUND (20170531/dswload-210) [0.093383] ACPI >

Re: [qubes-users] Qubes 4.0-rc3

2018-01-12 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-12 07:58, awokd wrote: > On Fri, January 12, 2018 1:04 pm, Tom Zander wrote: >> On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users >> wrote: >> >>> Would it be of value if I went through the published Docs and >>> added

Re: [qubes-users] Qubes 4.0-rc3

2018-01-12 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-12 08:00, 'awokd' via qubes-users wrote: > On Fri, January 12, 2018 1:09 pm, Holger Levsen wrote: > >> I'm not so sure, why not use git branches? > One reason that comes to mind: Segregating the documentation into two different

Re: [qubes-users] Qubes 4.0-rc3

2018-01-12 Thread 'awokd' via qubes-users
On Fri, January 12, 2018 1:09 pm, Holger Levsen wrote: > I'm not so sure, why not use git branches? It doesn't sound like that's the route the Qubes team wants to take right now, but at least splitting the content on the same page would make it easier to migrate to that approach if they change

Re: [qubes-users] Qubes 4.0-rc3

2018-01-12 Thread 'awokd' via qubes-users
On Fri, January 12, 2018 1:04 pm, Tom Zander wrote: > On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users wrote: > >> Would it be of value if I went through the published Docs and added >> these version headers? Should newer versions be added at the top (so 4.0 >> before 3.2 content)?

Re: [qubes-users] Qubes 4.0-rc3

2018-01-12 Thread 'Tom Zander' via qubes-users
On Friday, 12 January 2018 13:09:35 GMT Holger Levsen wrote: > I'm not so sure, why not use git branches? That has my preference still, but I'm ok for any workable solution. -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel -- You received this

Re: [qubes-users] Qubes 4.0-rc3

2018-01-12 Thread Holger Levsen
On Fri, Jan 12, 2018 at 01:04:23PM +, 'Tom Zander' via qubes-users wrote: > On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users wrote: > > Would it be of value if I went through the published Docs and added these > > version headers? Should newer versions be added at the top (so

Re: [qubes-users] Qubes 4.0-rc3

2018-01-12 Thread 'Tom Zander' via qubes-users
On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users wrote: > Would it be of value if I went through the published Docs and added these > version headers? Should newer versions be added at the top (so 4.0 before > 3.2 content)? 4.0 might just be "TBD". I think that would be wonderful,

Re: [qubes-users] Qubes 4.0-rc3

2018-01-12 Thread 'awokd' via qubes-users
On Fri, January 12, 2018 4:20 am, Andrew David Wong wrote: > It shouldn't require much effort. In most cases, all you have to add > is `## Qubes 3.2` above the existing documentation, shift the rest of the > headers down one by adding a `#` in front of each one, then add `## Qubes > 4.0` above

Re: [qubes-users] Qubes 4.0-rc3

2018-01-11 Thread Chris Laprise
On 01/11/2018 10:31 PM, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2018-01-11 14:41, Chris Laprise wrote: >> >> At least no section repetition for the scripts should be necessary. But >> doing this for the dialogs still adds a lot to an already long doc.

Re: [qubes-users] Qubes 4.0-rc3

2018-01-11 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-11 16:11, 'Tom Zander' via qubes-users wrote: > On Thursday, 11 January 2018 18:16:04 GMT Unman wrote: >> On the VPN case your own comment confirms that it would be >> better to provide a separate section, rather than trying to put >>

Re: [qubes-users] Qubes 4.0-rc3

2018-01-11 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-11 14:41, Chris Laprise wrote: > On 01/11/2018 01:16 PM, Unman wrote: >> On Thu, Jan 11, 2018 at 09:18:46AM +, 'Tom Zander' via qubes-users wrote: >>> On Thursday, 11 January 2018 03:42:11 GMT Andrew David Wong wrote: On

Re: [qubes-users] Qubes 4.0-rc3

2018-01-11 Thread 'Tom Zander' via qubes-users
On Thursday, 11 January 2018 18:16:04 GMT Unman wrote: > On the VPN case your own comment confirms that it would be better to > provide a separate section, rather than trying to put "exceptions" in to > the existing text. Thank you for explaining that unman, much clearer indeed. While I agree on

Re: [qubes-users] Qubes 4.0-rc3

2018-01-11 Thread Chris Laprise
On 01/10/2018 03:47 PM, Connor Page wrote: > The official templates use nftables so shouldn’t be mixed with iptables. I > didn’t have time to learn about nftables, so just removed nftables package > from debian 9 template. YMMV. > Hmmm, I was just thinking how Qubes' own guest scripts still

Re: [qubes-users] Qubes 4.0-rc3

2018-01-11 Thread Chris Laprise
On 01/11/2018 01:16 PM, Unman wrote: > On Thu, Jan 11, 2018 at 09:18:46AM +, 'Tom Zander' via qubes-users wrote: >> On Thursday, 11 January 2018 03:42:11 GMT Andrew David Wong wrote: >>> On 2018-01-10 12:53, 'Tom Zander' via qubes-users wrote: >> I poked the Qubes guys about providing a

Re: [qubes-users] Qubes 4.0-rc3

2018-01-11 Thread Unman
On Thu, Jan 11, 2018 at 09:18:46AM +, 'Tom Zander' via qubes-users wrote: > On Thursday, 11 January 2018 03:42:11 GMT Andrew David Wong wrote: > > On 2018-01-10 12:53, 'Tom Zander' via qubes-users wrote: > > > > I poked the Qubes guys about providing a separate dir on the website to > > >

Re: [qubes-users] Qubes 4.0-rc3

2018-01-11 Thread 'Tom Zander' via qubes-users
On Thursday, 11 January 2018 03:42:11 GMT Andrew David Wong wrote: > On 2018-01-10 12:53, 'Tom Zander' via qubes-users wrote: > > I poked the Qubes guys about providing a separate dir on the website to > > make it clear what is 3.x and what is 4.x specific, but they stated we > > should instead

Re: [qubes-users] Qubes 4.0-rc3

2018-01-10 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-10 12:53, 'Tom Zander' via qubes-users wrote: > On Wednesday, 10 January 2018 18:32:39 GMT Chris Laprise wrote: >> I also have a download-able project that makes the scripted/antileak >> setup fairly simple in Qubes R4.0: > > Please

Re: [qubes-users] Qubes 4.0-rc3

2018-01-10 Thread Connor Page
The official templates use nftables so shouldn’t be mixed with iptables. I didn’t have time to learn about nftables, so just removed nftables package from debian 9 template. YMMV. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe

Re: [qubes-users] Qubes 4.0-rc3

2018-01-10 Thread Chris Laprise
On 01/10/2018 01:53 PM, 'Tom Zander' via qubes-users wrote: On Wednesday, 10 January 2018 18:32:39 GMT Chris Laprise wrote: I also have a download-able project that makes the scripted/antileak setup fairly simple in Qubes R4.0: Please consider updating the docs repo with this :-) I poked the

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

2018-01-07 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, Jan 07, 2018 at 04:59:44AM -0800, Fabrizio Romano Genovese wrote: > Ok, I dug a bit deeper into this. It doesn't look like a problem of how much > memory I give to VMs. Essentially, my QubesOS boots in two different ways: > > - When

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

2018-01-07 Thread Yuraeitha
On Sunday, January 7, 2018 at 1:59:45 PM UTC+1, Fabrizio Romano Genovese wrote: > Ok, I dug a bit deeper into this. It doesn't look like a problem of how much > memory I give to VMs. Essentially, my QubesOS boots in two different ways: > > - When QubesOS is happy, it starts in ~1 min (yup,

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

2018-01-07 Thread Yuraeitha
On Sunday, January 7, 2018 at 1:59:45 PM UTC+1, Fabrizio Romano Genovese wrote: > Ok, I dug a bit deeper into this. It doesn't look like a problem of how much > memory I give to VMs. Essentially, my QubesOS boots in two different ways: > > - When QubesOS is happy, it starts in ~1 min (yup,

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

2018-01-07 Thread Fabrizio Romano Genovese
Ok, I dug a bit deeper into this. It doesn't look like a problem of how much memory I give to VMs. Essentially, my QubesOS boots in two different ways: - When QubesOS is happy, it starts in ~1 min (yup, starting up all the VMs still takes a while). The overall system is very reactive, for

Re: [qubes-users] Qubes 4.0 rc3, Whonix template: update-command-not-found

2018-01-06 Thread 'awokd' via qubes-users
On Sat, January 6, 2018 1:19 am, Fabrizio Romano Genovese wrote: > Yup, if you type curl it works, but you can't curl anything out of it OK, I see what you mean. What are you trying to accomplish? If it's just a one time file copy, you could use qvm-copy-to-vm to copy it to your template from

Re: [qubes-users] Qubes 4.0 rc3, Whonix template: update-command-not-found

2018-01-05 Thread Fabrizio Romano Genovese
Yup, if you type curl it works, but you can't curl anything out of it because you don't have connection. To reproduce what I'm talking about, open a terminal in whonix-ws/gw and type some random stuff (like "sdshgow"). Press enter. Whonix will tell you "Could not find the database of available

Re: [qubes-users] Qubes 4.0 rc3, Whonix template: update-command-not-found

2018-01-05 Thread 'awokd' via qubes-users
On Fri, January 5, 2018 11:11 pm, Fabrizio Romano Genovese wrote: > > This very very annoying thing happened to me also on Qubes 3.2. > Essentially, on a whonix-based template, (whonix-ws or whonix-gw, doesn't > really matter), every time I type something (aside of some basic commands > such as

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

2018-01-04 Thread 'Tom Zander' via qubes-users
On Thursday, 4 January 2018 11:49:45 GMT Fabrizio Romano Genovese wrote: > Looking at the console messages at startup, it looks like the problem is > that Qubes takes more than one minute to boot sys-net, sys-firewall, > sys-usb and sys-whonix. That was not the case in 3.2. > > Also, when giving

Re: [qubes-users] Qubes 4.0 RC3 (installation) MEGA-HUGE security flaw! (report the bug below or quit the program)

2017-12-02 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-11-29 15:03, genevieve.c.gauth...@gmail.com wrote: > On Wed, 2017-11-29 at 15:59 +, Unman wrote: >> In the Fedora documentation there ARE methods described for >> getting bug reports out of the install process, but they require >>

Re: [qubes-users] Qubes 4.0 RC3 (installation) MEGA-HUGE security flaw! (report the bug below or quit the program)

2017-11-29 Thread genevieve . c . gauthier
On Wed, 2017-11-29 at 15:59 +, Unman wrote: > In the Fedora documentation there ARE methods described for getting > bug > reports out of the install process, but they require active > intervention > from the user (copy to another drive or scp across network). There's > no > suggestion that

Re: [qubes-users] Qubes 4.0 RC3 (installation) MEGA-HUGE security flaw! (report the bug below or quit the program)

2017-11-29 Thread Unman
On Wed, Nov 29, 2017 at 02:51:33AM -0500, '[799]' via qubes-users wrote: > Hello Unman, > > >> It's perfectly possible that the installer (not principally written by > >> Qubes) could mistakenly include a passphrase string. > > As far as I have understand, the problem is not that the password is

Re: [qubes-users] Qubes 4.0 RC3 (installation) MEGA-HUGE security flaw! (report the bug below or quit the program)

2017-11-29 Thread 'Tom Zander' via qubes-users
On Wednesday, 29 November 2017 02:40:01 CET Genevieve Gauthier wrote: > What do you need me to do ? Please expain in a little more detail what versions of the software you were using, what steps we might follow to reproduce the problem. For instance which screen was the last thing that was on

Re: [qubes-users] Qubes 4.0 RC3 (installation) MEGA-HUGE security flaw! (report the bug below or quit the program)

2017-11-29 Thread 'Tom Zander' via qubes-users
On Wednesday, 29 November 2017 08:51:33 CET '[799]' via qubes-users wrote: > As far as I have understand, the problem is not that the password is > shown, but that the report with this error mistake and the password could > get transferred. I don't want that my password gets transferred in some >

Re: [qubes-users] Qubes 4.0 RC3 (installation) MEGA-HUGE security flaw! (report the bug below or quit the program)

2017-11-28 Thread '[799]' via qubes-users
Hello Unman, >> It's perfectly possible that the installer (not principally written by >> Qubes) could mistakenly include a passphrase string. As far as I have understand, the problem is not that the password is shown, but that the report with this error mistake and the password could get

Re: [qubes-users] Qubes 4.0 RC3 (installation) MEGA-HUGE security flaw! (report the bug below or quit the program)

2017-11-28 Thread Genevieve Gauthier
I do not know how to help you. I have taken a picture without removing the geotag (authentic picture /w geotag in my own living room. the picture (one of many) is in my iphone but my own finger is hiding MY OWN PASSPHRASE... I could see it 20/20.. I still have everything I used (my own laptop),

Re: [qubes-users] Qubes 4.0 RC3 (installation) MEGA-HUGE security flaw! (report the bug below or quit the program)

2017-11-28 Thread Unman
On Tue, Nov 28, 2017 at 07:48:49PM -0500, '[799]' via qubes-users wrote: > Hello, > > Original-Nachricht > An 29. Nov. 2017, 00:48, schrieb: > Sorry but I almost fainted ! (I even took a picture ! I could not believe > this MEGA-HUGE security flaw right in front of my eyes ) >