Re: [qubes-users] Get help with HNS VM installation error

2018-11-10 Thread 'awokd' via qubes-users

unman:

On Sat, Nov 10, 2018 at 03:36:09PM +, 'awokd' via qubes-users wrote:

gdru...@gmail.com:

Hi,

I'm trying to install a VM in HVM mode called HNS (hybrid network simulation).

Based on Debian, HNS seems to run on KVM/QEMU.


Running a hypervisor like KVM inside another hypervisor like Xen is known as
"nested virtualization". This is disabled and not supported in Qubes.


I think that gdrub51 is saying that HNS runs under KVM, and they want to
run it under Qubes, *not* that they are trying to run KVM within Qubes.


OK.


In any case, I dont believe that nested virtualization is "disabled"
under Qubes. Not suppported certainly, but that's different.


https://groups.google.com/d/msg/qubes-users/BwQskBAvMtY/AzZQ7Y-NAAAJ
https://groups.google.com/d/msg/qubes-users/Y3P_moY4QN0/PdYhFWCvCAAJ

Don't believe nestedhvm=1 out of the box. Ergo, it's disabled (at least 
for type 1 hypervisors). :)



--
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/9f38e68a-a818-3007-d6a0-9fef6fc45ab8%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] HCL - Purism Librem 13 v2

2018-11-10 Thread 22rip
Tough questions and discussion but in the spirit of finding the "best" we can 
get laptop for Qubes 4.0  (Best being defined as: available to purchase, priced 
right, most open, most "reasonably" secure and"reasonably simple" to 
maintain), for me I see the following as my best options, ranked:

Lenovo Carbon 5G X1
Available
Good RAM
Little pricey
Easy install/maintain? Not sure if I can flash these BIOS...

Lenova 400 series
Available
Affordable
Limited RAM?
Little boxy
Easier to install/maintain

Librem 'what ever" model
Available
NOT Affordable
Limited RAM?
Reasonably easy to install/maintain!

G505
NOT as Available
Affordable
Limited RAM?
Very boxy?
Tough to install/maintain (Flash BIOS?? Out of my scope...)


200 series
NOT as Available?
Affordable
Limited RAM?
Very boxy?
Tough to install/maintain! (Flash BIOS?? Out of my scope...)


Dell/HP/Other?
I don't know, but I suspect Qubes was developeded on Lenovo's yet select models 
work

Desk Tops
I need a laptop...

Keep in mind I might weigh some of the "Easy to install/maintain" perspective 
more heavily but I see my best options as:

1)Carbon X1 being the ultimate winner (if I want to invest the $1k)
2)T400+ series for the budget concerned
3)Librem if you want to get the best you can with out the "fuss" and pay some $$
4)G505/200 if you have the technical know-how/experience


What I am struggling to weigh is the security/privacy/trust compromises and 
implications I have made/would make? I know G505/200 type products are most 
secure but how can I get one pre-installed and done (Easy) yet still balance 
trust, security, afford-ability, etcI fear the open source BIOS are out of 
my technical scope to install and maintain.

I find Librem intriguing with the easiest "most" open source option for the 
"reasonable" layman(person)...sure not Intel/AMD/government secure but at least 
non chip maker collusion secure? Lets assume Librem screwed up initially with 
their claimsare they clear now? Is their product a good option?

Decisions, Decisions...

 

-- 
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/d53fd873-90fb-4426-b960-efd57aafbadd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] HCL - Purism Librem 13 v2

2018-11-10 Thread unman
On Sat, Nov 10, 2018 at 11:33:48AM -0800, Kyle Rankin wrote:
> 
> > Also, i wasnt able to find a statement of Purism about the fact that, in 
> > the beginning, they claimed the ME was "completely disabled and removed". I 
> > mean, that was obviously not true right?
> 
> I can only comment on the current state of things and what we have tried to
> be open about on our site. I don't recall them using words like
> "completely" but I also wasn't working there at the time.
> 

I find this somewhat disingenuous.

Original claims:

"This is the first laptop to be manufactured where there is no mystery
software. This means that there are absolutely no proprietary drivers
in the linux kernel, no Linux kernel binary blobs, and no proprietary
software applications required to operate this computer."

Later:
"We promise that a Purism system and all its components  will be free
according to the strictest of guidelines set forth by the FSF's Free
Software Definition."

By 2016, the company had (under pressure) rolled back on these claims,
and acknowledged that the BIOS and Intel Binaries required binary blobs.

The "completely" claim is in the October19 2017 post - "Purism Librem
Laptops Completely Disable Intel's Management Engine"

I think that what bothers people is that the early claims were either false
or misleading. I had concerns about the whole "Qubes endorsed" debacle.
I believe issues like these raise questions about the probity of the company,

unman

-- 
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/2018024616.jdigceo4sob5pdn4%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Get help with HNS VM installation error

2018-11-10 Thread unman
On Sat, Nov 10, 2018 at 03:36:09PM +, 'awokd' via qubes-users wrote:
> gdru...@gmail.com:
> > Hi,
> > 
> > I'm trying to install a VM in HVM mode called HNS (hybrid network 
> > simulation).
> > 
> > Based on Debian, HNS seems to run on KVM/QEMU.
> 
> Running a hypervisor like KVM inside another hypervisor like Xen is known as
> "nested virtualization". This is disabled and not supported in Qubes.

I think that gdrub51 is saying that HNS runs under KVM, and they want to
run it under Qubes, *not* that they are trying to run KVM within Qubes.

In any case, I dont believe that nested virtualization is "disabled"
under Qubes. Not suppported certainly, but that's different.

unman

-- 
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/2018015806.zjpgidqcz5s2vwuh%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Costum qubes order in QVM

2018-11-10 Thread pieter lems
Thanks for the response and sorry for the late response back. Concerning
the question, How didn't i think of that -_-! Thank you for mentioning
this. I've been using qube colors for my qube order. It works pretty well
if you get used to it.

For anyone wanting to use my method, the order of the qube colors is as
follows:
black ( i use it for my templates)
purple ( for sys qubes ex. sys-whonix)
blue ( for disposable vm's)
The rest of the colors can be used for whatever you like , but i use the
red one for qubes which are not connected to a netVM (ex. vault and db vm)
grey
green
yellow
orange
red

cheers!

Op za 10 nov. 2018 om 04:05 schreef Sven Semmler :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 11/2/18 8:20 AM, pieter lems wrote:
> > How does one costumize the order in wich the qubes are displayed.
>
> If you want a solution without programming: use a naming convention. I
> use simple prefix:
>
> app-... for AppVMs
> dvm-... for DispVM templates
> sys-... for system qubes
> sys-dvm-... for disposable system qubes
> tpl-... for templates
>
> Both qvm-ls and qubes-qube-manager will show your qubes somewhat
> ordered that way.
>
> /Sven
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlvmSwQACgkQ2m4We49U
> H7ZQAA/+JK4PHdoVFFmHYw0VDbQA6Gj2P4WeYtqUaxTdPeH8fdLon+fzmFxe6Wph
> hS/18fvSL9hsX9/UE5L/G2JseedKKReqQheQhhRWsSurZw3+KiWIgi6l+KzSMv6u
> 5mSieodtLZus1LeplYCA0/fHQmNgdE1+ArNTcGNhJfOfHbuacmqdFeq2aaaSNL8q
> 2uPzpwu9wm/O5wcXBg06pNVHQJ5BVm1DBCvUSApONwT+GvdJu/GMz/YeZcPTuS/x
> cB5b4TRkzlhCJJ1ytdStNU/EOgE3q7nXTDcZmlCjssJb3ouRxT0gCI/S5fyEgZmg
> ufcGe80Y/e1ocqGbJwx1IY7EnrZg/y1jqcr+KrCHqoSDSs7SpLjbgN7jUeXgb6Hc
> T73ndVxATbjFt28JZhv2EkiQdadqyl1N7G2a0DJaAY/WTfcgnEETQt9ev0PdY9xP
> OPISKvQ8byxfazJoDL/DByV61PYQ4kCKxh1dOO3jTt/JyJM8TyK9+PQsGaoUNkTe
> 6NH5qeEP0pW8Sv1VTMPHMyD1no+t+1Y9VAXjYhs47Q4zWYcqhi6QAW6YZJuuOuLX
> 0i09++sz2ig6rPjSwLVkzU6576/3q7pJ3v001NiR783SYMEPC+txe+PQw22Fjvyf
> jat+YsZ2D62Juk80ok9K0KzxV6G/z11MGEJSnHS8jqjvADt8h4I=
> =+8Hd
> -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/8d88df08-f7f6-e6c5-ed2d-dfcbb15d725a%40SvenSemmler.org
> .
> 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/CAK8vAnV9UbeRqq0fPN240ALRmdUR8k7rJ%2BOgXP0D_3NZhbxJWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Yubikey/Yubico Authenticator R4.0/r4.0.1rc4

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 16:59:00 UTC-5 schrieb hm...@tuta.io:
> The SW Yubico Authenticator works fine in a Fedora or Debian App VM.
> 
> Installation instructions Fedora 28/29:
> sudo dnf install yubioath desktop
> -then link it to your App VM
> 
> Installation instructions Debian 9:
> sudo apt install yubioath desktop
> -then link it to your App VM
> 
> Br
> Sebi

Installation instructions in your Fedora Template 28/29:

sudo dnf install yubioath-desktop
-then link it to your App VM

Installation instructions in your Debian 9 Template:

sudo apt install yubioath-desktop
-then link it to your App VM

-- 
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/03dfeac7-4b13-476e-8176-6bd18aa93d48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Yubikey/Yubico Authenticator R4.0/r4.0.1rc4

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 16:59:00 UTC-5 schrieb hm...@tuta.io:
> The SW Yubico Authenticator works fine in a Fedora or Debian App VM.
> 
> Installation instructions Fedora 28/29:
> sudo dnf install yubioath desktop
> -then link it to your App VM
> 
> Installation instructions Debian 9:
> sudo apt install yubioath desktop
> -then link it to your App VM
> 
> Br
> Sebi


Installation instructions in your Fedora Template 28/29:
sudo dnf install yubioath desktop
-then link it to your App VM

Installation instructions in your Debian 9 Template:
sudo apt install yubioath desktop
-then link it to your App VM

-- 
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/3e05cd76-8dbe-4ae1-9ff4-c3ea17502418%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Yubikey/Yubico Authenticator R4.0/r4.0.1rc4

2018-11-10 Thread hmiyc
The SW Yubico Authenticator works fine in a Fedora or Debian App VM.

Installation instructions Fedora 28/29:
sudo dnf install yubioath desktop
-then link it to your App VM

Installation instructions Debian 9:
sudo apt install yubioath desktop
-then link it to your App VM

Br
Sebi

-- 
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/1a764d0d-fde8-4068-afd7-41b142bda3e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - HP Elitebook x360 1030 G2

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 14:38:21 UTC-5 schrieb Sebastian Schatter:
> HW specifications: HP Elitebook x360 1030 G2
> 
> Intel Core i7 vPro 7th Gen
> 
> 16GB RAM
> 
> 256GB SSd
> 
> OS - Qubes R4.0.1rc1
> 
> The NB has no RJ45 port so the External USB-C Thunderbolt Dockingstation via 
> LAN doesn't work yet.
> 
> 
> 
> ---
> 
> layout:
> 
>   'hcl'
> 
> type:
> 
>   'convertible'
> 
> hvm:
> 
>   'yes'
> 
> iommu:
> 
>   'yes'
> 
> slat:
> 
>   'yes'
> 
> tpm:
> 
>   'unknown'
> 
> remap:
> 
>   'yes'
> 
> brand: |
> 
>   HP
> 
> model: |
> 
>   HP EliteBook x360 1030 G2
> 
> bios: |
> 
>   P80 Ver. 01.23
> 
> cpu: |
> 
>   Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
> 
> cpu-short: |
> 
>   FIXME
> 
> chipset: |
> 
>   Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
> Registers [8086:5904] (rev 02)
> 
> chipset-short: |
> 
>   FIXME
> 
> gpu: |
> 
>   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
> controller])
> 
>   Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 
> 21)
> 
> gpu-short: |
> 
>   FIXME
> 
> network: |
> 
>   Broadcom Limited NetXtreme BCM57762 Gigabit Ethernet PCIe (rev 01)
> 
>   Intel Corporation Wireless 8265 / 8275 (rev 78)
> 
> memory: |
> 
>   15783
> 
> scsi: |
> 
>   SanDisk SD8SN8U- Rev: 0006
> 
> usb: |
> 
>   2
> 
> versions:
> 
> 
> 
> - works:
> 
>     'FIXME:yes|no|partial'
> 
>   qubes: |
> 
>     R4.0
> 
>   xen: |
> 
>     4.8.4
> 
>   kernel: |
> 
>     4.14.74-1
> 
>   remark: |
> 
>     FIXME
> 
>   credit: |
> 
>     FIXAUTHOR
> 
>   link: |
> 
>     FIXLINK
> 
> 
> 
> ---

