[qubes-users] HCL - Lenovo X270

[Stephan Telling]

Runs beautifully. I have not experienced any problems, it powers
multiple displays, plays audio/video just fine, FN keys appear to work
and suspend/resume appears to be working as well (not something I use).

Untested:
- Webcam
- Microphone

dmesg reports TPM: [   16.445973] tpm_tis MSFT0101:00: 2.0 TPM
(device-id 0x0, rev-id 78) but qubes-hcl-report reports unknown.

-- 
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/73783e54-d529-cd1d-1572-7c5b81a00fde%40telling.xyz.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-LENOVO-20HN0012MX-20181119-085042.yml
Description: application/yaml

[qubes-users] XSA-276, XSA-277, and XSA-279 do not affect the security of Qubes OS

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Qubes Community,

The Xen Project has published Xen Security Advisories 276, 277, and 279
(XSA-276, XSA-277, and XSA-279, respectively). These XSAs do *not*
affect the security of Qubes OS, and no user action is necessary.

These XSAs have been added to the XSA Tracker:

https://www.qubes-os.org/security/xsa/#276
https://www.qubes-os.org/security/xsa/#277
https://www.qubes-os.org/security/xsa/#279

This announcement is also available on the Qubes website:
https://www.qubes-os.org/news/2018/11/19/xsa-276-277-279-qubes-not-affected/

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlv0yhMACgkQ203TvDlQ
MDAcQA//Qj5Qk5VDED0mvUOBAoFl6EeQApBCPBDBosh6ORlazfQNSX1m0SvTwjck
CheHiTBtW7qVjPafK/hMoMT2pCOleJJk9FzW7dW2MCYrZfWHp1LBYEcZ61t17CJs
jfIw6BaYpJccuZUaE5LfYQa2qVipRvD5EYLN9yqU9MQEJUyD/CK1O3Wc3yhrZ01e
2mSqlVWR7qxzM5Fy+sU7SspyHN5HM3Le0LWnrUf3+gz19Dr6jpz3q7S1N6w1ram1
roC3S4Egw0hLQdgQfbLvpAI7WZWF78PYd9A8hYPvK9ywT4mgOBczKf9COjUkSIic
+bBQf6uVKy0tybPJwwwTLPCOrvuskHAhGaKihHYvtk634SUIxYd8Ncm+Z/DaKK5P
TG5DbpsLCYzBsmzQF8eVtDFqFe1vbrx5ie3QLAGljtkggAbgyr883X90rgb7ijkV
jg3NnIpKbS86FfanxmHlT8R36p0TyWNoWySjYjK+ecR94GAN/mgk5uskGSabMNyQ
ZbjvRI1s0n1U1vt5RUZyhgSw6qv+NCk7b2BSYEECFs5kkhLuUf1PKgbREnIgsBa0
mv5b6fbRw45lK4+5z1SiTC9aq/f9SGZNrP7I33dzrnlb00zc7U1FR3LzQi7PRKPr
faNGVj0qtEb3Xulk4vD7yveGAIJjpo9ZFRoo3IGoZg57Vf/9K6E=
=h8UB
-END PGP SIGNATURE-

-- 
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/76922817-8589-c32f-8a91-e7f624094e4f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] QSB #44: Multiple Xen vulnerabilities (XSA-275, XSA-280)

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Qubes Community,

We have just published Qubes Security Bulletin (QSB) #44: Multiple Xen
vulnerabilities (XSA-275, XSA-280). The text of this QSB is reproduced
below. This QSB and its accompanying signatures will always be available
in the Qubes Security Pack (qubes-secpack).

View QSB #44 in the qubes-secpack:

https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-044-2018.txt

Learn about the qubes-secpack, including how to obtain, verify, and read
it:

https://www.qubes-os.org/security/pack/

View all past QSBs:

https://www.qubes-os.org/security/bulletins/

View XSA-275 and XSA-280 in the XSA Tracker:

https://www.qubes-os.org/security/xsa/#275  
https://www.qubes-os.org/security/xsa/#280

```


 ---===[ Qubes Security Bulletin #44 ]===---

 2018-11-20

   Multiple Xen vulnerabilities (XSA-275, XSA-280)

Summary


On 2018-11-20, the Xen Security Team published multiple Xen Security
Advisories (XSAs):

XSA-275 [1] "insufficient TLB flushing / improper large page mappings
with AMD IOMMUs":
| In order to be certain that no undue access to memory is possible
| anymore after IOMMU mappings of this memory have been removed,
| Translation Lookaside Buffers (TLBs) need to be flushed after most
| changes to such mappings.  Xen bypassed certain IOMMU flushes on AMD
| x86 hardware.
| | Furthermore logic exists Xen to re-combine small page mappings
| into larger ones.  Such re-combination could have occured in cases
| when it was not really safe/correct to do so.
| | A malicious or buggy guest may be able to escalate its privileges, may
| cause a Denial of Service (DoS) affecting the entire host, or may be
| able to access data it is not supposed to access (information leak).

XSA-275 affects only AMD CPUs using IOMMU on both Qubes OS 3.2 and Qubes
OS 4.0. XSA-275 does not affect Intel CPUs on any Qubes OS version.

XSA-280 [2] "Fix for XSA-240 conflicts with shadow paging":
| The fix for XSA-240 introduced a new field into the control structure
| associated with each page of RAM.  This field was added to a union,
| another member of which is used when Xen uses shadow paging for the
| guest.  During migration, or with the L1TF (XSA-273) mitigation for
| PV guests in effect, the two uses conflict.
| | A malicious or buggy x86 PV guest may cause Xen to crash, resulting in
| a DoS (Denial of Service) affecting the entire host.  Privilege
| escalation as well as information leaks cannot be ruled out.

XSA-280 affects only Qubes OS 3.2. XSA-280 does not affect Qubes OS 4.0,
since the shadow paging feature is disabled at build time for 4.0.

Patching
=

The specific packages that resolve the problems discussed in this
bulletin are as follows:

  For Qubes OS 3.2:
  - Xen packages, version 4.6.6-45

  For Qubes OS 4.0:
  - Xen packages, version 4.8.4-7

The packages are to be installed in dom0 via the Qubes VM Manager or via
the qubes-dom0-update command as follows:

  For updates from the stable repository (not immediately available):
  $ sudo qubes-dom0-update

  For updates from the security-testing repository:
  $ sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing

A system restart will be required afterwards.

These packages will migrate from the security-testing repository to the
current (stable) repository over the next two weeks after being tested
by the community.

If you use Anti Evil Maid, you will need to reseal your secret
passphrase to new PCR values, as PCR18+19 will change due to the new
Xen binaries.

Credits


See the original Xen Security Advisory.

References
===

[1] https://xenbits.xen.org/xsa/advisory-275.html
[2] https://xenbits.xen.org/xsa/advisory-280.html

- --
The Qubes Security Team
https://www.qubes-os.org/security/
```

