Re: [qubes-users] Re: Fedora 26 and Debian 8 approaching EOL

[Ivan Mitev]

On 05/24/2018 04:28 AM, Andrew David Wong wrote:

> Update: Fedora 28 is also available.
> 
> Instructions for upgrading from Fedora 27 to 28:
> 
> https://www.qubes-os.org/doc/template/fedora/upgrade-27-to-28/
> 
> (As stated in the document, these instructions should also work for
> upgrading from Fedora 26 to 28.)
> 
> Instructions for installing a fresh Fedora 28 TemplateVM:
> 
> https://www.qubes-os.org/doc/templates/fedora/#installing

FWIW when upgrading my custom fedora templates from 26 to 28 I got an
error with the qubes-core-agent-networking and qubes-core-agent-qrexec
packages: the "preun" rpm script of the old f26 rpm fails ("fg: no job
control"), and both version end up being installed, as shown by:

$ rpm -q qubes-core-agent-networking qubes-core-agent-qrexec

qubes-core-agent-networking-4.0.28-1.fc26.x86_64
qubes-core-agent-networking-4.0.28-1.fc28.x86_64
qubes-core-agent-qrexec-4.0.28-1.fc26.x86_64
qubes-core-agent-qrexec-4.0.28-1.fc28.x86_64

I've fixed this with:

$ rpm -e --noscripts qubes-core-agent-networking-4.0.28-1.fc26.x86_64 \
 qubes-core-agent-qrexec-4.0.28-1.fc26.x86_64

and re-installing the f28 versions (maybe not needed but can't hurt):

$ sudo dnf reinstall qubes-core-agent-networking qubes-core-agent-qrexec




-- 
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/057396f4-ddaf-9a2a-0558-348db54ed3d3%40maa.bz.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: Is my Qubes system corrupted or is this just a bug?

[cooloutac]

On Wednesday, May 23, 2018 at 11:37:39 AM UTC-4, Mindus Amitiel Debsin wrote:
> I've been having problems with the Qube Manager since I got Qubes installed, 
> and this most recent error makes me truly believe that there is something 
> wrong.
> 
> So I had Debian-9 templateVM running and I right clicked on it in Qube 
> Manager and told it to shut down. [I wanted to clone the Debian-9 so I had a 
> workspace that had exfat support] Then after about 30 seconds, it was still 
> up, so I right clicked on it and said "Kill Qube."
> 
> And the response I got was this: (Sorry I couldn't screenshot it).
> ===
> 
> [Dom0] Houston, We have a problem...
> Whoops. A critical error has occured. This is most likely a bug in Qubes 
> Manager.
> 
> Assertion Error: 
> at line 830
> of file /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py
> 
> 
> ===
> 
> I had been trying to get a Windows 10 Qube installed so I can learn Qube 
> while also getting some stuff done in my primary OS. I have read a very 
> interesting post here that encouraged me: 
> https://groups.google.com/d/topic/qubes-users/dB_OU87dJWA
> But sadly my attempts to even get a Win 10 installation started have resulted 
> in complete failure. I have 2 Windows 10 install methods: by USB drive, and 
> by .iso file. Neither have worked at all in the Qube I have created for it.  
> Obviously I was using the Debian qube from before because it supports exfat.
> 
> ===
> 
> When I start Qubes from boot, I get this message:
> "[FAILED] Failed to start Load Kernal Modules.
> See 'systemctl status systemd-modules-load.service' for details"
> 
> and then it goes into 
> "Starting apply Kernal Variables..."
> And it has a bunch of [OK]s in the boot.
> 
> ===
> Since I believed that my qubes system might be corrupted, I did a "shutdown 
> -Fr" in dom0 terminal, but it didn't seem to have any effect other than an 
> ordinary shutdown.
> 
> 
> So my questions:
> 
> 1) How do I confirm that my Qubes system is fully functioning? Like maybe an 
> SFC for Qubes?
> 2) With the error with the Qubes manager, how do I fix that or upgrade to a 
> newer version?
> 3) Are there any step-by-step install instructions for an HVM Windows 10 
> Qubes install?
> 
> Thanks for reading. Maybe I will come up with more questions later. Sorry I 
> don't know Qubes or Linux very well. I've been going through the 
> documentation and have even used terminal commands instead of just GUI, but 
> it is still a learning experience.
> 
> ~Mindus