Installation instructions:
- R4.0.1rc1 Image DD to SSD does not work (installation aborts)
- R4.0.1rc1 Image DD to USB drive does not work (installation aborts)
- R4.0.1rc1 Image burn to DVD-RW works fine (installation goes through)

Br
Sebi

-- 
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/b94dcddd-ca70-475c-8ffe-1f1be302464f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - HP Elitebook x360 1030 G2

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 14:38:21 UTC-5 schrieb Sebastian Schatter:
> HW specifications: HP Elitebook x360 1030 G2
> 
> Intel Core i7 vPro 7th Gen
> 
> 16GB RAM
> 
> 256GB SSd
> 
> OS - Qubes R4.0.1rc1
> 
> The NB has no RJ45 port so the External USB-C Thunderbolt Dockingstation via 
> LAN doesn't work yet.
> 
> 
> 
> ---
> 
> layout:
> 
>   'hcl'
> 
> type:
> 
>   'convertible'
> 
> hvm:
> 
>   'yes'
> 
> iommu:
> 
>   'yes'
> 
> slat:
> 
>   'yes'
> 
> tpm:
> 
>   'unknown'
> 
> remap:
> 
>   'yes'
> 
> brand: |
> 
>   HP
> 
> model: |
> 
>   HP EliteBook x360 1030 G2
> 
> bios: |
> 
>   P80 Ver. 01.23
> 
> cpu: |
> 
>   Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
> 
> cpu-short: |
> 
>   FIXME
> 
> chipset: |
> 
>   Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
> Registers [8086:5904] (rev 02)
> 
> chipset-short: |
> 
>   FIXME
> 
> gpu: |
> 
>   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
> controller])
> 
>   Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 
> 21)
> 
> gpu-short: |
> 
>   FIXME
> 
> network: |
> 
>   Broadcom Limited NetXtreme BCM57762 Gigabit Ethernet PCIe (rev 01)
> 
>   Intel Corporation Wireless 8265 / 8275 (rev 78)
> 
> memory: |
> 
>   15783
> 
> scsi: |
> 
>   SanDisk SD8SN8U- Rev: 0006
> 
> usb: |
> 
>   2
> 
> versions:
> 
> 
> 
> - works:
> 
>     'FIXME:yes|no|partial'
> 
>   qubes: |
> 
>     R4.0
> 
>   xen: |
> 
>     4.8.4
> 
>   kernel: |
> 
>     4.14.74-1
> 
>   remark: |
> 
>     FIXME
> 
>   credit: |
> 
>     FIXAUTHOR
> 
>   link: |
> 
>     FIXLINK
> 
> 
> 
> ---

Installation instructions:
- R4.0 Image DD to SSD does not work (installation aborts)
- R4.0 Image DD to USB drive does not work (installation aborts)
- R4.0 Image burn to DVD-RW works fine (installation goes through)

Br
Sebi

-- 
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/3cc26c9a-a58f-4901-8454-cc1247840eb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Lenovo x230 / Coreboot/SeaBios

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 15:16:28 UTC-5 schrieb Sebastian Schatter:
> HW specifications: Lenovo x230
> 
> 16GB RAM
> 
> 256GB SSd
> 
> OS - Qubes R4.0
> 
> BIOS: Coreboot/SeaBios 1.10.-2 and active ME Cleaner
> 
> 
> 
> ---
> 
> layout:
> 
>   'hcl'
> 
> type:
> 
>   'laptop'
> 
> hvm:
> 
>   'yes'
> 
> iommu:
> 
>   'yes'
> 
> slat:
> 
>   'yes'
> 
> tpm:
> 
>   'unknown'
> 
> remap:
> 
>   'yes'
> 
> brand: |
> 
>   LENOVO
> 
> model: |
> 
>   2325YBN
> 
> bios: |
> 
>   CBET4000 4.6-196-g0fb6568
> 
> cpu: |
> 
>   Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
> 
> cpu-short: |
> 
>   FIXME
> 
> chipset: |
> 
>   Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 
> 09)
> 
> chipset-short: |
> 
>   FIXME
> 
> gpu: |
> 
>   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
> (rev 09) (prog-if 00 [VGA controller])
> 
> gpu-short: |
> 
>   FIXME
> 
> network: |
> 
>   Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
> 
>   Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
> 
> memory: |
> 
>   8116
> 
> scsi: |
> 
>   Samsung SSD 850  Rev: 1B6Q
> 
> usb: |
> 
>   3
> 
> versions:
> 
> 
> 
> - works:
> 
>     'FIXME:yes|no|partial'
> 
>   qubes: |
> 
>     R4.0
> 
>   xen: |
> 
>     4.8.4
> 
>   kernel: |
> 
>     4.14.74-1
> 
>   remark: |
> 
>     FIXME
> 
>   credit: |
> 
>     FIXAUTHOR
> 
>   link: |
> 
>     FIXLINK
> 
> 
> 
> 
> 
> -- 
> 
>  Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: 
> 
>  https://tutanota.com

Installation instructions:
- R4.0 Image DD to SSD works fine
- R4.0 Image DD to USB drive works well
- R4.0 Image burn to DVD-RW works well

Br
Sebi