This announcement is also available on the Qubes website:
https://www.qubes-os.org/news/2018/11/20/qsb-44/

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlv0yfkACgkQ203TvDlQ
MDBPPRAAsvklyGwHVwvNYbDpSRfNr3Q7zvsyPRNW6UBBOKZjiczixrCxEt23Ok12
VScalFyjtb7YcH6NnLuvNYFXWLA3mB0BsXK3A/kKqM4n00QbRPStihDGpdtm04kJ
7wb7J/zKpU3iYWNZepI/0GyYluq3JXNkfS5EoAhMaNYAkwA1mzLRU7Ogp5B3ibu1
IYycXPxouv32Ay3TqOl1lTHBMT16mx2uQkqZDXaFB0Rk8CjUCOawiJB+dQmhRxg8
wE61EFe2XDzaR8T9BbZ3nEB7qQthUa4rBARk5ch/lC347SE+s2w1mW5vkgFit1ZL
cniMgT+mujHLKkv21Owg96VwO1LL+OBu/K3vJcwzBYGdwbgNZsHISHXLFKyk8UZ9
MxmXnXj+NzWmz/p9dHEIFQQ6kz0I8glHkS51PVqWCK5ujgimdysaqF9kp67BY0cH
tk79CXIeNnqGiX8fkXA5p24smnkn+XoP6B3g8fZXMt1So8jCaG2xvKGjoxgIRKpA
Y5W42w7D9DHSlL/OMGVybY/1lRl6ylHVPecnQG6gQLRsmtKgSkhjYxRD2Y92uaRp
0RCSKBz+PF5CbLcd7CCybMFxipzTF2PNrdz4eHahcHSkKj3EsO4vI3rYgqA2K55x
gqxO6e5GYAmJp8R/Zf1UBklsyioOS0WFvyssJiEWTwh2jbRHTcw=
=Hpgh
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To 

[qubes-users] Re: X1 Carbon again; Qubes DSDT override?

[richard . deyoung]

On Thursday, November 8, 2018 at 3:04:12 PM UTC-6, mark...@gmail.com wrote:
> On Monday, November 5, 2018 at 7:20:17 PM UTC+2, pkra...@gmail.com wrote:
> > Dan, 
> > Thank you for the instructions! I would like to confirm the patch still 
> > works against 4.14.72.1
> > 
> > The only problem I had with original instruction is that yum didn't want to 
> > install another kernel (compiled one) with identical version (one was 
> > already installed since I did upgrade first) - I had to increment value in 
> > qubes-linux-kernel/rel file and recompile again so my version named as 
> > 4.14.72.2.
> 
> hi friends just update the bios and choose the linux sleep option in the 
> bios, the issue has been fixed

Can confirm. Perform the BIOS update, and enter BIOS configuration at boot:

Config -> Power -> Sleep State -> Linux

I switched xen.cfg default kernel to 4.14.18-1.pvops.qubes.x86_64.

Sleep now works great! Laptop even wakes to XScreenSaver when lid is opened. 

-- 
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/9b063218-082f-483f-b9ee-dc6a0e6ece91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4 are "Starting Start Qubes VM personal" and it does not starts it and either has no time-out!

[Sergio Matta]

I already tried init 2 (too late) init S (too early) and init 1 (root is 
locked).
Does somebody has a way to not start the vm or set a timeout or get dom0 
terminal?
Or any other ideia to login?
Thank you!

-- 
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/92b9a69d-db7b-4d04-a786-eeab30324401%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4.0+ Windows 10

[799]

Hello Black Beard,

Am Mo., 19. Nov. 2018, 10:32 hat Black Beard 
geschrieben:

> [...]
> I'm currently thinking about creating a separate Windows 10 partition
> besides Qubes.
> Is this feasible? Or would one jeopardize his safety in any way?


I am running exactly this configuration as I must run Windows for some
applications (ERP / VMware Workstation ...)

I'm not a security expert, as such I'd like to see someone who is more
skilled adding information if this is not correct:


The problem in a dual boot setup is, that it might be possible to tweak the
unencrypted Boot partition.
The Qubes partition is LUKS encrypted and is therefore more secured.
It could be that an attacker  is able to place "something" in /boot which
will steal the passphrase when you enter it to unlock the LuKS partition.
And it could be possible that the other partitions will be destroyed from
windows, but as you have Backups (do you ;-) , this is acceptable.

I made the decisions that I can live with this risk, still I wanted to try
as reasonable secure as possible which included:

1) having my windows partition Bitlocker encrypted
2) run Coreboot
3) Beeing able to Multiboot and launch windows without entering the
Bitlocker Recovery key

I spent lots (!!) of time getting this accomplished, but it worked.
I can send you my How-to if you are interested.

- O

-- 
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/CAJ3yz2sphWDic9AG8-Vs%3DRX663Ar7oLPf8qNtJ8CUeRJyHU5vQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I remove the GUI when booting qubes