yes as above poster said, after every action you need to manually refresh the 
qubes manager by clicking the green recycle icon. The qubes manager is still 
showing it as running but it is already shut down thats probably why you are 
getting that error message.

A more reliable way to see running qubes with mouse is by using the widget in 
taskbar.

I also personally like to keep qubes-manager organized by the state column.

 

-- 
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/07c059ed-3cd4-46dc-b60c-183901eb8a75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Fedora 26 and Debian 8 approaching EOL

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-05-24 04:18, Holger Levsen wrote:
> On Wed, May 23, 2018 at 08:21:12PM -0500, Andrew David Wong wrote:
>> Fedora 26 will reach EOL ([end-of-life]) on 2018-06-01, and Debian 8
>> (["Jessie" full, not LTS][debian-releases]) will reach EOL on
>> 2018-06-06. We strongly recommend that all Qubes users upgrade their
>> Fedora 26 and Debian 8 TemplateVMs and StandaloneVMs to Fedora 27 and
>> Debian 9 or higher, respectively, by these EOL dates. 
> 
> I'm not sure why you suggest^wstrongly recommend to upgrade from Debian
> 8 to 9. "Suggest" I would understand, but Debian 8 will be supported for
> another 2 years via LTS.
>  

Thank you for the correction. I've updated the announcement on the
website to clarify this:

https://github.com/QubesOS/qubes-posts/commit/3db9a35e297b3defa0863f8ab02ebd56e8384053

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlsHWNgACgkQ203TvDlQ
MDAZXg//fkL6JAbGPlKL+qrwnydn5HHV9HCGvvwPvB7fNLRrL4e4xO8L57/jHCZ0
++8t0f6bjVN5qxNDm1eMKWJLqSxKfeMBE/ANMJKvUkgNqDnfoSekikCY8YQNVuG3
HIQ6ZyH5UCw/TQxyhmyPF1F154Egy/hQ+XY8owhJ+3/YO4STRJhQT+UaWo1/dI6P
gTF+iSb/xvX7vjNvLX/BqKw/zUyfq1fciHEI9S/a9eG4WiBipQR694LrdWz7d+Lz
4jrX60FjQL1Gr2Vn4hDHhncsNnYXziJ4AHYEkH3CSJ96U30RSAeoT/mgRhj6+dXt
QbopJ8w0qfoS2p9MnNsEJVPj8QrxkpP/Vy46e/a1qWLUTScjsfztC9AAh4wRD0ge
Afpwv10C5i/sTBN96xDylBKn5H0gKDHHv0tTnyx9EDdYV0+Cdve7jf4ILlLcY51C
jI4rc9aY3rwXcp6LjTHnwdwjSvowMwmF5hxttjCISbSdu7l66X60LuD2D9SE4x8M
1L1QXymdXduo555bprkf7nOlTTEp+53z1lA8rYg4akxKGDFq9m6YglmXX6Vxbz+w
/nxZIDu/aigWgRJcEPJhjvIXqaxVG6S2fSFAf64XbYj5k4Sz01yu/MOJJ6p40joG
NJQBN25kl2lXrcsgGRhJYO3+CMAIr01OP1YLxhFIYbsCybtSiZw=
=0xJE
-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/3eb34268-2eb0-4097-e867-843c60fe9d7e%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] QSB #40: Information leaks due to processor speculative store bypass (XSA-263)

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Qubes Community,

We have just published Qubes Security Bulletin (QSB) #40: Information
leaks due to processor speculative store bypass (XSA-263). 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 #40 in the qubes-secpack:

https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-040-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-263 in the XSA Tracker:

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