-- 
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/225d54cc-7bec-4e7b-952b-1283e630a4f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Vertrauliche Nachricht von Sebastian Schatter

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 16:00:38 UTC-5 schrieb pieter lems:
> For the people that don't understand German or don't bother to translate it 
> here you go:
> 
> 
> 
> 
> --
> 
> Good day,
> 
> 
> I have just sent a confidential message to Tutanota (https://tutanota.com). 
> Tutanota automatically encrypts emails end-to-end, including all attachments. 
> The following link leads to the encrypted mailbox, from which you can also 
> answer in encrypted form:
> 
> 
> Show encrypted message
> 
> 
> Or copy this link to the browser:
> https://app.tutanota.com/#mail/LQzEzz4131kbz7xTfTUj_JA7h57f5w
> 
> 
> This e-mail was generated automatically for the transmission of the link. The 
> link will remain valid until I send a new confidential email.
> 
> 
> many Greetings
> 
> 
> --
> 
> 
> It's an auto message so not sure if it has any meaning.
> Cheers!
> 
> 
> On Sat, Nov 10, 2018, 9:11 PM Sebastian Schatter  wrote:
> 
> 
> Guten Tag,
> ich habe gerade eine vertrauliche Nachricht mit Tutanota 
> (https://tutanota.com) gesendet. Tutanota verschlüsselt E-Mails automatisch 
> Ende-zu-Ende, inklusive aller Anhänge. Der folgende Link führt zur 
> verschlüsselten Mailbox, von der aus auch verschlüsselt geantwortet werden 
> kann:
> Verschlüsselte Nachricht anzeigen
> Oder kopiere diesen Link in den Browser:
> https://app.tutanota.com/#mail/LQzEzz4131kbz7xTfTUj_JA7h57f5w
> 
> Diese E-Mail wurde für die Übermittlung des Links automatisch erzeugt. Der 
> Link bleibt gültig, bis ich eine neue vertrauliche E-Mail sende.
> Viele Grüße
> Sebastian Schatter
> 
> 
> 
> 
> -- 
> 
> 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...@googlegroups.com.
> 
> To post to this group, send email to qubes...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/LQzF-1G--V-1%40tuta.io.
> 
> For more options, visit https://groups.google.com/d/optout.

Hello Pieter

Thanks for the translation. I sent this post again in english, a decryption is 
not necessary.

Br
Sebi

-- 
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/c20ad8bf-c83c-46f6-9735-3248aa3d2281%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Vertrauliche Nachricht von Sebastian Schatter

2018-11-10 Thread pieter lems
For the people that don't understand German or don't bother to translate it
here you go:


--
Good day,

I have just sent a confidential message to Tutanota (https://tutanota.com).
Tutanota automatically encrypts emails end-to-end, including all
attachments. The following link leads to the encrypted mailbox, from which
you can also answer in encrypted form:

Show encrypted message

Or copy this link to the browser:
https://app.tutanota.com/#mail/LQzEzz4131kbz7xTfTUj_JA7h57f5w

This e-mail was generated automatically for the transmission of the link.
The link will remain valid until I send a new confidential email.

many Greetings

--

It's an auto message so not sure if it has any meaning.
Cheers!

On Sat, Nov 10, 2018, 9:11 PM Sebastian Schatter  wrote:

> Guten Tag,
>
> ich habe gerade eine vertrauliche Nachricht mit Tutanota (
> https://tutanota.com) gesendet. Tutanota verschlüsselt E-Mails
> automatisch Ende-zu-Ende, inklusive aller Anhänge. Der folgende Link führt
> zur verschlüsselten Mailbox, von der aus auch verschlüsselt geantwortet
> werden kann:
>
> Verschlüsselte Nachricht anzeigen
> 
>
> Oder kopiere diesen Link in den Browser:
> https://app.tutanota.com/#mail/LQzEzz4131kbz7xTfTUj_JA7h57f5w
>
> Diese E-Mail wurde für die Übermittlung des Links automatisch erzeugt. Der
> Link bleibt gültig, bis ich eine neue vertrauliche E-Mail sende.
>
> Viele Grüße
> Sebastian Schatter
>
> --
> 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/LQzF-1G--V-1%40tuta.io
> 
> .
> 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/CAK8vAnVe-w%2BZ17Hs7%3Df_PM_C2%2Bw24bc8Lt3wgNdOUWzUedqNVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - Lenovo x230 / Coreboot/SeaBios

2018-11-10 Thread Sebastian Schatter
HW specifications: Lenovo x230
16GB RAM
256GB SSd
OS - Qubes R4.0
BIOS: Coreboot/SeaBios 1.10.-2 and active ME Cleaner

---
layout:
  'hcl'
type:
  'laptop'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  LENOVO
model: |
  2325YBN
bios: |
  CBET4000 4.6-196-g0fb6568
cpu: |
  Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
  Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
memory: |
  8116
scsi: |
  Samsung SSD 850  Rev: 1B6Q
usb: |
  3
versions:

- works:
    'FIXME:yes|no|partial'
  qubes: |
    R4.0
  xen: |
    4.8.4
  kernel: |
    4.14.74-1
  remark: |
    FIXME
  credit: |
    FIXAUTHOR
  link: |
    FIXLINK


-- 
 Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: 
 https://tutanota.com

-- 
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/LQzGAVz--3-1%40tuta.io.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Vertrauliche Nachricht von Sebastian Schatter

2018-11-10 Thread Sebastian Schatter
Guten Tag,ich habe gerade eine vertrauliche Nachricht mit Tutanota (https://tutanota.com) gesendet. Tutanota verschlüsselt E-Mails automatisch Ende-zu-Ende, inklusive aller Anhänge. Der folgende Link führt zur verschlüsselten Mailbox, von der aus auch verschlüsselt geantwortet werden kann:Verschlüsselte Nachricht anzeigenOder kopiere diesen Link in den Browser:https://app.tutanota.com/#mail/LQzEzz4131kbz7xTfTUj_JA7h57f5wDiese E-Mail wurde für die Übermittlung des Links automatisch erzeugt. Der Link bleibt gültig, bis ich eine neue vertrauliche E-Mail sende.Viele GrüßeSebastian Schatter



-- 
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/LQzF-1G--V-1%40tuta.io.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - HP Elitebook x360 1030 G2

2018-11-10 Thread 'Sebastian Schatter' via qubes-users
HW specifications: HP Elitebook x360 1030 G2
Intel Core i7 vPro 7th Gen
16GB RAM
256GB SSd
OS - Qubes R4.0.1rc1

The NB has no RJ45 port so the External USB-C Thunderbolt Dockingstation via 
LAN doesn't work yet.

---
layout:
  'hcl'
type:
  'convertible'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  HP
model: |
  HP EliteBook x360 1030 G2
bios: |
  P80 Ver. 01.23
cpu: |
  Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers [8086:5904] (rev 02)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
  Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
gpu-short: |
  FIXME
network: |
  Broadcom Limited NetXtreme BCM57762 Gigabit Ethernet PCIe (rev 01)
  Intel Corporation Wireless 8265 / 8275 (rev 78)
memory: |
  15783
scsi: |
  SanDisk SD8SN8U- Rev: 0006
usb: |
  2
versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R4.0
  xen: |
4.8.4
  kernel: |
4.14.74-1
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---

-- 
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/loI0keQf3TXgW_uTAiuhoNIioomwWeCRSl-SFjfXpH-VNDIh9mhLBZeiw6W638H5gyFEt4TRVCB2-l5hLN9azxnyQlMdRCX3cS7gRuFacsY%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] HCL - Purism Librem 13 v2

2018-11-10 Thread Kyle Rankin
I would have preferred to keep this thread focused on the HCL and not get
too derailed off-topic. I'll try to keep this brief and apologies to the
moderators for continuing the off-topic thread. I'll give a reply and then
leave it.

As someone who's working inside the org every day earnestly to try to
improve everyone's security and freedom, I guess I don't get all the
animosity, as I don't know of too many other organizations who are trying
as we are to advance the cause of liberating these closed modules. I don't
agree with the "all or nothing" approach some people are touting--having a
motherboard without AMT at all, and with an ME that is reflashed to have
most of its code removed is, to me, a much better situation than what you
can get off the shelf. Is it 100% there? Of course not, but we are truly
working to get it there.

Other replies inline:

On Sat, Nov 10, 2018 at 06:33:05PM +, 'casiu' via qubes-users wrote:
> 
> "We have four ME modules remaining to liberate (and anyone with access to our 
> BIOS ROM or our BIOS build script
>  can confirm those claims)."
> 
> Last time i checked Intel still did not hand you over their signing-keys ?
> Im happy to change my mind, please educate me.:) Is the ME completely shut 
> off BEFORE the kernel boots up?
> If not, im sure you know a few me modules more ore less is completely 
> irrelevant from a security point of view.
> 

As part of reflashing the BIOS we reflash the ME so when the system boots
it is running from the remaining four modules (kernel, supporting kernel
libraries) in the ME that initialize the hardware. The high level info is
here:

https://puri.sm/learn/intel-me/

And the more detailed technical information is here:

https://puri.sm/posts/deep-dive-into-intel-me-disablement/

> Also, i wasnt able to find a statement of Purism about the fact that, in the 
> beginning, they claimed the ME was "completely disabled and removed". I mean, 
> that was obviously not true right?

I can only comment on the current state of things and what we have tried to
be open about on our site. I don't recall them using words like
"completely" but I also wasn't working there at the time.

> 
> From what i see, despite Purism claims they will liberate it probably 
> sometime , purism-bios still only initializes proprietary blobs, which also 
> defeats the purpose. Im not one for great conspiracy theories, and also at 
> least for now willing to accept the term "opensource-hardware" for something 
> with one or two small irrelevant blobs because they cant be avoided,
> but advertising hardware which runs almost entirely on closed source software 
> (certainly, all the important parts do), that just sound highly dishonest in 
> my ears.
> 

We may have to agree to disagree here, as I wouldn't characterize loading
an open source coreboot BIOS that includes Intel FSP binary blobs and the
remaining few percent of the closed ME code that we haven't freed yet, and
then boots into a completely free software OS as "almost entirely on closed
source software." It sounds like you are assigning much more importance and
weight into the FSP than I am when thinking about the whole system.

> Last one: Would you honestly recommend people  buying your products to 
> improve their security RIGHT NOW, not someday in the future when and if your 
> products will be completely open source. If so, wy?

I would. For one, we are one of the few companies who are actively working
to improve the current situation with respect to closed firmware and
software on regular laptops. Not everyone has the ability to reflash
firmware themselves to apply an open source BIOS and erase most of the ME
and so we provide hardware that has that already applied. There are still
binary blobs remaining but we are working to remove those as well.

A lot of the arguments seem to center on some belief that we aren't genuine
in our beliefs because we've set big goals, some of which are long term,
and therefore haven't achieved all of those goals yet. For what it's worth,
we have gone to the extra effort to codify our ethical stance into our
corporate Social Purpose Corporation (SPC) charter and mean what we say.

I personally am working to include Heads as a default tamper-detecting BIOS
option for more security-minded people who order our hardware. Our hardware
runs Qubes 4.0 out of the box and it is the primary OS on both my personal
and work laptops (both Librems). We are actively working to integrate our
Librem Key USB security token with Heads (my PR was just merged this past
week) to provide a simple way to detect tampering in the BIOS and
kernel/initrd/grub config.

Is there still more work to do? Sure. But then I've always liked to be busy
and hated being bored at work. Security is like golf. You try to get closer
to the hole with every stroke. If you just try to get a hole in one every
time you will lose.

-Kyle

> 
> If you could provide me an answer to those Questions, i would be very 
> grateful. 

[qubes-users] HCL-R4.0.1rc1-HP Elitebook x360 1030 G2

2018-11-10 Thread hmiyc
HW specifications: HP Elitebook x360 1030 G2
Intel Core i7 vPro 7th Gen
16GB RAM
256GB SSd
OS - Qubes R4.0.1rc1

The NB has no RJ45 port so the External USB-C Thunderbolt Dockingstation via 
LAN doesn't work yet.

---
layout:
  'hcl'
type:
  'convertible'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  HP
model: |
  HP EliteBook x360 1030 G2
bios: |
  P80 Ver. 01.23
cpu: |
  Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers [8086:5904] (rev 02)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
  Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
gpu-short: |
  FIXME
network: |
  Broadcom Limited NetXtreme BCM57762 Gigabit Ethernet PCIe (rev 01)
  Intel Corporation Wireless 8265 / 8275 (rev 78)
memory: |
  15783
scsi: |
  SanDisk SD8SN8U- Rev: 0006
usb: |
  2
versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R4.0
  xen: |
4.8.4
  kernel: |
4.14.74-1
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

-- 
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/3b338d5c-28c2-439d-81db-2bf906abc069%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Fresh install Failed to synchronize cache for repo 'qubes-dom0-current' and 'qubes-templates-itl'

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 20:12:16 UTC+1 schrieb alrojs:
> On Friday, November 9, 2018 at 6:57:31 PM UTC-8, alrojs wrote:
> > Hardware: t460p and t450s
> > I am currently on my fourth install of qubes and using 4.0 rc1 build.
> > 
> > The operating system seems to work fine. I am able to create proxyvm's, and 
> > link them together  appvm>vpn1>vpn2>sys-whonix>sys-firewall>sys-net(main 
> > goal opsec). On my first and second install I was able to set up all these 
> > vm's, however when I wanted to update dom0 or install package u2f to use my 
> > yubikey I would always encounter this issue updating. 
> > 
> > whole output on terminal dom0
> > [user@dom0 ~] sudo qubes-dom0 update
> > using sys-firewall as UpdateVM to download updates for Dom0; this may take 
> > some time...
> > Qubes Dom0 Repository (updates)63 B/s | 169 B  00:02
> > Using sys-firewall as UpdateVM to download updates for Dom0; this may take 
> > some time...
> > Using sys-firewall as UpdateVm to download updates for Dom0; this may take 
> > some ...
> > Qubes Templates repository 66 B/s | 169 B 00:02
> > Failed to synchronize cache for repo 'qubes-dom0-current', ignoring this 
> > repo.
> > Failed to synchronize cache for repo 'qubes-templates-itl', ignoring this 
> > repo.
> > Last Metadata expiration check: 0:03:13 ago on Fri Nov 9 18:32:21 2018.
> > Dependencies resolved.
> > Nothing to do.
> > Complete!
> > No packages downloaded
> > 
> > 
> > 
> > I can confirm this is not a hardware issue as I am trying it on a t450p and 
> > t450s, two complete different laptops.
> > 
> > I've tried trouble shooting this for the past 10 hours and i still don't 
> > know what I am doing wrong. I've tried so many suggested tips. http to 
> > https, mod yum repo, and others i've alrady forgotten i'm sure im probably 
> > looking in the wrong place. please anyone who can lead me to fixing this 
> > issue i would greatly appreciate it.
> 
> UPDATE!
> 
> I have no idea why this is happening but User alex completely fixed my issue
> https://groups.google.com/d/msg/qubes-users/K7zAP4LXcN4/U-09iYILAwAJ

It works for me now, too, thanks to Alex.
Thanks for the quick 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/d1f2d59d-0507-4947-8417-a6df74117495%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Fresh install Failed to synchronize cache for repo 'qubes-dom0-current' and 'qubes-templates-itl'

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 03:57:31 UTC+1 schrieb alrojs:
> Hardware: t460p and t450s
> I am currently on my fourth install of qubes and using 4.0 rc1 build.
> 
> The operating system seems to work fine. I am able to create proxyvm's, and 
> link them together  appvm>vpn1>vpn2>sys-whonix>sys-firewall>sys-net(main goal 
> opsec). On my first and second install I was able to set up all these vm's, 
> however when I wanted to update dom0 or install package u2f to use my yubikey 
> I would always encounter this issue updating. 
> 
> whole output on terminal dom0
> [user@dom0 ~] sudo qubes-dom0 update
> using sys-firewall as UpdateVM to download updates for Dom0; this may take 
> some time...
> Qubes Dom0 Repository (updates)63 B/s | 169 B  00:02
> Using sys-firewall as UpdateVM to download updates for Dom0; this may take 
> some time...
> Using sys-firewall as UpdateVm to download updates for Dom0; this may take 
> some ...
> Qubes Templates repository 66 B/s | 169 B 00:02
> Failed to synchronize cache for repo 'qubes-dom0-current', ignoring this repo.
> Failed to synchronize cache for repo 'qubes-templates-itl', ignoring this 
> repo.
> Last Metadata expiration check: 0:03:13 ago on Fri Nov 9 18:32:21 2018.
> Dependencies resolved.
> Nothing to do.
> Complete!
> No packages downloaded
> 
> 
> 
> I can confirm this is not a hardware issue as I am trying it on a t450p and 
> t450s, two complete different laptops.
> 
> I've tried trouble shooting this for the past 10 hours and i still don't know 
> what I am doing wrong. I've tried so many suggested tips. http to https, mod 
> yum repo, and others i've alrady forgotten i'm sure im probably looking in 
> the wrong place. please anyone who can lead me to fixing this issue i would 
> greatly appreciate it.

It works for me now, too, thanks to Alex.
Thanks for the quick 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/bdfb3776-3525-4334-ab77-962ce5e76cef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] R4.0.1rc1-HVL-HP x360 1030 G2

2018-11-10 Thread hmiyc
HW specifications: HP Elitebook x360 1030 G2
Intel Core i7 vPro 7th Gen
16GB RAM
256GB SSd
OS - Qubes R4.0.1rc1

The NB has no RJ45 port so the External USB-C Thunderbolt Dockingstation via 
LAN doesn't work yet.

---
layout:
  'hcl'
type:
  'convertible'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  HP
model: |
  HP EliteBook x360 1030 G2
bios: |
  P80 Ver. 01.23
cpu: |
  Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers [8086:5904] (rev 02)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
  Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
gpu-short: |
  FIXME
network: |
  Broadcom Limited NetXtreme BCM57762 Gigabit Ethernet PCIe (rev 01)
  Intel Corporation Wireless 8265 / 8275 (rev 78)
memory: |
  15783
scsi: |
  SanDisk SD8SN8U- Rev: 0006
usb: |
  2
versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R4.0
  xen: |
4.8.4
  kernel: |
4.14.74-1
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---

-- 
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/edb43c42-55ff-4030-81a5-5f17e8bed12b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 19:45:25 UTC+1 schrieb alrojs:
> On Saturday, November 10, 2018 at 8:29:04 AM UTC-8, hm...@tuta.io wrote:
> > @Alex - Thank you for pointing that out.
> > 
> > I just tried to install version R4.0.1rc1 on the x230 again, but the 
> > installation breaks off when configuring ext4.  It is probably due to the 
> > HW or Coreboot.
> > 
> > I will flash my x220 with Coreboot/SeaBios + Intel ME Cleaner and install 
> > R4.0.1rc1 again.  Then i let you know if your tip worked.
> > 
> > 
> > PS.  Under Qubes 3.0/3.1/3.2 i didn't have these problems.
> > 
> > 
> > Greetings
> > 
> > Sebi
> 
> We're you able to get it working? 
> 
> I will try this tip right now

@Alex - I tried the installation quickly on my HP x360 1030 G2. Your hint works 
fine. Thanks a lot Alex. 

HW specifications: HP Elitebook x360 1030 G2
Intel Core i7 vPro 7th Gen
16GB RAM
256GB SSd
OS - Qubes R4.0.1rc1

PS:Test it soon on my x220. 

Br
Sebi

-- 
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/dcbdc93f-1e96-495a-84b0-09ce56c55d4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Fresh install Failed to synchronize cache for repo 'qubes-dom0-current' and 'qubes-templates-itl'

2018-11-10 Thread alrojs
On Friday, November 9, 2018 at 6:57:31 PM UTC-8, alrojs wrote:
> Hardware: t460p and t450s
> I am currently on my fourth install of qubes and using 4.0 rc1 build.
> 
> The operating system seems to work fine. I am able to create proxyvm's, and 
> link them together  appvm>vpn1>vpn2>sys-whonix>sys-firewall>sys-net(main goal 
> opsec). On my first and second install I was able to set up all these vm's, 
> however when I wanted to update dom0 or install package u2f to use my yubikey 
> I would always encounter this issue updating. 
> 
> whole output on terminal dom0
> [user@dom0 ~] sudo qubes-dom0 update
> using sys-firewall as UpdateVM to download updates for Dom0; this may take 
> some time...
> Qubes Dom0 Repository (updates)63 B/s | 169 B  00:02
> Using sys-firewall as UpdateVM to download updates for Dom0; this may take 
> some time...
> Using sys-firewall as UpdateVm to download updates for Dom0; this may take 
> some ...
> Qubes Templates repository 66 B/s | 169 B 00:02
> Failed to synchronize cache for repo 'qubes-dom0-current', ignoring this repo.
> Failed to synchronize cache for repo 'qubes-templates-itl', ignoring this 
> repo.
> Last Metadata expiration check: 0:03:13 ago on Fri Nov 9 18:32:21 2018.
> Dependencies resolved.
> Nothing to do.
> Complete!
> No packages downloaded
> 
> 
> 
> I can confirm this is not a hardware issue as I am trying it on a t450p and 
> t450s, two complete different laptops.
> 
> I've tried trouble shooting this for the past 10 hours and i still don't know 
> what I am doing wrong. I've tried so many suggested tips. http to https, mod 
> yum repo, and others i've alrady forgotten i'm sure im probably looking in 
> the wrong place. please anyone who can lead me to fixing this issue i would 
> greatly appreciate it.

UPDATE!

I have no idea why this is happening but User alex completely fixed my issue
https://groups.google.com/d/msg/qubes-users/K7zAP4LXcN4/U-09iYILAwAJ

-- 
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/144d3c8f-9297-4451-858a-4ebdd87511b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread alrojs

This worked! this pushed the update through!!!

-- 
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/4333bad3-a7a0-413c-85c6-7f2476630540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread alrojs
On Saturday, November 10, 2018 at 8:29:04 AM UTC-8, hm...@tuta.io wrote:
> @Alex - Thank you for pointing that out.
> 
> I just tried to install version R4.0.1rc1 on the x230 again, but the 
> installation breaks off when configuring ext4.  It is probably due to the HW 
> or Coreboot.
> 
> I will flash my x220 with Coreboot/SeaBios + Intel ME Cleaner and install 
> R4.0.1rc1 again.  Then i let you know if your tip worked.
> 
> 
> PS.  Under Qubes 3.0/3.1/3.2 i didn't have these problems.
> 
> 
> Greetings
> 
> Sebi

We're you able to get it working? 

I will try this tip right now 

-- 
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/77a32881-9c1b-4c96-8243-db532a9974af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] HCL - Purism Librem 13 v2