[799]

Hello Pieter,

Am Di., 20. Nov. 2018, 20:20 hat pieter lems 
geschrieben:

> [...]
> I was wondering how i can make it so that when qubes is starting i see the
> boot information (the output of the boot progress,im not sure how i should
> call it). I know that when u press a key it shows the output but i would
> like that it always shows. [...]
>

You can change the default behaviour of the Boot loader:

nano /etc/default/grub

[...]
GRUB_TERMINAL_OUTPUT="console"
[...]
Edit the line which has: GRUB_CMDLINE_LINUX=[...] rhgb quiet"
remove rhgb quiet.

After this you need to write the new configuration to the Boot partition
with:

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

This will show the default messages when booting up.

- O

-- 
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/CAJ3yz2sY%3DXAPogjQ2_yt40nwtL-HdT4ikj4x-zRY02R5N8NxAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - LENOVO X1 Carbon 20BSCTO1WW

[dalecarst]

It took me a few days, but I think the solution I found is simpler.
At least for getting Qubes installed.  I still don't have it booting
from the hard drive, but I can do a rescue boot and proceed from there.

My computer is an H-P compact desktop.  The Qubes install (4.0-rc3 for
x86_64) doesn't like something about either the Intel ethernet or the
Intel i915, so it doesn't automatically try vnc and Xorg fails.
And with text, the disk autopart fails for lack of an encryption
password for the LVM partition.

I let the default (not text) install fail, unable to start Xorg.
I press Alt-Tab until I get the shell window.  I find the network
interface name by running networkctl.  I run dhclient with the
interface name as the sole argument.  I use ifconfig to find the
IP address that DHCP assigned.  I remove /var/run/anaconda.pid.
I run

 anaconda --vnc

On a remote computer behind the same router I start a vnc client and
connect to the Qubes target IP::5901.  I think the client (tightvnc
on Windows 8.1) defaults to port 5900, and the anaconda sets up 5901.

Just do the graphical install on the vnc client and all goes well right
up to the reboot failing to boot from the hard drive, which I consider
to be a separate problem.

On Tuesday, February 10, 2015 at 7:54:29 AM UTC-7, george wrote:
> No graphics available with Qubes kernels which prevents installation due 
> to anaconda issues.  I'm sure the following could be improved and maybe 
> all included in the kickstart file but that wasn't my priority.  I got 
> Qubes installed and working like this:
> 
> Before starting you need the kickstart file and the Fedora kernel rpm on 
> removable media (sdb1 in my case but check your own setup).  Similarly, 
> sda in the kickstart file may not be right for you.  Also check 
> language, keyboard and timezone.
> 
> Some wrinkles I found:
> - Don't change the hostname from "dom0" as it will break things
> - anaconda in text mode demands a user is set up
> - Qubes first-boot also sets up a user, couldn't skip this either
> - With two users strange stuff happened in first-boot
> - That's why I delete a user before doing anything and need root login
> - In one test run I saw nomodeset as a kernel parameter and that caused
>graphics to fail, after finding that I never saw it again
> 
> Boot installation media and hit tab, adding (after "quiet")
> ks=hd:sdb1:/ks.cfg
> 
> Installation should run with no further interaction.
> Once it is complete change to another console (Alt-F2)
> # mount /dev/sdb1 /root
> # cp /root/kernel*.rpm /mnt/sysimage/var/lib/qubes/updates
> # umount /root
> 
> I chose /root as the mount point as it didn't seem to have anything 
> important in it. It worked so I didn't think any further about it.
> 
> Back to console 1 and press the finished key which will reboot.
> Still no graphics, so after boot finishes with a blank screen,
> find a text console to log in on as root.  Then
> 
> # userdel -r deleteme
> # yum install /var/lib/qubes/updates/kernel*.rpm
> # grub2-mkconfig -o /boot/grub2/grub.cfg
> # dracut -f
> # vi /etc/yum.repos.d/qubes-dom0.repo
>add "exclude = kernel" at end of [qubes-dom0-current] section
> # passwd -l root
> 
> Reboot and (hopefully) enjoy.  Don't forget to change the LUKS password, 
> or put a proper one in the kickstart file if you're happy to can erase 
> it safely or keep it secure some other way.
> 
> So far so good for me.  There is a TPM but I haven't got round to 
> testing that yet (and it will be a while).

-- 
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/8cc5e2a6-d0f6-4289-8095-c7b8caa2c1a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes: Unable to connect to VPN

[22rip]

Thanks...I am away from my Qubes but will try! 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 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/84169442-5ee0-4f7b-9148-905ca3e0f1ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes: Unable to connect to VPN

[Otto Kratik]

On Tuesday, November 20, 2018 at 3:56:22 PM UTC-5, 22...@tutamail.com wrote:
> Interesting Otto...can you elaborate on the files you changed? I had this 
> working at one time but then broke...I never managed to get it working.
> 
> What files did you change? The config files?
> 
> Any specifics for a newbie would be appreciated and likely appreciated by 
> others.
> 
> Thanks,
> 22Rip


In my case I had to change the config file supplied by the VPN provider itself, 
which ends with the extension ".ovpn"

In that file, just before the certificate info section which starts with:



-BEGIN CERTIFICATE-


..I had to add the lines:

script-security 2
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf


That change, in combination with the package 'resolvconf' being installed in 
the template that the AppVM is based on (Debian 9, which did not have it 
installed by default), caused the VPN connection to work properly with 
functioning DNS lookup.

-- 
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/bdba428f-3533-4cee-8a3d-67f1f137c0f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: QUESTION - QUBES OS - HARDWARE

[22rip]

Adam,

Here is a list of hardware that has been tried with Qubes, try to pick a 
computer with greens for 4.0(most recent Qubes OS):
https://www.qubes-os.org/hcl/