```
 ---===[ Qubes Security Bulletin #40 ]===---

 2018-05-24


  Information leaks due to processor speculative store bypass (XSA-263)

Summary


On 2018-05-21, the Xen Security Team published Xen Security Advisory
263 (CVE-2018-3639 / XSA-263) [1] with the following description:

| Contemporary high performance processors may use a technique commonly
| known as Memory Disambiguation, whereby speculative execution may
| proceed past unresolved stores.  This opens a speculative sidechannel
| in which loads from an address which have had a recent store can
| observe and operate on the older, stale, value.

Please note that this issue was neither predisclosed nor embargoed.
Consequently, the Qubes Security Team has not had time to analyze it in
advance of issuing this bulletin.

Impact
===

According to XSA-263, the impact of this issue is as follows:

| An attacker who can locate or create a suitable code gadget in a
| different privilege context may be able to infer the content of
| arbitrary memory accessible to that other privilege context.
| | At the time of writing, there are no known vulnerable gadgets in the
| compiled hypervisor code.  Xen has no interfaces which allow JIT code
| to be provided.  Therefore we believe that the hypervisor itself is
| not vulnerable.  Additionally, we do not think there is a viable
| information leak by one Xen guest against another non-cooperating
| guest.
| | However, in most configurations, within-guest information leak is
| possible.  Mitigation for this generally depends on guest changes
| (for which you must consult your OS vendor) *and* on hypervisor
| support, provided in this advisory.

In light of this, XSA-263 appears to be less severe than the related
Spectre and Meltdown vulnerabilities we discussed in QSB #37 [2].

Patching
=

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

  For Qubes 3.2:
  - Xen packages, version 4.6.6-41

  For Qubes 4.0:
  - Xen packages, version 4.8.3-8

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.

In addition, Intel Corporation has announced that microcode updates
will be available soon [3]:

| Variant 3a is mitigated in the same processor microcode updates as
| Variant 4, and Intel has released these updates in beta form to OEM
| system manufacturers and system software vendors. They are being
| readied for production release, and will be delivered to consumers
| and IT Professionals in the coming weeks.

This bulletin will be updated once the Intel microcode updates are
available. No microcode update is necessary for AMD processors.

Credits


See the original Xen Security Advisory.

References
===

[1] https://xenbits.xen.org/xsa/advisory-263.html
[2] https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-037-2018.txt
[3] 
https://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.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/05/24/qsb-40/

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlsHTIcACgkQ203TvDlQ
MDCoHw//dx+GcN8QIz0ww1tUQZufTaDwSy0eiY+Ul3PFX5CVnhzmXk6r4iRSkYVU
lxSitio+STe2WHnpS6dVQhRcR+RCBu5A07MPvzq9tv/tMw8nkRx5GnE54so9oVjB
wv26jkMdo7XreZuih3MEjacsvgL9hogpTAzuxelpU3Ve9/J3GhiNbqgscx+Dop4n
hloKnKmwKbJOgyZcxH/Px5nnDLpICR5Z5gTZDKQPvzXaPVRbQ8cS/WPLdbqxnAH8

[qubes-users] Deleting Disposable VMs / Qubes Docs / Warning

[ponyboy]

Hi.
Just a little warning:
The typing error
[user@dom0 ~]$ QUBES[instead of qvm]-prefs  default_disp ""
in the section »Deleting Disposable VM« on 
https://www.qubes-os.org/doc/dispvm-customization 

can cost you hours of research –if you are as blind and stupid as me. 
Ahoy,PB

-- 
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/LDJHlUH--3-0%40keemail.me.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0 / Updated to Fedora 27 / Networking

[ponyboy]

Hello all.
Just a little hint:Using tasket's brilliant Qubes-vpn-support(easy to searx and 
find),I had to update/reinstall it in order to see thebeloved box »Link is up!« 
again.
#Qubes-4.0  #updating  #templates  #appvms  #Fedora-26-to-27
Cheers,Pony Boy

-- 
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/LDJFyT6--3-0%40keemail.me.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Dell XPS 13 (9360)

['Satnam Ram' via qubes-users]

I just installed the latest Qubes R4.0 on my XPS 13 FHD-Model (9360). It
required some minor tweaking.

1. Preparation

- update your BIOS
Version: 2.6.2   Release Date: 22 Mar 2018
- replace killer wifi with an Intel 8265 card
- apply Thunderbolt 3 Firmware Update (don't know if this was required)
- apply adaptive brightness display firmware update (only if you want/need
it)

2. BIOS Settings

- change SATA Operation from "RAID On" to "AHCI"
- disable secure boot
- disable EFI (the first time the Installer froze while installing the
Whonix template)
- disable Intel SpeedStep (!!!)
If you don't the OS will run a lot slower if you start the device
unplugged no matter if you
plug it in later. I can confirm the "happy" and "unhappy" states
described here:
https://groups.google.com/forum/#!topic/qubes-users/9Hqyepkp8XM
Booting on battery was about 1min25s for me while booting with AC gave
me 55s. After turning
it off I get about 55s in both situations which is fine.

3. Qubes
- enable trackpad features
add the Option entries to your
/usr/share/X11/xorg.conf.d/60-libinput.conf touchpad section

Section "InputClass"
Identifier "libinput touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "libinput"
  ->Option "Tapping" "True"
  ->Option "PalmDetection" "True"
  ->Option "TappingDragLock" "True"
EndSection

---

Update:

I use Qubes for about a week now - primarily for go development with
Goland, browsing and watching videos. Everything I used worked very well.
The battery life is good. Video playback and similar things (using software
rendering) heat up the CPU and drain considerably more power (my estimated
remaining time is usually halfed). Booting takes about 1 minute (starting
net, firewall and whonix qubes). Suspend to RAM works most of the time -
once in a while the screen stays black after resume - this is the only bug
I encountered so far but its negligible. I managed to install Kali 2018.1
after I set the system volume size to 30GB (default setting caused the kali
installer to fail). I was able to expose my Intel 8265 directly to the kali
hvm and put it into monitoring mode. Rising initial memory to 1GB lowers
boot time for most VMs, setting a high VCPU count for VMs where you cannot
afford lag helped transitioning from bare metal. I installed Steam and
Factorio in a another VM and I was able to play with minor glitches
(v-sync) and major cpu heat.

not tested:
- USB-C
- Webcam
- Mic (but its recognized)

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


Qubes-HCL-Dell_Inc_-XPS_13_9360-20180524-210753.yml
Description: application/yaml

[qubes-users] Re: Fedora-27 Template Issues, Qubes 3.2

[Sergio Matta]

Em quinta-feira, 24 de maio de 2018 16:31:22 UTC-3, Stuart Perkins  escreveu:
> Now that the Fedora 27 template is available, I downloaded and installed it 
> without issue.  Modifying sys-net and sys-firewall to use it fails miserably 
> though..no network connectivity.  Anybody else get this?
> 
> Qubes OS 3.2, Thinkpad T520...
> 
> Stuart

Sorry to ask but, did you updated it before use?

-- 
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/5ca0a89f-b8c0-4b0a-91bc-f5b1ba1e95d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] AEM boot = GPU hang, no graphics display

[tasket]

On 24.05.2018 04:12, awokd wrote:

Not sure if it's related or why AEM would have modified it, but try
changing that i915 option to i915.alpha_support=1 (like
https://www.qubes-os.org/doc/intel-igfx-troubleshooting/#software-rendering-or-video-lags).


As noted on qubes-issues, I had to remove "iommu=no-igfx" from Xen 
options to get graphics working.


Another side-effect that AEM/tboot has, unfortunately, is that 
sleep/suspend no longer works (now it causes an unintended reboot when 
entering sleep). But its been a long time since this combination worked.


Chris

--
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/97d31bc76ff997cbe3722cad70d1b089%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Fedora-27 Template Issues, Qubes 3.2

[Stuart Perkins]

Now that the Fedora 27 template is available, I downloaded and installed it 
without issue.  Modifying sys-net and sys-firewall to use it fails miserably 
though..no network connectivity.  Anybody else get this?

Qubes OS 3.2, Thinkpad T520...

Stuart

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

[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0

[beastgoalie]

I want to try adapting the grub instructions to EFI and patching tables that 
way, but won't have a laptop I can use in place of my current one until late 
june/early july. I'll report back then on what works if 4.15 isn't already 
solving the problem. Thank you for trying this though.

-- 
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/8b43024d-6637-44e4-9731-ad0795840b8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Curl error (6) by updating dom0

[awokd]

On Thu, May 24, 2018 4:24 pm, evo wrote:
>
>
> On 05/24/18 14:33, awokd wrote:

>>
>> See the instructions at the top of
>> https://www.qubes-os.org/doc/installation-guide/.
>>
>>
>
>
> thanks!
> i changed the 4 links to https.
>
> ...but now i get curl error (3) on several links
> "ULR using bad/illegal format or missing URL for ..."
> und am Ende "... http' contains bad letter"

You edited /etc/yum.repos.d/qubes-dom0.repo, right? And made the line
under [qubes-dom0-current] look something like:

baseurl = https://yum.qubes-os.org/r$releasever/current/dom0/fc25


-- 
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/fbd3623206e9f64938eea106c631cdbe%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Curl error (6) by updating dom0

[evo]

On 05/24/18 14:33, awokd wrote:
> On Thu, May 24, 2018 11:34 am, evo wrote:
>> Hi,
>>
>> now i get Qubes 4.0 working... but by updating dom0 i get much errors.
>>
>> curl error (6): couldn't resolve host name for ...
>>
>> there are many of the mirrors which follows then.
>>
>> it's a very fresh install of the qubes 4.0, so i did not do anything on
>> the system, but to set the network on manual connection with the router.
>>
>> the strange thing is, that other mirrors work, so dom0 could
>> install/upgrade 46 packages.. but not the mentioned with the error.
> 
> See the instructions at the top of
> https://www.qubes-os.org/doc/installation-guide/.
> 
> 


thanks!
i changed the 4 links to https.

...but now i get curl error (3) on several links
"ULR using bad/illegal format or missing URL for ..."
und am Ende "... http' contains bad letter"

-- 
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/4b8bf796-0ff2-a3ab-3054-fe76fd47c0fb%40aliaks.de.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] ~/.gnupg/gpg.conf doesnt exist in vault-safe VM, even pgp keys were generated there

[qubes-fan]

Hi, I am using split gpg. vault-safe VM is a no-net VM with master secret keys, 
work is the VM to communicate the gpg actions to the world. 

I generated 2 sets of keys in the vault-safe VM. It is working well also with 
the work VM through qubes-gpg-client. 
I wanted now to adjust the ~/.gnupg/gpg.conf in the vault-safe VM, but the file 
~/.gnupg/gpg.conf doesnt exist there. In the work VM, the ~/.gnupg/gpg.conf 
exists. Am I missing something? 

-- 
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/LDHUdOM--3-0%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Curl error (6) by updating dom0

[awokd]

On Thu, May 24, 2018 11:34 am, evo wrote:
> Hi,
>
> now i get Qubes 4.0 working... but by updating dom0 i get much errors.
>
> curl error (6): couldn't resolve host name for ...
>
> there are many of the mirrors which follows then.
>
> it's a very fresh install of the qubes 4.0, so i did not do anything on
> the system, but to set the network on manual connection with the router.
>
> the strange thing is, that other mirrors work, so dom0 could
> install/upgrade 46 packages.. but not the mentioned with the error.

See the instructions at the top of
https://www.qubes-os.org/doc/installation-guide/.


-- 
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/364ab582720c6bef96ac367f3877f7d6%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: whonixdvm isn't using updated torbrowser

[awokd]

On Thu, May 24, 2018 4:11 am, john wrote:

>
>
> ...guess I can try again later ;  presently  I am also  getting
> these   new  sys-whonix   time errors .  I hope they are going to
> make  a useable   new template  Whonix14 install instructions (which
> apparently may fix these time NTP error) ;  the upgrade 13-14  looks
> crazy IMO

If you want to try out the unstable -14 templates, you can follow this:
https://github.com/Qubes-Community/Contents/blob/master/docs/misc/iaq.md#manually-install-whonix-14-templates.


-- 
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/954231e8090315b8020027ade95c551f%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] failed to start SSD after installing Qubes 4

[awokd]

On Tue, May 22, 2018 10:00 am, wd...@freenet.de wrote:
> just reinstalled Qubes with UEFI-Mode only (without CMS) in BIOS... but i
> get still the blackscreen after reboot... so it doesnt want to start the
> SSD
>  
> the thing is... i don't see the start screen (grub2 or whatever it is) if
> i install from USB. It just start the USB without showing me the screen
> with possibilities to choose.
> Normally it should show me "test media and install qubes".
>  
> so do i understand it right, that the grub or MBR is dead?

If you have a nvidia card in your laptop, try to disable it in your UEFI
config or add the nouveau.modeset=0 option. Also try installing in legacy
only mode, if you haven't already.

-- 
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/9f03bb0b0824fd335c9625eaa71666d1%40elude.in.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Curl error (6) by updating dom0

[evo]

Hi,

now i get Qubes 4.0 working... but by updating dom0 i get much errors.

curl error (6): couldn't resolve host name for ...

there are many of the mirrors which follows then.

it's a very fresh install of the qubes 4.0, so i did not do anything on
the system, but to set the network on manual connection with the router.

the strange thing is, that other mirrors work, so dom0 could
install/upgrade 46 packages.. but not the mentioned with the error.


greets
evo

-- 
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/f447291f-39cb-993a-4bf3-4a82c518bc69%40aliaks.de.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] No System(xen)boot after Qubes 4.0 installation

[evo]

after trying to install Qubes 3.2 (that i already had) i got also
problems. Than i installed it in legacy (no UEFI) mode and everything
was ok, also for Qubes 4.0

don't understand it (because earlier the 3.2 version works with UEFI
well), but it works!

-- 
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/51328895-4b03-9567-e9c3-8228312c3777%40aliaks.de.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Fedora 26 and Debian 8 approaching EOL

[Holger Levsen]

On Wed, May 23, 2018 at 08:21:12PM -0500, Andrew David Wong wrote:
> Fedora 26 will reach EOL ([end-of-life]) on 2018-06-01, and Debian 8
> (["Jessie" full, not LTS][debian-releases]) will reach EOL on
> 2018-06-06. We strongly recommend that all Qubes users upgrade their
> Fedora 26 and Debian 8 TemplateVMs and StandaloneVMs to Fedora 27 and
> Debian 9 or higher, respectively, by these EOL dates. 

I'm not sure why you suggest^wstrongly recommend to upgrade from Debian
8 to 9. "Suggest" I would understand, but Debian 8 will be supported for
another 2 years via LTS.
 

-- 
cheers,
Holger

-- 
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/20180524091854.ydlin2mvv77qeb2r%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: [qubes-users] mr. tasket's vpn new SMTP errors timeout in thunderbird

[tasket]

On 24.05.2018 06:15, john wrote:

so, until today all was well, I really have done much other than
switch over to Fedora-28 for all App-proxyVM qube/domains and the
sys-net sys-firewall, but even after that I've been sending SMTP ok on
thunderbird, till today

I can IMAP ok, its just  SMTP,  is there  some  iptables -allow port
465  I should try adding,  if so,  can you help me  how and where to
do that , and so it would persist

I made the App-proxy qube-domains  via installing the github script in
the app-proxy and then cloning it and changing out the  ln -s  links


FWIW, I'm having sending issues as well... sending this via webmail.

The proxy firewall config doesn't have any impediments to email.

There has probably been a surge in attacks lately against email 
services, who sometimes block the SMTP port from VPN IP addresses; this 
is usually done to deter spammers or stem a rise in attacks. Even VPN 
providers may choose to block port 465 so they stay in the good graces 
of service providers.


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/e0b9a52089d5523bffe59eb5e9361ccc%40posteo.net.
For more options, visit https://groups.google.com/d/optout.