2018-11-10 Thread 'casiu' via qubes-users


"We have four ME modules remaining to liberate (and anyone with access to our 
BIOS ROM or our BIOS build script
 can confirm those claims)."

Last time i checked Intel still did not hand you over their signing-keys ?
Im happy to change my mind, please educate me.:) Is the ME completely shut off 
BEFORE the kernel boots up?
If not, im sure you know a few me modules more ore less is completely 
irrelevant from a security point of view.

Also, i wasnt able to find a statement of Purism about the fact that, in the 
beginning, they claimed the ME was "completely disabled and removed". I mean, 
that was obviously not true right?

>From what i see, despite Purism claims they will liberate it probably sometime 
>, purism-bios still only initializes proprietary blobs, which also defeats the 
>purpose. Im not one for great conspiracy theories, and also at least for now 
>willing to accept the term "opensource-hardware" for something with one or two 
>small irrelevant blobs because they cant be avoided,
but advertising hardware which runs almost entirely on closed source software 
(certainly, all the important parts do), that just sound highly dishonest in my 
ears.

Last one: Would you honestly recommend people  buying your products to improve 
their security RIGHT NOW, not someday in the future when and if your products 
will be completely open source. If so, wy?

If you could provide me an answer to those Questions, i would be very grateful. 
I read this post twice , and i hope nobody finds it offensive in any way, im 
actually trying to get a productive discussion here.
Please dont let this go emotional, rather provide people with actual, 
verifiable TECHNICAL  FACTS.