Not sure you have read this link but this was a note from the list above...its 
close to yours. Not usre of the difference between the GL753VD and your 
GL753VE. 
https://groups.google.com/forum/#!msg/qubes-users/ylHfuhQxmhE/ihkoVxFjBAAJ

Pick your hardware carefully, its important...

-- 
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/dd1635e7-8e76-416c-ba89-f56cac626a3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes: Unable to connect to VPN

[22rip]

Interesting Otto...can you elaborate on the files you changed? I had this 
working at one time but then broke...I never managed to get it working.

What files did you change? The config files?

Any specifics for a newbie would be appreciated and likely appreciated by 
others.

Thanks,
22Rip

-- 
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/0f04d11c-827b-4ebe-b678-90f4218d60f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Change update Template from sys-whonix to sys-whonix-New

[22rip]

Thanks for the response but I did manage to change the "Dom0 UpdateVM" via the 
GUI (System->Global Settings->"Dom0 UpdateVM"), however my understanding is 
this only updates Dom0.

I am trying to change the UpdateVM for all my templates...they are currently 
using the old sys-whonix. I want to change that to sys-whonix-New

-- 
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/ea685a84-2abd-43c1-8ee2-c6ce20aaa9ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I remove the GUI when booting qubes

[Steve Coleman]

On 11/20/18 3:25 PM, pieter lems wrote:
It doesn't seem to work unfortunately, it does display more information 
tho.


Once Xen finishes booting then the OS itself needs to boot, and that 
grub boot entry probably needs the same 'quiet' key word removed. I 
believe this grub file is generated from a script. so there is another 
file that needs to be edited.


look at grub2-mkconfig command for more info

Op di 20 nov. 2018 om 19:32 schreef donoban >:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 11/20/18 8:19 PM, pieter lems wrote:
 > Hello everyone, First of all i would like to start of thanking the
 > Qubes developers. I've been using QubesOS for around a month right
 > now and i cannot wish for more. It's insane how much work you've
 > put into the development of the OS and that you've come so far.
 >
 > I was wondering how i can make it so that when qubes is starting i
 > see the boot information (the output of the boot progress,im not
 > sure how i should call it). I know that when u press a key it shows
 > the output but i would like that it always shows. No offence to the
 > GUI tho!
 >

I think that removing 'quiet' in /boot/efi/EFI/qubes/xen.cfg should
work but maybe you can modify other thing for do not lost the change
when upgrading dom0.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlv0YUgACgkQFBMQ2OPt
CKUyeQ//aH/6q5xpg4Xuu5zXa4sIBDazXLPND7yl25sEha/RW2VwYDUfrfAijcN3
VU+DzVeH2nTByePXXAvz7XNShhYYFnTYo4lEp6GmrHQPaUV7KpGtjT2Egn9k97cA
oyQ90ZowPn0XK7owje8Vi4vV6ZhmVzFi9wlLzX40Dv0grrxOxV5AlrhBavpq+HfJ
Zz8O6k+bmPGqIWP2udBWULFN8+twSOGMCQgAI3mvAWZC/AfMevlooAkcFviawsk3
IpVzRktrriVrNPT1LfJzvhRZVNNq4d9BaFKDPSGO1t9Nts5Srs7MzEBoR1LWVHHG
YoLE6PyE0beUfvHKtyII2M37FSDO+aseQmHk4iPSqg0/TW7P8t5LUZSM/JObSJw2
/YJMfWy7qC/zbDuTkezEE+7rwR1BZp8w9H7Sotm3on4Xzs3B9WXA9VVZfiiiBFt5
f7CTnV0mfMoPiOAX7GqVcc/5YlXD7OSh9Ei0MvHYPAWX3eE23ScY309/T2zqBlD9
DEGQdJ6179roGAWI/HLoy7/BF8iz1o4ahAL0h1s2PkMinYjYfLnvsFDL4aNj/pi0
itKaf+TNQr9JSqpLEWpjWY4w6V2WmqRSmX424cP4TJX6gUuVsWxrPFn8R7uC/aZW
KC9uEbM/qOTJuc+ieNYL2hbC7IlV2CyLghKLMyaxrR92Q5SnIG0=
=gHiN
-END PGP SIGNATURE-

-- 
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/17835bd5-6058-8f77-ba38-312f519a3082%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

--
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/CAK8vAnVEjk0qryoggbn%2BmeFhzmUp4u0i%3DCMw1ajLTLhaxU2hkA%40mail.gmail.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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/b7d08d49-d348-f8db-8048-b163ee0d66b5%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I remove the GUI when booting qubes

[pieter lems]

It doesn't seem to work unfortunately, it does display more information
tho.