Happy to learn something new, Casiu.


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Saturday, November 10, 2018 5:24 PM, Kyle Rankin  wrote:

> It's a shame this thread got hijacked by people slandering the company.
> Could someone who is responsible for the HCL please update it with the data
> I've provided in this thread? This would update the HCL with a version of
> the Librem 13v2 that provides a TPM for people who are considering running
> Qubes 4.0 with AEM.
>
> -Kyle
>
> PS. For what it's worth we continue to work earnestly behind the scenes to
> liberate the remaining binary blobs (FSP and what remains of the ME after
> we disable and delete the majority of the modules) because we want to
> provide people with modern hardware that runs blob-free. For the ME, we
> have already documented what we have done to attempt to both disable (HAP)
> and neuter (zero out modules) the ME. We have four ME modules remaining to
> liberate (and anyone with access to our BIOS ROM or our BIOS build script
> can confirm those claims). Those of you who work in this space are aware of
> the challenges behind all of this and if anyone wants to help us in
> liberating the FSP and the remaining four ME modules that are present we
> would certainly welcome the help.
>
> On Fri, Sep 14, 2018 at 11:10:59AM -0700, Kyle Rankin wrote:
>
> > Install works out of the box with no warnings. I haven't run into any
> > issues with hardware compatibility--hardware in general works (video,
> > audio, all ports, Fn keys). Hardware Kill Switches work as expected within
> > Qubes. Suspend/resume works.
> > By default it works with the standard included coreboot BIOS but I've also
> > tested it with Heads using the TPM and that works as well.
> > --
> > 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/20180914181059.fkt3blxd3heez54s%40work.
> > For more options, visit https://groups.google.com/d/optout.
>
> > layout:
> > 'hcl'
> > type:
> > 'laptop'
> > hvm:
> > 'yes'
> > iommu:
> > 'yes'
> > slat:
> > 'yes'
> > tpm:
> > ''
> > remap:
> > 'yes'
> > brand: |
> > Purism
> > model: |
> > Librem 13 v2
> > bios: |
> > 4.7-Purism-4-heads
> > cpu: |
> > Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
> > cpu-short: |
> > FIXME
> > chipset: |
> > Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
> > Bridge/DRAM Registers [8086:1904] (rev 08)
> > chipset-short: |
> > FIXME
> > gpu: |
> > Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
> > controller])
> > Intel Corporation Device [8086:9d24] (rev 21)
> > gpu-short: |
> > FIXME
> > network: |
> > Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
> > memory: |
> > 16298
> > scsi: |
> > Samsung SSD 850 Rev: 2B6Q
> > Samsung SSD 850 Rev: 1B6Q
> > usb: |
> > 1
> > versions:
> >
> > -   works:
> > 'FIXME:yes|no|partial'
> > qubes: |
> > R4.0
> > xen: |
> > 4.8.4
> > kernel: |
> > 4.14.57-2
> >   

Re: [qubes-users] HCL - Purism Librem 13 v2

2018-11-10 Thread Holger Levsen
On Sat, Nov 10, 2018 at 09:24:40AM -0800, Kyle Rankin wrote:
> It's a shame this thread got hijacked by people slandering the company.

indeed.

> PS. For what it's worth we continue to work earnestly behind the scenes to
> liberate the remaining binary blobs (FSP and what remains of the ME after
> we disable and delete the majority of the modules) because we want to
> provide people with modern hardware that runs blob-free. For the ME, we
> have already documented what we have done to attempt to both disable (HAP)
> and neuter (zero out modules) the ME. We have four ME modules remaining to
> liberate (and anyone with access to our BIOS ROM or our BIOS build script
> can confirm those claims). Those of you who work in this space are aware of
> the challenges behind all of this and if anyone wants to help us in
> liberating the FSP and the remaining four ME modules that are present we
> would certainly welcome the help.

thanks for this interesting update. Much appreciated!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

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


signature.asc
Description: PGP signature


Re: [qubes-users] HCL - Purism Librem 13 v2

2018-11-10 Thread Kyle Rankin
It's a shame this thread got hijacked by people slandering the company.
Could someone who is responsible for the HCL please update it with the data
I've provided in this thread? This would update the HCL with a version of
the Librem 13v2 that provides a TPM for people who are considering running
Qubes 4.0 with AEM.

-Kyle

PS. For what it's worth we continue to work earnestly behind the scenes to
liberate the remaining binary blobs (FSP and what remains of the ME after
we disable and delete the majority of the modules) because we want to
provide people with modern hardware that runs blob-free. For the ME, we
have already documented what we have done to attempt to both disable (HAP)
and neuter (zero out modules) the ME. We have four ME modules remaining to
liberate (and anyone with access to our BIOS ROM or our BIOS build script
can confirm those claims). Those of you who work in this space are aware of
the challenges behind all of this and if anyone wants to help us in
liberating the FSP and the remaining four ME modules that are present we
would certainly welcome the help.


On Fri, Sep 14, 2018 at 11:10:59AM -0700, Kyle Rankin wrote:
> Install works out of the box with no warnings. I haven't run into any
> issues with hardware compatibility--hardware in general works (video,
> audio, all ports, Fn keys). Hardware Kill Switches work as expected within
> Qubes.  Suspend/resume works.
> 
> By default it works with the standard included coreboot BIOS but I've also
> tested it with Heads using the TPM and that works as well.
> 
> -- 
> 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/20180914181059.fkt3blxd3heez54s%40work.
> For more options, visit https://groups.google.com/d/optout.

> ---
> layout:
>   'hcl'
> type:
>   'laptop'
> hvm:
>   'yes'
> iommu:
>   'yes'
> slat:
>   'yes'
> tpm:
>   ''
> remap:
>   'yes'
> brand: |
>   Purism
> model: |
>   Librem 13 v2
> bios: |
>   4.7-Purism-4-heads
> cpu: |
>   Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
> cpu-short: |
>   FIXME
> chipset: |
>   Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
> Bridge/DRAM Registers [8086:1904] (rev 08)
> chipset-short: |
>   FIXME
> gpu: |
>   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
> controller])
>   Intel Corporation Device [8086:9d24] (rev 21)
> gpu-short: |
>   FIXME
> network: |
>   Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
> memory: |
>   16298
> scsi: |
>   Samsung SSD 850  Rev: 2B6Q
>   Samsung SSD 850  Rev: 1B6Q
> usb: |
>   1
> versions:
> 
> - works:
> 'FIXME:yes|no|partial'
>   qubes: |
> R4.0
>   xen: |
> 4.8.4
>   kernel: |
> 4.14.57-2
>   remark: |
> FIXME
>   credit: |
> FIXAUTHOR
>   link: |
> FIXLINK
> 
> ---
> 

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


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread hmiyc
@Alex - Thank you for pointing that out.

I just tried to install version R4.0.1rc1 on the x230 again, but the 
installation breaks off when configuring ext4.  It is probably due to the HW or 
Coreboot.

I will flash my x220 with Coreboot/SeaBios + Intel ME Cleaner and install 
R4.0.1rc1 again.  Then i let you know if your tip worked.