Op di 20 nov. 2018 om 19:32 schreef donoban :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 11/20/18 8:19 PM, pieter lems wrote:
> > Hello everyone, First of all i would like to start of thanking the
> > Qubes developers. I've been using QubesOS for around a month right
> > now and i cannot wish for more. It's insane how much work you've
> > put into the development of the OS and that you've come so far.
> >
> > I was wondering how i can make it so that when qubes is starting i
> > see the boot information (the output of the boot progress,im not
> > sure how i should call it). I know that when u press a key it shows
> > the output but i would like that it always shows. No offence to the
> > GUI tho!
> >
>
> I think that removing 'quiet' in /boot/efi/EFI/qubes/xen.cfg should
> work but maybe you can modify other thing for do not lost the change
> when upgrading dom0.
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlv0YUgACgkQFBMQ2OPt
> CKUyeQ//aH/6q5xpg4Xuu5zXa4sIBDazXLPND7yl25sEha/RW2VwYDUfrfAijcN3
> VU+DzVeH2nTByePXXAvz7XNShhYYFnTYo4lEp6GmrHQPaUV7KpGtjT2Egn9k97cA
> oyQ90ZowPn0XK7owje8Vi4vV6ZhmVzFi9wlLzX40Dv0grrxOxV5AlrhBavpq+HfJ
> Zz8O6k+bmPGqIWP2udBWULFN8+twSOGMCQgAI3mvAWZC/AfMevlooAkcFviawsk3
> IpVzRktrriVrNPT1LfJzvhRZVNNq4d9BaFKDPSGO1t9Nts5Srs7MzEBoR1LWVHHG
> YoLE6PyE0beUfvHKtyII2M37FSDO+aseQmHk4iPSqg0/TW7P8t5LUZSM/JObSJw2
> /YJMfWy7qC/zbDuTkezEE+7rwR1BZp8w9H7Sotm3on4Xzs3B9WXA9VVZfiiiBFt5
> f7CTnV0mfMoPiOAX7GqVcc/5YlXD7OSh9Ei0MvHYPAWX3eE23ScY309/T2zqBlD9
> DEGQdJ6179roGAWI/HLoy7/BF8iz1o4ahAL0h1s2PkMinYjYfLnvsFDL4aNj/pi0
> itKaf+TNQr9JSqpLEWpjWY4w6V2WmqRSmX424cP4TJX6gUuVsWxrPFn8R7uC/aZW
> KC9uEbM/qOTJuc+ieNYL2hbC7IlV2CyLghKLMyaxrR92Q5SnIG0=
> =gHiN
> -END PGP SIGNATURE-
>
> --
> 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/17835bd5-6058-8f77-ba38-312f519a3082%40riseup.net
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAK8vAnVEjk0qryoggbn%2BmeFhzmUp4u0i%3DCMw1ajLTLhaxU2hkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I remove the GUI when booting qubes

[pieter lems]

Do you happen to know the reason why i cant cd into the efi directory?
adding sudo does'nt work it stays in the boot directory. :)

Op di 20 nov. 2018 om 19:32 schreef donoban :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 11/20/18 8:19 PM, pieter lems wrote:
> > Hello everyone, First of all i would like to start of thanking the
> > Qubes developers. I've been using QubesOS for around a month right
> > now and i cannot wish for more. It's insane how much work you've
> > put into the development of the OS and that you've come so far.
> >
> > I was wondering how i can make it so that when qubes is starting i
> > see the boot information (the output of the boot progress,im not
> > sure how i should call it). I know that when u press a key it shows
> > the output but i would like that it always shows. No offence to the
> > GUI tho!
> >
>
> I think that removing 'quiet' in /boot/efi/EFI/qubes/xen.cfg should
> work but maybe you can modify other thing for do not lost the change
> when upgrading dom0.
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlv0YUgACgkQFBMQ2OPt
> CKUyeQ//aH/6q5xpg4Xuu5zXa4sIBDazXLPND7yl25sEha/RW2VwYDUfrfAijcN3
> VU+DzVeH2nTByePXXAvz7XNShhYYFnTYo4lEp6GmrHQPaUV7KpGtjT2Egn9k97cA
> oyQ90ZowPn0XK7owje8Vi4vV6ZhmVzFi9wlLzX40Dv0grrxOxV5AlrhBavpq+HfJ
> Zz8O6k+bmPGqIWP2udBWULFN8+twSOGMCQgAI3mvAWZC/AfMevlooAkcFviawsk3
> IpVzRktrriVrNPT1LfJzvhRZVNNq4d9BaFKDPSGO1t9Nts5Srs7MzEBoR1LWVHHG
> YoLE6PyE0beUfvHKtyII2M37FSDO+aseQmHk4iPSqg0/TW7P8t5LUZSM/JObSJw2
> /YJMfWy7qC/zbDuTkezEE+7rwR1BZp8w9H7Sotm3on4Xzs3B9WXA9VVZfiiiBFt5
> f7CTnV0mfMoPiOAX7GqVcc/5YlXD7OSh9Ei0MvHYPAWX3eE23ScY309/T2zqBlD9
> DEGQdJ6179roGAWI/HLoy7/BF8iz1o4ahAL0h1s2PkMinYjYfLnvsFDL4aNj/pi0
> itKaf+TNQr9JSqpLEWpjWY4w6V2WmqRSmX424cP4TJX6gUuVsWxrPFn8R7uC/aZW
> KC9uEbM/qOTJuc+ieNYL2hbC7IlV2CyLghKLMyaxrR92Q5SnIG0=
> =gHiN
> -END PGP SIGNATURE-
>
> --
> 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/17835bd5-6058-8f77-ba38-312f519a3082%40riseup.net
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAK8vAnViJqeyPaiOOEafFggo0nCjF_mL3YAQ65VemVNnS5%2BRXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I remove the GUI when booting qubes

[pieter lems]

thanks for the quick responce.
I'll try it now and get back with the results!
cheers!