PS.  Under Qubes 3.0/3.1/3.2 i didn't have these problems.


Greetings

Sebi

-- 
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/84e80aa2-87b8-400a-88e5-5c72783b7c0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!

2018-11-10 Thread 'awokd' via qubes-users

LMiller M:

I got sys-firewall to start green state. I cannot get fedora 26 to update.
It crashes. Debain 9 starts and updated as required. Both PC and laptop
will not let fedora update. Any suggestions?

Yes I would like to contribute to the help documentation. I will look at
the link and post what I have come across.

Thank you very much for helping.
On Sat, Nov 10, 2018 at 10:51 AM LMiller M <56lmil...@gmail.com> wrote:


Stuart!

Yes the pci device is my Nic. Thank you.. I didn’t realize sys-Firewall
had the Nic assigned to it. I removed t and the firewall started

Thank you..
On Fri, Nov 9, 2018 at 7:32 PM Stuart Perkins 
wrote:




On Fri, 9 Nov 2018 10:45:06 -0500
LMiller M <56lmil...@gmail.com> wrote:


Ok back with the laptop. During boot up, dom0 green state, sys-net green
state. WiFi connection good, and can reboot! Lol

But with that said nothing else auto loads. I have to start fedora-26 and
it will.

When trying to start sys-firewall I get error ( PCI device 02:00.0 is in
use by driver xenlight domain sys-net
Log: /var/log/libvirt/libxl/libxl-driver.log

I don’t see this log listed with sys-net, there are no logs with
sys-firewall. I don’t see this listed in the Qubes log either.

I have looked up help, but others have usb issues. I don’t have any
attached and not trying to do anything with them as stated .

I tried command qvm-pci attach —persistent —option permissive=True

—option

no-strict-reset

But I’m missing something so it’s not working. I’m in the right

direction?

I need to reset pci and set no restrictions?


On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote:


Ok so I figured out how to see the logs.

I have been able to figure out why the laptop wasn’t responding to the

OS

correctly. Now it’s working and updating as needed.

I will explain more as I learn more.

I do appreciate the guidance. I think there is more that can be shown,

to

help newbies.

I’m going to put something together from my view point to see if you

all

agree. Maybe it can be useful to all new qube users like me. Lol

anyway, I

wouldn’t have figured it out as fast for myself with out your help.

Thank you for helping me.

I’m still figuring things out, but this build is awesome and so much to
learn with it.
On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote:


Ok on first boot after install Qubes will show the kernel failure and
bypass and boot into dom0.

Once there, in the Qubes manager dom0 has green state.

Lol ok don’t laugh too hard. So I checked devices like have been,

sys-net

as you mentioned. Both Ethernet and WiFi devices are there. So I just
removed my Ethernet from device selection and bingo sys-net green

state!


So I will try now to run system updates for dom0 and fedora.

Thanks again for point things out. Sometimes you look at something so
crazy and just need a second thought.

So, can you show me how to check logs if I run into issues? Lol please
and thanks
On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users <
qubes-users@googlegroups.com> wrote:



LMiller M:

Update: Kernel failure during boot install OS 4.0

After the install booted into dom0, checking Qubes kernel package

to

see

what three were stored or available. Mine only list one kernel.

4.14.18-1

I checked using the rpm -qa ‘kernel-Qubes-vm*’

Using the install update option I get:

Unable to reset pci device :03:00.2:

Trying to apply the device to the selected box: error: device tab:

can’t

attach pci device to VM in pvh mode

Does that mode need to be changed?

Stupid question but because honestly I don’t know. How do you

check the

logs? I’m the terminal?

I downloaded the new kernel to cd, can install from the cd? I

don’t see

anything on the Qubes kernel page except download from internet

throw

Qubes. With internet I can’t.


On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com>

wrote:



So, after looking more into the kernel issue. I see on the Qubes

site

some

instructions for trying to change the kernel. I’m going to do a

reinstall

of the 4.0 os to get back into Dom0 and try it out. I will post

back

hopefully with success..
On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com>

wrote:



Ok so one more if I can please, this is on a Asus K56c laptop

and it

has

a kernel failure on boot with Qubes Os 4.0. On the first install

it

shows

the kernel failure and it boots to the OS don0. If I turn off or

reboot it

shows my kernel failure and won’t load into the os.


Glad you got your other computer working at least! So on this one,

where

are you getting this kernel failure exactly? If it's booting to dom0,
I'm not following where you're having trouble. There's a message on

boot

about failed to load kernel modules that can be safely ignored.

To update dom0, you want to use "sudo qubes-dom0-update". You should
rarely need to update the kernel by itself.

Is that when you are getting the PCI reset error? Is your sys-net
started? 

Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!

2018-11-10 Thread LMiller M
I got sys-firewall to start green state. I cannot get fedora 26 to update.
It crashes. Debain 9 starts and updated as required. Both PC and laptop
will not let fedora update. Any suggestions?

Yes I would like to contribute to the help documentation. I will look at
the link and post what I have come across.

Thank you very much for helping.
On Sat, Nov 10, 2018 at 10:51 AM LMiller M <56lmil...@gmail.com> wrote:

> Stuart!
>
> Yes the pci device is my Nic. Thank you.. I didn’t realize sys-Firewall
> had the Nic assigned to it. I removed t and the firewall started
>
> Thank you..
> On Fri, Nov 9, 2018 at 7:32 PM Stuart Perkins 
> wrote:
>
>>
>>
>> On Fri, 9 Nov 2018 10:45:06 -0500
>> LMiller M <56lmil...@gmail.com> wrote:
>>
>> >Ok back with the laptop. During boot up, dom0 green state, sys-net green
>> >state. WiFi connection good, and can reboot! Lol
>> >
>> >But with that said nothing else auto loads. I have to start fedora-26 and
>> >it will.
>> >
>> >When trying to start sys-firewall I get error ( PCI device 02:00.0 is in
>> >use by driver xenlight domain sys-net
>> >Log: /var/log/libvirt/libxl/libxl-driver.log
>> >
>> >I don’t see this log listed with sys-net, there are no logs with
>> >sys-firewall. I don’t see this listed in the Qubes log either.
>> >
>> >I have looked up help, but others have usb issues. I don’t have any
>> >attached and not trying to do anything with them as stated .
>> >
>> >I tried command qvm-pci attach —persistent —option permissive=True
>> —option
>> >no-strict-reset
>> >
>> >But I’m missing something so it’s not working. I’m in the right
>> direction?
>> >I need to reset pci and set no restrictions?
>> >
>> >
>> >On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote:
>> >
>> >> Ok so I figured out how to see the logs.
>> >>
>> >> I have been able to figure out why the laptop wasn’t responding to the
>> OS
>> >> correctly. Now it’s working and updating as needed.
>> >>
>> >> I will explain more as I learn more.
>> >>
>> >> I do appreciate the guidance. I think there is more that can be shown,
>> to
>> >> help newbies.
>> >>
>> >> I’m going to put something together from my view point to see if you
>> all
>> >> agree. Maybe it can be useful to all new qube users like me. Lol
>> anyway, I
>> >> wouldn’t have figured it out as fast for myself with out your help.
>> >>
>> >> Thank you for helping me.
>> >>
>> >> I’m still figuring things out, but this build is awesome and so much to
>> >> learn with it.
>> >> On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote:
>> >>
>> >>> Ok on first boot after install Qubes will show the kernel failure and
>> >>> bypass and boot into dom0.
>> >>>
>> >>> Once there, in the Qubes manager dom0 has green state.
>> >>>
>> >>> Lol ok don’t laugh too hard. So I checked devices like have been,
>> sys-net
>> >>> as you mentioned. Both Ethernet and WiFi devices are there. So I just
>> >>> removed my Ethernet from device selection and bingo sys-net green
>> state!
>> >>>
>> >>> So I will try now to run system updates for dom0 and fedora.
>> >>>
>> >>> Thanks again for point things out. Sometimes you look at something so
>> >>> crazy and just need a second thought.
>> >>>
>> >>> So, can you show me how to check logs if I run into issues? Lol please
>> >>> and thanks
>> >>> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users <
>> >>> qubes-users@googlegroups.com> wrote:
>> >>>
>> 
>>  LMiller M:
>>  > Update: Kernel failure during boot install OS 4.0
>>  >
>>  > After the install booted into dom0, checking Qubes kernel package
>> to
>>  see
>>  > what three were stored or available. Mine only list one kernel.
>>  >
>>  > 4.14.18-1
>>  >
>>  > I checked using the rpm -qa ‘kernel-Qubes-vm*’
>>  >
>>  > Using the install update option I get:
>>  >
>>  > Unable to reset pci device :03:00.2:
>>  >
>>  > Trying to apply the device to the selected box: error: device tab:
>>  can’t
>>  > attach pci device to VM in pvh mode
>>  >
>>  > Does that mode need to be changed?
>>  >
>>  > Stupid question but because honestly I don’t know. How do you
>> check the
>>  > logs? I’m the terminal?
>>  >
>>  > I downloaded the new kernel to cd, can install from the cd? I
>> don’t see
>>  > anything on the Qubes kernel page except download from internet
>> throw
>>  > Qubes. With internet I can’t.
>>  >
>>  >
>>  > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com>
>> wrote:
>>  >
>>  >> So, after looking more into the kernel issue. I see on the Qubes
>> site
>>  some
>>  >> instructions for trying to change the kernel. I’m going to do a
>>  reinstall
>>  >> of the 4.0 os to get back into Dom0 and try it out. I will post
>> back
>>  >> hopefully with success..
>>  >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com>
>> wrote:
>>  >>
>>  >>> Ok so one 

Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!

2018-11-10 Thread LMiller M
Stuart!

Yes the pci device is my Nic. Thank you.. I didn’t realize sys-Firewall had
the Nic assigned to it. I removed t and the firewall started

Thank you..
On Fri, Nov 9, 2018 at 7:32 PM Stuart Perkins 
wrote:

>
>
> On Fri, 9 Nov 2018 10:45:06 -0500
> LMiller M <56lmil...@gmail.com> wrote:
>
> >Ok back with the laptop. During boot up, dom0 green state, sys-net green
> >state. WiFi connection good, and can reboot! Lol
> >
> >But with that said nothing else auto loads. I have to start fedora-26 and
> >it will.
> >
> >When trying to start sys-firewall I get error ( PCI device 02:00.0 is in
> >use by driver xenlight domain sys-net
> >Log: /var/log/libvirt/libxl/libxl-driver.log
> >
> >I don’t see this log listed with sys-net, there are no logs with
> >sys-firewall. I don’t see this listed in the Qubes log either.
> >
> >I have looked up help, but others have usb issues. I don’t have any
> >attached and not trying to do anything with them as stated .
> >
> >I tried command qvm-pci attach —persistent —option permissive=True —option
> >no-strict-reset
> >
> >But I’m missing something so it’s not working. I’m in the right direction?
> >I need to reset pci and set no restrictions?
> >
> >
> >On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote:
> >
> >> Ok so I figured out how to see the logs.
> >>
> >> I have been able to figure out why the laptop wasn’t responding to the
> OS
> >> correctly. Now it’s working and updating as needed.
> >>
> >> I will explain more as I learn more.
> >>
> >> I do appreciate the guidance. I think there is more that can be shown,
> to
> >> help newbies.
> >>
> >> I’m going to put something together from my view point to see if you all
> >> agree. Maybe it can be useful to all new qube users like me. Lol
> anyway, I
> >> wouldn’t have figured it out as fast for myself with out your help.
> >>
> >> Thank you for helping me.
> >>
> >> I’m still figuring things out, but this build is awesome and so much to
> >> learn with it.
> >> On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote:
> >>
> >>> Ok on first boot after install Qubes will show the kernel failure and
> >>> bypass and boot into dom0.
> >>>
> >>> Once there, in the Qubes manager dom0 has green state.
> >>>
> >>> Lol ok don’t laugh too hard. So I checked devices like have been,
> sys-net
> >>> as you mentioned. Both Ethernet and WiFi devices are there. So I just
> >>> removed my Ethernet from device selection and bingo sys-net green
> state!
> >>>
> >>> So I will try now to run system updates for dom0 and fedora.
> >>>
> >>> Thanks again for point things out. Sometimes you look at something so
> >>> crazy and just need a second thought.
> >>>
> >>> So, can you show me how to check logs if I run into issues? Lol please
> >>> and thanks
> >>> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users <
> >>> qubes-users@googlegroups.com> wrote:
> >>>
> 
>  LMiller M:
>  > Update: Kernel failure during boot install OS 4.0
>  >
>  > After the install booted into dom0, checking Qubes kernel package to
>  see
>  > what three were stored or available. Mine only list one kernel.
>  >
>  > 4.14.18-1
>  >
>  > I checked using the rpm -qa ‘kernel-Qubes-vm*’
>  >
>  > Using the install update option I get:
>  >
>  > Unable to reset pci device :03:00.2:
>  >
>  > Trying to apply the device to the selected box: error: device tab:
>  can’t
>  > attach pci device to VM in pvh mode
>  >
>  > Does that mode need to be changed?
>  >
>  > Stupid question but because honestly I don’t know. How do you check
> the
>  > logs? I’m the terminal?
>  >
>  > I downloaded the new kernel to cd, can install from the cd? I don’t
> see
>  > anything on the Qubes kernel page except download from internet
> throw
>  > Qubes. With internet I can’t.
>  >
>  >
>  > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com>
> wrote:
>  >
>  >> So, after looking more into the kernel issue. I see on the Qubes
> site
>  some
>  >> instructions for trying to change the kernel. I’m going to do a
>  reinstall
>  >> of the 4.0 os to get back into Dom0 and try it out. I will post
> back
>  >> hopefully with success..
>  >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com>
> wrote:
>  >>
>  >>> Ok so one more if I can please, this is on a Asus K56c laptop and
> it
>  has
>  >>> a kernel failure on boot with Qubes Os 4.0. On the first install
> it
>  shows
>  >>> the kernel failure and it boots to the OS don0. If I turn off or
>  reboot it
>  >>> shows my kernel failure and won’t load into the os.
>  >>>
>  Glad you got your other computer working at least! So on this one,
> where
>  are you getting this kernel failure exactly? If it's booting to dom0,
>  I'm not following where you're having trouble. There's a message 

[qubes-users] Re: Qubes User Forum

2018-11-10 Thread Zrubi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 11/10/18 4:50 AM, Sven Semmler wrote:
> Testing to post from the forum. First impressions:
> 
> - Pretty sure I want to post from my mail client, since I like my
> stuff to be signed.

I'm fully agree with this.

> - Following a discussion might be faster in the mail client too,

That's where I would prefer a forum instead of a mail client.
However I'm not a younger one :D

And the forums has more features like
- - moderation of the posts

- - re organization of the threads.
You can make the mess more useful for others

- - topic, forum tagging

- - user/thread rating

- - you can follow selected threads, and skip the rest.
Currently I receive much more mails that I can ever read.

- - much better search possibilities.
Especially if you are not have all the mails locally.


> - If this POC gets legs, it would be very useful if the software
> would become GPG/PGP aware (as in verifying signatures and hiding
> the actual signatures)


That's would be awesome!
This forum engine is open source, and prepared for plugins.
So, contributions are welcome ;)



- -- 
Zrubi
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEmAe1Y2qfQjTIsHwdVjGlenYHFQ0FAlvm/hoACgkQVjGlenYH
FQ1SXA//XB2KnzZfcKURO4+QTohLlS7MBymm8Kz+boEjC/UVz1AyLSUTkIof07qi
LcQxTWH6+ajQf60WUDV0opynF+Vy3TpF+wWOu6Z3uGsXxObwHBYtyLQIT+QT20Lg
uz4g/lnlBHMrwxj2//QtyXUgk2Q0nNDNp8p/7OHOqahyRnMVAhvZL835jAyKP3jA
favna9UGtyiQNOxW0pDMuxRz1+hmc3YhHdL3+Wf2sSErrlyAh9pAUi9Eo8vjhbRg
xNQ4vFE53qnCq+KzurQi6T0O1ZWLGTs8vYjTHoYHFowFfSl0srJhojA2DkDmh4Gl
3/bGz+74fP+KdPn4GD8i11LUGKVbOhgx8Jyo+00fEfYVPT4+1kXmFkQkQhIDQfpA
XcBbPfWgwlZ/dB/9GNXzHHxwE+1L35DdRzVYHmjd9PPj5LFHY/Z03hr3orb2lmLS
Hiu4Zhuli/05ZsNsQoh9GMPhKnHPV/v6pQTe2+ERPCNl64C6pLM9+tNZg8UVY/BD
4g3Q3uB4ozYD6U7CavTAK+LeFgC5AF70KkqBlyEpbRVXdRRsdePUI+2BXyI3XhXx
YOkE/Xk/xntRNlS+828AVjs/g8g3+h4vY+2O43tKJhZf0D+Cinz8gUi/1nDrOcM6
CyFKllrFB2/wh3f00sqB+itNFI3fILnJqjNw76nzuqH5SsrYo6A=
=/5Qj
-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/73274931-a0e5-4adb-edf9-746cf6348acf%40zrubi.hu.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!

2018-11-10 Thread 'awokd' via qubes-users

LMiller M:

Ok so I figured out how to see the logs.

I have been able to figure out why the laptop wasn’t responding to the OS
correctly. Now it’s working and updating as needed.

I will explain more as I learn more.

I do appreciate the guidance. I think there is more that can be shown, to
help newbies.

I’m going to put something together from my view point to see if you all
agree. Maybe it can be useful to all new qube users like me. Lol anyway, I
wouldn’t have figured it out as fast for myself with out your help.

Thank you for helping me.

I’m still figuring things out, but this build is awesome and so much to
learn with it.


There is definitely a learning curve to Qubes. On some hardware the 
steepest part can unfortunately be right in the beginning with the 
install. Glad you're making progress! If you want to help contribute to 
the documentation, check out https://www.qubes-os.org/doc/doc-guidelines/.


--
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/c018f247-7163-c63b-abbe-2b2d1dd13e69%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Thinkpad T400s RYF

2018-11-10 Thread 'awokd' via qubes-users

qubes-...@tutanota.com:

Hi, I am thinking about getting the RYF T400s for Qubes 4. Is there anyone here 
who is running the T400s successfully with Qubes 4? If yes, how is the 
install/setup?

https://tehnoetic.com/tet-t400s 

It's a respectable piece of hardware, but I think it is too old to 
support the hardware virtualization (VT-d) Qubes 4.0 requires.


--
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/8d3d3601-b64e-77c5-3740-f89e41321b37%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Fedora > 26 can not attach encrypted usb key

2018-11-10 Thread 'awokd' via qubes-users

Cranix:

Hello
I was on fedora-26 template and everything was OK.
Because fedora 26 is pretty old right now i installed fresh template
fedora 29 (tried 27 and 28 and had this same problem too).

I have appvm and i attach my usb key to it via sys-usb.
Then when i run sudo cryptsetup luksOpen /dev/sda1 flash
first shell did not find completion for luksOpen command,
then in best case i got message that crypsetup is killed.
In worse case whole vm crashes and requires manuall kill and start.

I tried to search for any information but duckduckgo, startpage
and google can not find any helpful information.

I ran out of ideas what is going on i can past logs,
just please tell me what will be usefull.

Thanks in advance for help.

If you are using qvm-usb to attach the key, try using qvm-block instead 
to only attach the partition. Then, inside the AppVM, do your cryptsetup 
against /dev/xvdi. Qvm-usb should work too, but maybe there's a bug. 
Qvm-block is preferable anyways.


--
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/d0bd30a9-11c2-df56-3003-38c564462daa%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Get help with HNS VM installation error

2018-11-10 Thread 'awokd' via qubes-users

gdru...@gmail.com:

Hi,

I'm trying to install a VM in HVM mode called HNS (hybrid network simulation).

Based on Debian, HNS seems to run on KVM/QEMU.


Running a hypervisor like KVM inside another hypervisor like Xen is 
known as "nested virtualization". This is disabled and not supported in 
Qubes.


--
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/88b0b65e-3c8d-8838-010b-314966c29d02%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] GRUB upgrade debian-9 - what device to install it on

2018-11-10 Thread unman
On Sat, Nov 10, 2018 at 02:56:13PM +0100, qubes-...@tutanota.com wrote:
> Hi, I downloaded the debian-9 update which includes the GRUB upgrade. It asks 
> me to decide where to install it. What device should I take? I run on Qubes 4.
> 
> /dev/xvda
> /dev/xvdb
> /dev/xvdc
> /dev/xvdd
> /dev/xvda3
> 
> Thank you

Unless you have kernel set to "none", and are booting *from* the qube,
early stage boot is controlled by Qubes.
You can set to /dev/xvda without issue, as that is the base root device
in the templates.

unman

-- 
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/20181110151958.fh6tw7lpwilrgufj%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes OS 4.0, full screen and HVM domain

2018-11-10 Thread unman
On Sat, Nov 10, 2018 at 09:51:39AM +0100, GDRUB wrote:
> Le 09/11/2018 à 15:20, unman a écrit :
> > On Fri, Nov 09, 2018 at 01:11:53AM -0800, gdru...@gmail.com wrote:
> > > Hi,
> > > 
> > > I'm trying to enable full screen mode two standalone VM(s).
> > > 
> > > The following modus operandi does not work : 
> > > https://www.qubes-os.org/doc/full-screen-mode/
> > > 
> > > No error displayed and no change right-clicking on a window’s title bar 
> > > and selecting "Fullscreen".
> > > 
> > > How can I fix it ?
> > > 
> > > Any help and advice would be greatly appreciated.
> > > 
> > > Best regards.
> > > 
> > > GD Rub
> > > 
> > You dont say what the standaloneVMs are:
> > On a Debian based HVM the simplest thing to do (under Xfce) is to set
> > the display size in the HVM to that of the screen (or larger) and then 
> > select
> > Fullscreen from the title bar.
> > The same works in a Windows HVM.
> > 
> > That works for me.ymmv
> > 
> > 
> > 
> > 
> Hi,
> 
> Thanks so much. VMs Kali & Hynesim based based on Debian ;-)
> 
> Frustrating how the answer was so simple. I searched for a long time and
> found nothing.
> 
> GD Rub
> 

Glad to help.
I should add it to the docs, perhaps.

unman

-- 
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/20181110150036.el6ojovm22fjxfuk%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Dell Inspiron 13 5387 - Qubes 4.0

2018-11-10 Thread als . alsx
Hello guys,

Did awokd's suggestion work? I'm about to get that same laptop and it'd be 
really important for me to know if the problem of the crashing HVMs could be 
circumvented.

Thanks for your help,

On Tuesday, May 1, 2018 at 4:46:16 AM UTC-3, NaBaCo wrote:
> On 04/30/18 15:47, donoban wrote:
> > On 04/30/18 14:20, NaBaCo wrote:
> >> 1. I'm unable to start HVM from ISO's. They all crash while
> >> loading.
> > 
> > Check 'qvm-prefs VM', kernel should be empty.
> > 
> >>
> 
> Did that. In most ISOs I manage to boot up to the GRUB, and begin the
> boot process, and that's when it crashes.
> 
> I'll be glad to post logs if told which ones.
> 
> --
> NaBaCo.

-- 
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/ff39c2e7-2282-46da-96b1-80eee5005ec2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] update broke whonix, can't reinstall

2018-11-10 Thread birdynam
Hi, 
this is the way i've updated my whonix on R4.
Hope it'll help.

https://www.militant.dk/category/linux/qubes-os/