Op di 20 nov. 2018 om 19:32 schreef donoban :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 11/20/18 8:19 PM, pieter lems wrote:
> > Hello everyone, First of all i would like to start of thanking the
> > Qubes developers. I've been using QubesOS for around a month right
> > now and i cannot wish for more. It's insane how much work you've
> > put into the development of the OS and that you've come so far.
> >
> > I was wondering how i can make it so that when qubes is starting i
> > see the boot information (the output of the boot progress,im not
> > sure how i should call it). I know that when u press a key it shows
> > the output but i would like that it always shows. No offence to the
> > GUI tho!
> >
>
> I think that removing 'quiet' in /boot/efi/EFI/qubes/xen.cfg should
> work but maybe you can modify other thing for do not lost the change
> when upgrading dom0.
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlv0YUgACgkQFBMQ2OPt
> CKUyeQ//aH/6q5xpg4Xuu5zXa4sIBDazXLPND7yl25sEha/RW2VwYDUfrfAijcN3
> VU+DzVeH2nTByePXXAvz7XNShhYYFnTYo4lEp6GmrHQPaUV7KpGtjT2Egn9k97cA
> oyQ90ZowPn0XK7owje8Vi4vV6ZhmVzFi9wlLzX40Dv0grrxOxV5AlrhBavpq+HfJ
> Zz8O6k+bmPGqIWP2udBWULFN8+twSOGMCQgAI3mvAWZC/AfMevlooAkcFviawsk3
> IpVzRktrriVrNPT1LfJzvhRZVNNq4d9BaFKDPSGO1t9Nts5Srs7MzEBoR1LWVHHG
> YoLE6PyE0beUfvHKtyII2M37FSDO+aseQmHk4iPSqg0/TW7P8t5LUZSM/JObSJw2
> /YJMfWy7qC/zbDuTkezEE+7rwR1BZp8w9H7Sotm3on4Xzs3B9WXA9VVZfiiiBFt5
> f7CTnV0mfMoPiOAX7GqVcc/5YlXD7OSh9Ei0MvHYPAWX3eE23ScY309/T2zqBlD9
> DEGQdJ6179roGAWI/HLoy7/BF8iz1o4ahAL0h1s2PkMinYjYfLnvsFDL4aNj/pi0
> itKaf+TNQr9JSqpLEWpjWY4w6V2WmqRSmX424cP4TJX6gUuVsWxrPFn8R7uC/aZW
> KC9uEbM/qOTJuc+ieNYL2hbC7IlV2CyLghKLMyaxrR92Q5SnIG0=
> =gHiN
> -END PGP SIGNATURE-
>
> --
> 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/17835bd5-6058-8f77-ba38-312f519a3082%40riseup.net
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAK8vAnWEApyeTVgCvSAuX-%3DL4x7nHHewzc5d-rP9XyTnnUfc1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes: Unable to connect to VPN

[Otto Kratik]

Further update: I decided to try a completely different VPN provider's config 
file, and to my surprise that one worked fine using the old simple method of 
calling openvpn from the AppVM.

Examining both files and looking for the difference between the two, it appears 
the broken one did not ever invoke resolvconf include the following lines:

script-security 2
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf


Adding those lines to the non-functioning file and running it resulted in 
success.

-- 
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/930b5080-4ba8-428f-bcf6-0eeaa1411c4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Custom dom0 wallpaper (a kind of guide)

[pieter lems]

Hello everyone,
Today I was customizing my QubesOS and I was running into a few problems
trying to change the dom0 wallpaper. I got it to work eventually and I
wanted to share how I did it. It's not safe to copy any files to dom0 but i
found that it's necessary to be able to use a custom wallpaper. (I'm sorry
if this is not the case). I did find a way to do this in a "sort of" secure
way, removing possible malware embedded in the image.

- First find an image you like to use as a wallpaper and download it.
- Open it using a disposable vm.
- Select full screen in the image viewer and take a screenshot.
- Save the screenshot in dom0
- Copy the screenshot to a trusted VM by using the command :

qvm-copy-to-vm  

- Open the image in an image editor and cut the top border
- Save the image and copy it back to the backgrounds folder in dom0 by
using the command:

qvm-run --pass-io  'cat /path/to/file_in_src_domain' | sudo
tee /usr/share/backgrounds


And voila the wallpaper is in dom0. You can change it by right
clicking on your desktop and selecting desktop settings and then point
the folder to backgrounds

Again sorry if this is not the correct way.

cheers!

-- 
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/CAK8vAnXh8OF6Yg6HPRn8Gpfnt%3DH7i03%3DVVWi%3DpL3sJ5MRhkSLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I remove the GUI when booting qubes

[donoban]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 11/20/18 8:19 PM, pieter lems wrote:
> Hello everyone, First of all i would like to start of thanking the
> Qubes developers. I've been using QubesOS for around a month right
> now and i cannot wish for more. It's insane how much work you've
> put into the development of the OS and that you've come so far.
> 
> I was wondering how i can make it so that when qubes is starting i
> see the boot information (the output of the boot progress,im not
> sure how i should call it). I know that when u press a key it shows
> the output but i would like that it always shows. No offence to the
> GUI tho!
> 

I think that removing 'quiet' in /boot/efi/EFI/qubes/xen.cfg should
work but maybe you can modify other thing for do not lost the change
when upgrading dom0.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlv0YUgACgkQFBMQ2OPt
CKUyeQ//aH/6q5xpg4Xuu5zXa4sIBDazXLPND7yl25sEha/RW2VwYDUfrfAijcN3
VU+DzVeH2nTByePXXAvz7XNShhYYFnTYo4lEp6GmrHQPaUV7KpGtjT2Egn9k97cA
oyQ90ZowPn0XK7owje8Vi4vV6ZhmVzFi9wlLzX40Dv0grrxOxV5AlrhBavpq+HfJ
Zz8O6k+bmPGqIWP2udBWULFN8+twSOGMCQgAI3mvAWZC/AfMevlooAkcFviawsk3
IpVzRktrriVrNPT1LfJzvhRZVNNq4d9BaFKDPSGO1t9Nts5Srs7MzEBoR1LWVHHG
YoLE6PyE0beUfvHKtyII2M37FSDO+aseQmHk4iPSqg0/TW7P8t5LUZSM/JObSJw2
/YJMfWy7qC/zbDuTkezEE+7rwR1BZp8w9H7Sotm3on4Xzs3B9WXA9VVZfiiiBFt5
f7CTnV0mfMoPiOAX7GqVcc/5YlXD7OSh9Ei0MvHYPAWX3eE23ScY309/T2zqBlD9
DEGQdJ6179roGAWI/HLoy7/BF8iz1o4ahAL0h1s2PkMinYjYfLnvsFDL4aNj/pi0
itKaf+TNQr9JSqpLEWpjWY4w6V2WmqRSmX424cP4TJX6gUuVsWxrPFn8R7uC/aZW
KC9uEbM/qOTJuc+ieNYL2hbC7IlV2CyLghKLMyaxrR92Q5SnIG0=
=gHiN
-END PGP SIGNATURE-

-- 
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/17835bd5-6058-8f77-ba38-312f519a3082%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Problems of Installation on macOS 10.14 Mojave

[Koma Kurt]

Hi there, they told me to send my question to this mailing list ..hope you can 
help me guys;-)

Hi there im new to Qubes OS and i want to install it on external ssd...
rEFInd 0.11.4 is already installed and macOS is updated to macOS 10.14 Mojave.
Wanna install it on MacBook Pro (Retina 13 Zoll, Anfang 2015).
I downloaded Qubes-R4.0.1-rc1-x86_64 ISO and dd ed it on a boot stick..

Now reboot my macbook...
there are now 3 options to boot from:
-->legacy mode (doesnt work)
-->vmlinuz (doesnt work -->freeze install progress @ dracut..with 4 penguins
-->fallback...it works installer starts but then where i have to choose 
language ..i cant choose cause the keyboard and trackpad are frozen :-/
the xen.efi is also missing or broken...

@eduncan911 
you write above Apple hardware has been fixed: 
QubesOS/qubes-installer-qubes-os#20 
 ...
can you please tell me (step-by-step)

for what is the qubes-installer-qubes-os used for (to build iso?)
how to Compile/ build / use qubes-installer-qubes-os ??
i couldnt figure out how to use this repo cause there is no README file ??
Do i have to make it like the qubes builder? does it output an ISO ?
@marmarek 
is there a way how i could build my own iso with all the fixes inside which 
works on my macbook?
i read in the issues that the problems where fixed but i didnt know how to fix 
it ..
could you please so kind to give me step-by-step instructions on which files i 
have to change before building the iso? can i build the iso in debian or only 
Fedora?

You are my last chance how to get answers ...i crawled the whole Internet to 
find some useful tipps and read every page of the documentation of cause 
macbook troubleshooting but with no success:-(
Could anyone add a README file to QubesOS/qubes-installer-qubes-os ...it wont 
only useful for me ..i think it would be great for everybody whos new to Qubes 
OS

Thanks so much for your help!!

-- 
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/1D7AC1A6-47ED-4584-B7FF-1D4858303D49%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] How can I remove the GUI when booting qubes

[pieter lems]

Hello everyone,
First of all i would like to start of thanking the Qubes developers. I've
been using QubesOS for around a month right now and i cannot wish for more.
It's insane how much work you've put into the development of the OS and
that you've come so far.

I was wondering how i can make it so that when qubes is starting i see the
boot information (the output of the boot progress,im not sure how i should
call it). I know that when u press a key it shows the output but i would
like that it always shows. No offence to the GUI tho!

Thanks in advance,
Cheers!

-- 
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/CAK8vAnVZfV5THRMQV0JsH%2BwNm1SBUdZq2TPKiSLmmqMaSB%3D%3Dwg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes: Unable to connect to VPN

[Otto Kratik]

On Monday, November 19, 2018 at 3:55:19 PM UTC-5, Chris Laprise wrote:
> Qubes 4 networking is re-written and functions somewhat differently than 
> Qubes 3.x.


So it seems. After spending several days trying to get a VPN connection up and 
working via every possible method conceivable, I have been met with complete 
and utter failure and have finally given up.

The results are always the same. Whether I connect manually with Openvpn, use 
qubes-vpn-support, qubes-tunnel, try from an AppVM, NetVM, ProxyVM, edit 
/etc/resolv.conf or any number of other files or scripts, it makes no 
difference. The VPN output reports successful connection (Initialization 
sequence completed) and I can ping any numerical IP address I specify without 
issue. But DNS resolution does not work, and nothing I try fixes it.

Booting up Qubes 3.2, the same VPN connection works flawlessly and DNS is 
trouble-free. So I've decided to solve my problem in the simplest (and only) 
way available: by going back to Qubes 3.2.

I appreciate all your attempts to help me with this. Thank you.

-- 
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/81b7d62b-f4ca-45b1-9745-1030ebbd6530%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Q4.0 qvm-prefs kernel property vs the installed/latest kernel

[Steve Coleman]

I have two up to date fedora-26 templates, that have long since been 
upgraded to fc28, that are both apparently 'stuck' at kernel version 
4.14.74-1. I apparently can not set either template to a newer kernel. 
There are a lot of customizations involved so I am hoping not to have to 
go back to the fc28 rpm and start all over.


Both methods of inspection show the old kernel:

QubeManager /QubeSettings/advanced/kernel/

qvm-prefs --get  kernel

The current/latest installed fc28 kernel version appears to be 
4.18.18-200, yet this latest kernel does not even show up under the 
QubeManager settings, nor qvm-prefs, and absolutely refuses to 
set/update this 'kernel' key to this latest kernel version number.


The qvm-prefs utility simply claims that this newer kernel version is 
not installed, yet "rpm-qa | grep 4.18.18-200" clearly shows that it is. 
In fact rpm says that the older kernel 4.14.74-1 is *not* installed. If 
so, then how is this template even running? I'm using it daily!


I know dnf can block a package from upgrading, but that is clearly not 
what is happening here. The packages do update but apparently Qubes is 
just not seeing them, as to be able to display any in Qube-Manager or 
set/use them using qvm-prefs.


The "Qubes Global Settings" shows the default kernel as 4.14.74-1, and I 
can't even change that, because the newer kernels are not listed there 
either.


A file system scan for the old version number yields /usr/lib/modules/* 
directory that shows up with 4.14.74-1 as an *fc26* module rather than a 
fc28 module, so this whole version disparity appears to be due to some 
kind of botched fc26 --> fc28 system/module check routine during a past 
upgrade? At least that I my best guess at the moment of what broke and 
when.


In fact /usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build/
is the only *build directory* where as all the newer kernels this is 
merely a symlink into /usr/src/kernels/*/


Is there anywhere that I would find a Qubes "version setting" that 
switches from fc26 modules to fc28 modules? Or is it just somehow 
scanning for this "build" directory and then ignoring the newer symlinks?


Any clues of what this should be doing might be very helpful about now.

thanks,

Steve

--
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/f37dec5e-f9cf-3a23-a5ed-f4cfe2ac7053%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Reinstall Qubes-Whonix TemplateVMs documentation revamped

[Patrick Schleizer]

https://www.whonix.org/wiki/Qubes/Reinstall

-- 
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/848894e9-5e3b-b4cb-327b-0e741aa0caf5%40whonix.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] TOR browser updates.