Birdy.


-- 
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/11733142-1cba-1be2-faf4-eefe1e7d703d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature


[qubes-users] Thinkpad T400s RYF

2018-11-10 Thread qubes-fan
Hi, I am thinking about getting the RYF T400s for Qubes 4. Is there anyone here 
who is running the T400s successfully with Qubes 4? If yes, how is the 
install/setup?

https://tehnoetic.com/tet-t400s 

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


[qubes-users] GRUB upgrade debian-9 - what device to install it on

2018-11-10 Thread qubes-fan
Hi, I downloaded the debian-9 update which includes the GRUB upgrade. It asks 
me to decide where to install it. What device should I take? I run on Qubes 4.

/dev/xvda
/dev/xvdb
/dev/xvdc
/dev/xvdd
/dev/xvda3

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


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread Alex
On 11/10/18 11:23 AM, hm...@tuta.io wrote:
> hello
> 
> I have exactly the same problem on two of my x230 Lenovo notebooks with Qubes 
> version R4.0.1rc1.
Have had this very issue on R4.0.

I checked by running, in dom0:
# qubes-dom0-update -v

That runs the dnf updater with the "-v" verbose flag. With that, the URL
for the repositories will be printed on screen, in red (because it's
happening in the UpdateVM).

I found that the URL being printed was
https://yum.qubes-os.org/r25-4/current/dom0/fc25/repodata/repomd.xml.metalink

instead of the correct
https://yum.qubes-os.org/r4.0/current/dom0/fc25/repodata/repomd.xml.metalink

(the yum.qubes-os.org domain can be navigated with a browser).

I found that inside [dom0]/etc/yum.repos.d/qubes-dom0.repo the url is
saved as
https://yum.qubes-os.org/r$releasever/current/dom0/fc25/repodata/repomd.xml.metalink

Changed that with nano to read "4.0" instead of "$releasever" and voilà,
updates went through.

Check, try and let the list know ;)

-- 
Alex

-- 
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/90d6b896-f532-519a-cffd-bcdafe509eb8%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Fedora > 26 can not attach encrypted usb key

2018-11-10 Thread Cranix
Hello
I was on fedora-26 template and everything was OK.
Because fedora 26 is pretty old right now i installed fresh template
fedora 29 (tried 27 and 28 and had this same problem too).

I have appvm and i attach my usb key to it via sys-usb.
Then when i run sudo cryptsetup luksOpen /dev/sda1 flash
first shell did not find completion for luksOpen command,
then in best case i got message that crypsetup is killed.
In worse case whole vm crashes and requires manuall kill and start.

I tried to search for any information but duckduckgo, startpage
and google can not find any helpful information.

I ran out of ideas what is going on i can past logs,
just please tell me what will be usefull.

Thanks in advance for 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/20181110110608.GA14384%40hackerspace.pl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread hmiyc
hello

I have exactly the same problem on two of my x230 Lenovo notebooks with Qubes 
version R4.0.1rc1.


I suspected it might be Coreboot/SeaBios, but obviously it's not.

Greetings

-- 
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/71e24526-8103-4230-b722-9c755b45fcf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Fresh install Failed to synchronize cache for repo 'qubes-dom0-current' and 'qubes-templates-itl'

2018-11-10 Thread hmiyc
hello

I have exactly the same problem on two of my x230 Lenovo notebooks with Qubes 
version R4.0.1rc1.


I suspected it might be Coreboot/SeaBios, but obviously it's not.

Greetings

-- 
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/ec719a5f-4446-4419-8a10-6f7d3815e3ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Ledger Nano S works great with Qubes OS R3.2 [Debian 8 and Fedora 24 AppVMs]

2018-11-10 Thread hmiyc
hello

It also works with R4.0 and R4.0.1rc1.

Greetings

-- 
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/654d97f1-c2a9-430e-823a-7fb7437948f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Get help with HNS VM installation error

2018-11-10 Thread gdrub51
Hi,

I'm trying to install a VM in HVM mode called HNS (hybrid network simulation). 

Based on Debian, HNS seems to run on KVM/QEMU.

I followed the step-by-step installation instructions : 
https://www.hynesim.org/installation-pas-a-pas/

Edit /etc/hynesim/hynesim-node.ini

Add support for KVM/QEMU :

KvmQemu/dummy = 1

I am having an issue relating to kvm_intel module into the Qubes OS 4.0 
environment. 

Cleanup prior to restarting the hynesim-node service :

$ /etc/init.d/hynesim-node cleanup
[...]
Failed to stop vboxdrv.service: Unit vboxdrv.service not loaded.
modprobe: ERROR: could not insert 'kvm_intel': Operation not supported
Module unloading failed: kvm_intel
[...]

How can I fix it ?

Any help and advice would be greatly appreciated.

Best regards.

GD Rub 

-- 
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/97ca9638-d000-4964-b90d-00454733ccbd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes OS 4.0, full screen and HVM domain

2018-11-10 Thread GDRUB

Le 09/11/2018 à 15:20, unman a écrit :

On Fri, Nov 09, 2018 at 01:11:53AM -0800, gdru...@gmail.com wrote:

Hi,

I'm trying to enable full screen mode two standalone VM(s).

The following modus operandi does not work : 
https://www.qubes-os.org/doc/full-screen-mode/

No error displayed and no change right-clicking on a window’s title bar and selecting 
"Fullscreen".

How can I fix it ?

Any help and advice would be greatly appreciated.

Best regards.

GD Rub


You dont say what the standaloneVMs are:
On a Debian based HVM the simplest thing to do (under Xfce) is to set
the display size in the HVM to that of the screen (or larger) and then select
Fullscreen from the title bar.
The same works in a Windows HVM.

That works for me.ymmv





Hi,

Thanks so much. VMs Kali & Hynesim based based on Debian ;-)

Frustrating how the answer was so simple. I searched for a long time and 
found nothing.


GD Rub

--
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/9344b393-1d59-316f-6c66-51040b35a65d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.