[Patrick Schleizer]

William Fisher:
> How do I update the TOR browsers at the Template VM level? I've updated TOR 
> at the APP level but it doesn't stay updated.
> 

New documentation page just now created focusing only on updating Tor
Browser in Qubes-Whonix:

https://www.whonix.org/wiki/Qubes/Tor_Browser

-- 
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/e2149b99-9d5d-0ea0-be41-c8cd3388d135%40whonix.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: TOR browser updates.

[brendan . hoar]

On Tuesday, November 20, 2018 at 1:29:04 AM UTC-5, Антон Чехов wrote:
> On Tuesday, November 20, 2018 at 3:39:24 AM UTC+1, William Fisher wrote:
> > How do I update the TOR browsers at the Template VM level? I've updated TOR 
> > at the APP level but it doesn't stay updated.
> 
> I updated my template-vm (whonix-gw-14, whonix-ws-14 and sys-whonix) this 
> week via console (sudo apt-get update && sudo apt-get dist-upgrade) and the 
> latest TOR browser was downloaded. 

I currently avoid dist-upgrade and stick with upgrade. But YMMV.

With that said, it's important to keep cloned copies of all your templates a 
few update versions back...just in case. Can be difficult to recover a botched 
upgrade once sys-net won't work any more. :) 

> I started a disposable whonix-vm and checked (help -> about tor browser) the 
> version and it was 8.0.3 which should be the latest.
> Starting anon-whonix-vm was not updated (8.0) but tor-browser did download 
> the latest version upon opening it (help -> about tor browser) and it stays 
> updated.

The explanation for the different behaviors is that, unlike most software in 
the templates, TB is stored in the private volume (in ~/.tb). When updated in 
the template, the template's private volume receives the new TB version.

- DVMs are always started with a temporary copy of the parent template's 
current private volume. Hence the DVM automatically used the apt-get upgraded 
~/.tb dir from the template.

- AppVMs keep their own separate (non-updating) private volume after being 
created, so they do not inherit the template's update to ~/.tb. However once 
you update TB in the AppVM, since it resides in the private volume, it will 
remain updated after AppVM restarts.

Brendan

-- 
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/206c48db-c95f-48ef-a724-b1ab91bff6db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Help setting up internet connection via wireless netgear internet adapter without internet

[Ivan Mitev]

On 11/20/18 2:12 AM, 'Ryan Carter' via qubes-users wrote:


Hi I am having troubles setting up a internet connection via a wireless netgear 
internet adapter.
Some problems I encountered:
- I believe that I have to install installation disc software via a cd/rom 
drive just like setting up on any other OS without a prior internet connection
- So I tried attaching the cd/rom to sys-net vm by clicking yellow device 
button in top right corner and it was successful although when I went into the 
sys-net vm devices to add it it wasn’t there. I also tried doing it manually 
via the terminal but had no such luck maybe I did something wrong there not 
sure though.
- Also I tried inserting the wireless adapter w/o the installation disc first 
and it’s not registering at all on devices, but I assume that is b/c the 
software for it hasn’t been downloaded via cd hence my problem


You shouldn't have to install third-party drivers, the linux kernel 
usually supports mainstream hardware out of the box. There are 
exceptions though - fancy printers/scanners, exotic hardware, closed 
hardware difficult to reverse-engineer, and/or hardware that is too new 
for support to have reached the stable kernels used in Qubes, ...
By the way installing vendor drivers is quite a painful and time 
consuming process.


What is your wireless adapter based on ? USB ? PCIe ? If you have 
another computer with a "standard" linux distribution installed - eg. 
debian, fedora, ubuntu, ... - did you try your adapter there ?


If your adapter is a PCIe card, did you assign it to sys-net ? Do you 
see anything relevant in `sudo dmesg` in sys-net ?


Otherwise, assuming it's a USB device, is it shown when typing `lsusb` 
in sys-usb (assuming you have such vm) ? Ditto for `sudo dmesg` ?


Or maybe your adapter is supported but you simply didn't configure your 
VM(s) to use it - eg.:


1- attach the device from sys-usb to sys-net (not guaranteed to work - 
usb pass-through is usually a hit or miss)


2- or, attach the relevant usb controller(s) to sys-net (and ditch 
sys-usb if it doesn't have controllers assigned to it anymore).


3- or, setting up NetworkManager in sys-usb and defining 'sys-usb' as 
sys-firewall's netvm (which basically ends up being identical to 2- above).


(note: I don't have a usb network adapter to test so the above is what I 
imagine is needed given my knowledge of qubes. Others may chime in...).


The following may also help: https://www.qubes-os.org/doc/usb/

Ivan

--
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/ab405d5f-fc3f-b4ac-e3fc-c09b6b5a20b8%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Change update Template from sys-whonix to sys-whonix-New

[aaq via qubes-users]

mandag den 19. november 2018 kl. 16.55.42 UTC+1 skrev 22...@tutamail.com:
> I recreated a new Appvm for my templates to use for updates. I currently use 
> sys-whonix...the new template is sys-whonix-New.
> 
> 
> How would I do this?

Hey there!

I am not currently on my Qubes box, but I guess you can change it in the Qubes 
Global Settings program (if you want GUI). I am pretty sure you can set the 
dom0 update VM in there.

Otherwise you can also do it with qvm-prefs, I just don't have enough 
experience using it to set stuff on dom0.

Hope this helps.

-- 
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/14f925a0-a2dc-4731-bc94-c4ca78f585a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.