date:20180317

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-03-17 15:10, Andrew David Wong wrote:
> On 2018-03-17 15:07, socks wrote:
>> On 03/17/2018 08:37 AM, socks wrote:
>>> I'm sure it's the newb in me, but I'm trying to verify the rc5.iso and
>>> getting stuck here:
>>>
>>> https://www.qubes-os.org/security/pack/
>>>
>>>
>>> Step 4.
>>>
>>> Verify signed Git tags.
>>>
>>> |$ cd qubes-secpack/ $ git tag -v `git describe` I get "object not
>>> found" proceeding in the /canaries , it's ok |
>>>
>>>
>> Intriguingly I also get this :
> 
> 
>> desktop ~/Downloads/Qubes-R4.0-rc5-x86_64 $ md5sum -c
>> Qubes-R4.0-rc5-x86_64.iso.DIGESTS
>> Qubes-R4.0-rc5-x86_64.iso: OK
>> md5sum: WARNING: 22 lines are improperly formatted
> 
> 
>> so:  is this .iso  OK  or ?
> 
> 
> That's normal:
> 
> https://ask.fedoraproject.org/en/question/10956/checksum-verification-error-message-is-mysterious/
> 

By the way, this is already thoroughly explained in our documentation:

https://www.qubes-os.org/security/verifying-signatures/#verifying-digests

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqt7MMACgkQ203TvDlQ
MDB7zg/+L51BthFM82dgxFzXqRjR3ecJyv+xSN/G3GgSHxW/93pD4SDwfhBf9vB5
2dk1zztAMCG6x+ssemfNn+N/tV25DaLMeOeFhmanI5RKUhaXj3u/5KIarQvz38DP
0bwMpFX5XjPBsby/5WHeR/wCuMmf0Plj1sBeLUI9y8Y/ZeNKOON4uts60DzuYb/d
Kvfht0xKxAf1+rPVWRHkJLNv1N3uF+zxovs7cLQwS7rx2FlFbCa9Xne1QRpc93+2
9kT1YWzSuV8xraaRkjzlaOCu0fak5mlScWbAQLGHqBykR6hKGX7ydjDXWHn1tN4+
tHHmTRuuiiiJ87p70BG9e4ngx4or+3BiLfkc02772vN6jRnki0a9t4+xXCObKWrJ
JqtBo7F/OrszJYoQhHotllZBxv4sGIOdh/5Mv+U3z53si/ErywrClT871CC2SUwQ
Xo7Fn0GfnAq4vOha4RBV8uJxQo6tVqDxjP4Djcciu40/F1DfTydNh7yD4KI0/fI3
FJFa0HIQaxtoQNEjGoa8AkkYJgQJEzWxGrfPZDwBrNTQ/0h4bYMDljabHmhNpQyb
jwRDEz7SzmZy0YLRPvFOQumYvYFVgWF/A8Ke2ficwTPJBMRckGx1LDEvESCgdJke
SACPgjUISfPbq+lkgzTPO0C23ebGn+Ycd5ClpsHKvsUzajDBMYk=
=fnym
-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/eca4c97c-207d-3bf6-b311-d2617ecc6d96%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Macbook Pro - Broadcom WLAN adapter BCM43602 causing freezing under Qubes OS 4.0 rc5

2018-03-17 Thread Greg

On Friday, March 16, 2018 at 2:11:06 PM UTC+2, c... wrote:
> пятница, 16 марта 2018 г., 5:19:41 UTC+3 пользователь Greg написал:
> > Hi,
> > 
> > Please assist if possible - I'm trying to get the Broadcom WLAN adapter 
> > BCM43602 working on my Macbook Pro under Qubes OS 4.0 rc5. 
> > 
> > "03:00.0 Network controller: Broadcom Limited BCM43602 802.11ac Wireless 
> > LAN SoC (rev 01)"
> > 
> > I've managed to install Qubes OS successfully (during the second part of 
> > setup, just before sys-net creation I switched to a console and started a 
> > short bash script that just loops over and over trying to remove the 
> > BCM43602 from sys-net, then I went back and completed the setup. The script 
> > successfully removed the BCM43602 from sys-net before sys-net was started 
> > by the setup wizard, meaning that I managed to avoid the system freeze that 
> > would have otherwise occurred during setup).
> >  
> > Now I'm trying to actually get the BCM43602 working, i.e. attach the 
> > adapter to a qube (e.g. sys-net, standalone hvm or anything at all without 
> > freezing). However it seems that the system freezes the moment I start the 
> > qube it is attached to and it doesn't matter which kernel the associated 
> > qube is actually running (e.g. it freezes even when I attach it to a qube 
> > that is a fresh Ubuntu 17.10 install with hvm and no kernel seleced). I've 
> > tried different combinations of permissive mode and no-strict-reset and 
> > pv/hvm but every combination results in freezing. 
> > 
> > I'm not sure how to proceed? Does anyone have the BCM43602 working under 
> > 4.0 rc5?
> > 
> > Any pointers would be appreciated.
> > 
> > Thanks,
> > Greg
> 
> Try to start sys-net without attached devices, after that attach adapter 
> directly:
> sudo xl pci-attach sys-net '03:00.0,permissive=1'
> That helped for me.
> qvm-pci for some reason freezes my macbook
> 
> cheers

Using "sudo xl pci-attach sys-net '03:00.0,permissive=1'" to attach the adapter 
to sys-net (after starting it first) works great. At least I can now attach the 
adapter to a qube without freezing my system.

Thanks so much for the suggestion.

-- 
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/03bd6681-6854-4c3d-b2c6-3f26de2d4166%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?

On Sat, Mar 17, 2018 at 11:52:00PM +, qubes-li...@riseup.net wrote:
>  What would be the step to downgrade to the previous version to
>  get dispVMs working again?
> 
>  qubes-dom0-update --action=downgrade xen something like this or is it
>  necessary to specify all packets individually?
> >>>
> >>> Depending on how attached you are to Fedora, you might want to temporarily
> >>> try the Debian template instead of downgrading Xen?
> >>
> >>
> >> I get the same error after switching to debian-9 as the dispVM template.
> >>
> >> So switching to debian-9 for dispVM is unfortunately _not_ a possible 
> >> workaround for this.
> > 
> > You're using Testing arent you?
> 
> Yes, to be precise: 
> 
> qubes-dom0-current-testing is _not_ enabled.
> 
> qubes-dom0-security-testing _is_ enabled.
> 
> 
> > You could downgrade to the 36 version of xen-libs and runtime etc. That
> > should fix your problem until 6-38 is released
>  
> What would be the recommended way of downgrading? (and wouldn't it be
> better to revert all packages of the given upgrade?)
> 
> qubes-dom0-update --action=downgrade xen-libs xen-runtime xen-hvm
> 
> Maybe lets add generic downgrade instructions for such cases (dom0) to the 
> documentation?

I would just downgrade the Xen packages to start.

There are already instructions here:
https://www.qubes-os.org/doc/software-update-dom0/

Look at the section on downgrading a specific package.

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

Re: [qubes-users] Using postgresql database in qubes(AppVM)

On Fri, Mar 16, 2018 at 10:24:34PM -0700, redleopar...@gmail.com wrote:
> Hello!
> As a web developer, I was using Arch linux as development os then I got to 
> know qubes os, and really hooked it.
> 
> I almost finished setting up my qubes os as Web development os. But I finally 
> found out 1 problem. that is database.
> 
> Postgresql database's data location is (normally) /var/lib/pgsql/10/data
> As I learned, AppVM's folder will be reset every time I start. (except /home)
> 
> So I am thinking about the solution, first, I just create every database that 
> need for my project in TemplateVM, so I can see it my Dev AppVM
> 
> Is there anyone using qubes os as web development os?
> Is there any best practice for this case?
> 
> Please help me!
> 

Why not use bind-dirs, which is intended for exactly this sort of case.
It's documented here:
https://www.qubes-os.org/doc/bind-dirs/


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

[qubes-users] HCL Compal pbl21

2018-03-17 Thread stephen smith

The only thing I have had issue with is the onboard wifi. Qubes does not 
recognize it. I polugged in a USB wifi and it works perfectly

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


Qubes-HCL-Compal-PBL21-20180317-200017.yml
Description: application/yaml


Qubes-HCL-Compal-PBL21-20180317-201030.cpio.gz
Description: application/gzip

Re: [qubes-users] DispVM broken in 3.2?

 What would be the step to downgrade to the previous version to
 get dispVMs working again?

 qubes-dom0-update --action=downgrade xen something like this or is it
 necessary to specify all packets individually?
>>>
>>> Depending on how attached you are to Fedora, you might want to temporarily
>>> try the Debian template instead of downgrading Xen?
>>
>>
>> I get the same error after switching to debian-9 as the dispVM template.
>>
>> So switching to debian-9 for dispVM is unfortunately _not_ a possible 
>> workaround for this.
> 
> You're using Testing arent you?

Yes, to be precise: 

qubes-dom0-current-testing is _not_ enabled.

qubes-dom0-security-testing _is_ enabled.


> You could downgrade to the 36 version of xen-libs and runtime etc. That
> should fix your problem until 6-38 is released
 
What would be the recommended way of downgrading? (and wouldn't it be
better to revert all packages of the given upgrade?)

qubes-dom0-update --action=downgrade xen-libs xen-runtime xen-hvm

Maybe lets add generic downgrade instructions for such cases (dom0) to the 
documentation?

-- 
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/720d2245-2082-d12e-2d79-7abbe485b90c%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] unexpected hard reboot on xen-4.6.6-37 (in security-testing repo)

Hi,

this is just a warning for those that have qubes-dom0-security-testing enabled
and did not upgrade yet.

Besides breaking dispVM functionality [1] I also had a strange
unexpected hard reboot since I upgraded to xen-4.6.6-37.
I don't know the root cause of the reboot but it _might_ be related
to the xen update. 


So if you enabled the dom0 security-testing repo you might want to
avoid upgrading just yet.




[1] https://github.com/QubesOS/qubes-issues/issues/3711

-- 
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/6fa1fbd5-17d4-364a-b805-8a4993280f15%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?

On Sat, Mar 17, 2018 at 08:13:00PM +, qubes-li...@riseup.net wrote:
> 
> 
> awokd:
> > On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote:
> > 
> >> What would be the step to downgrade to the previous version to
> >> get dispVMs working again?
> >>
> >> qubes-dom0-update --action=downgrade xen something like this or is it
> >> necessary to specify all packets individually?
> > 
> > Depending on how attached you are to Fedora, you might want to temporarily
> > try the Debian template instead of downgrading Xen?
> 
> 
> I get the same error after switching to debian-9 as the dispVM template.
> 
> So switching to debian-9 for dispVM is unfortunately _not_ a possible 
> workaround for this.

You're using Testing arent you?

You could downgrade to the 36 version of xen-libs and runtime etc. That
should fix your problem until 6-38 is released

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

[qubes-users] Re: Using postgresql database in qubes(AppVM)

2018-03-17 Thread Yuraeitha

On Saturday, March 17, 2018 at 6:24:34 AM UTC+1, Taehwan Kim wrote:
> Hello!
> As a web developer, I was using Arch linux as development os then I got to 
> know qubes os, and really hooked it.
> 
> I almost finished setting up my qubes os as Web development os. But I finally 
> found out 1 problem. that is database.
> 
> Postgresql database's data location is (normally) /var/lib/pgsql/10/data
> As I learned, AppVM's folder will be reset every time I start. (except /home)
> 
> So I am thinking about the solution, first, I just create every database that 
> need for my project in TemplateVM, so I can see it my Dev AppVM
> 
> Is there anyone using qubes os as web development os?
> Is there any best practice for this case?
> 
> Please help me!

or to make it even easier, by using the cups example inside the file, is to 
just put your data at /rw/config/data and then symbolic link it to 
/var/lib/pgsql/10/data

Then all your data is kept in /rw/config/data but the system believes its at 
/var/lib/pgsql/10/data

By using /rw/config as a place to store your folders, then it also becomes more 
easy to keep overview of everything, rather than clustering it all in folders 
in various different directions (keep it simple).

-- 
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/0eda79b5-a17a-43bb-999c-397cd6424f34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Using postgresql database in qubes(AppVM)

2018-03-17 Thread Yuraeitha

On Saturday, March 17, 2018 at 6:24:34 AM UTC+1, Taehwan Kim wrote:
> Hello!
> As a web developer, I was using Arch linux as development os then I got to 
> know qubes os, and really hooked it.
> 
> I almost finished setting up my qubes os as Web development os. But I finally 
> found out 1 problem. that is database.
> 
> Postgresql database's data location is (normally) /var/lib/pgsql/10/data
> As I learned, AppVM's folder will be reset every time I start. (except /home)
> 
> So I am thinking about the solution, first, I just create every database that 
> need for my project in TemplateVM, so I can see it my Dev AppVM
> 
> Is there anyone using qubes os as web development os?
> Is there any best practice for this case?
> 
> Please help me!

There is a 4th option to the 3 options above, which is changing the specific 
folder at /var/lib/pgsql/10/data and allow it to become persistent in in this 
location /rw. The /rw folder stays persistent, and it's also here you'll find 
everything else that is staying persistent in the AppVM's. 

Changing what stays persistent and what doesn't is actually quite easy to do 
too, but be aware it adds yet another folder which can be exploited to attacks, 
so if you can use the option 1) awokd mention up above, then it'll be more 
secure.

Basically how it works, is that it'll start the full template, then it'll 
remove the symbolic links to the specific folders you want to be persistent 
(that means, the default template folders are cut-away), and then it'll change 
the symbolic link to the persistent folder. Generally, I believe, this is how 
AppVM's work in general, however, you can modify it to include or exclude 
specific folders, as you desire.

Use a terminal text editor, like nano, and edit this file '/rw/config/rc.local'
Instructions how to do this is included in the Qubes file, it's using Cups as 
an example how to do it, just do the same for your specific folder instead of 
Cups.

Remember the systemctl restart is only needed if you're changing a service or 
module driver, it might not be relevant for your needs. So you only need the 
"rm" template folder line, and the "ln -s" add new symbolic link line to a 
replacement folder.

Remember your "/var/lib/pgsql/10/data" content, now will be inside a folder you 
placed somewhere suitable in the /rw folder, for example 
/rw/var/lib/pgsql/10/data, which then will act as if it was at the real 
destination.

-- 
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/8ce9e42d-a749-4d1e-a88f-ca28a752a9cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Using postgresql database in qubes(AppVM)

On Sat, March 17, 2018 5:24 am, redleopar...@gmail.com wrote:
> Hello!
> As a web developer, I was using Arch linux as development os then I got to
> know qubes os, and really hooked it.
>
> I almost finished setting up my qubes os as Web development os. But I
> finally found out 1 problem. that is database.
>
> Postgresql database's data location is (normally) /var/lib/pgsql/10/data
> As I learned, AppVM's folder will be reset every time I start. (except
> /home)
>
>
> So I am thinking about the solution, first, I just create every database
> that need for my project in TemplateVM, so I can see it my Dev AppVM
>
> Is there anyone using qubes os as web development os?
> Is there any best practice for this case?

Not sure about best practice, but I see 3 approaches:
1. Do like you're doing and install them all in a template, but don't
forget anything written to them will be reverted on AppVM shutdown.
2. Change Postgresql to install them to /home. Then you can have a
different database in every AppVM.
3. Use a standalone template instead.


-- 
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/e5ccc9145f862be97c97d51d0bace4d8.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: mouse lagging with sys-usb in Qubes 3.2

2018-03-17 Thread Yuraeitha

On Saturday, March 17, 2018 at 8:14:02 PM UTC+1, snowbo...@gmail.com wrote:
> Since I created a sys-usb device and connected the mouse with passthrough to 
> dom0 (I answered yes the first time) the mouse is lagging significantly. I 
> even changed the attributes from mouse properties from the GUI menu but 
> nothing happens. It's a laptop so touchpad is working perfectly.
> 
> Why does it lag so much?
> 
> Output of qubes.InputMouse:
> 
> sys-usb dom0 allow,user=root
> $anyvm $anyvm deny

By any chance are you using current-testing repositories? and if so, did you 
update all your templates with current-testing repositories too? If only dom0 
is updated, or if not keeping the updates in sync between dom0/domU, then it 
might cause smaller issues, i.e. it might be possible to cause an issue like 
this one. 

It's not exclusive current-testing either, however it's more easy to make the 
update-sync mistake for current-testing updates. In general every Qubes update 
repository must stay in sync across the whole system.

-- 
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/ca1086a0-468e-41d7-a40f-17938df22b2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Coreboot + Qubes :: Best Practises / Coreboot docs page

2018-03-17 Thread Rusty Bird

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

799:
> Seabios or Grub and are there any special options which might make sense?

SeaBIOS is nice. You can build it with CONFIG_SEABIOS_VGA_COREBOOT=y
(might be the default now), and completely disable dynamic loading of
any dubious option ROMs:

$ build/cbfstool build/coreboot.rom add-int -i 0 -n etc/pci-optionrom-exec

That's incompatible with graphical mode GRUB, but you can simply
change GRUB_TERMINAL_OUTPUT from "gfxterm"[1] to "console"[2] in
/etc/default/grub and rerun 'grub2-mkconfig -o /boot/grub2/grub.cfg'.

IMO it actually looks better - no blindingly bright blue light at
night, and fewer font changes during startup. I've been meaning
(forever) to open a pull request to make this the default...

You might also enjoy HEADS[3].

Rusty


1. https://image.ibb.co/jGvCCx/grub_gfxterm.png
2. https://image.ibb.co/mbnsCx/grub_console.png
3. https://github.com/osresearch/heads
-BEGIN PGP SIGNATURE-

iQJ7BAEBCgBmBQJarZQ6XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfSKUP+NrPMBRzFqbxr7ciUg/Qnh9m
5ykQ4unpLU9CfiAotMDo7xJdjEZA7lwTeloVtsPL1GeVPTpYuFbkX2rxjSUQAb7H
JSWUxTZOU2YjNjQfOz+W/Wnb0uHK9G8a5h2Pf9v8lEW5/Z3iGeTeOiSSjSc6OJjw
Nn9ycrr2m6PvcM14OZ5DqnISdKKogUZBz+9TemhPVgSogA1RpsB9GRHgUcDermgs
D7T62f2Bs79suOMwRDM/IZ6f4MNvsSF1pFSN+xE3JOpivx+xfAgBlc///vsz7dM2
05hqyVLoeCs6qHwe2PtbBlHfLdfPVoaC/kwQRDV8Obj9hP4/CFnQkRDyvN1dnwDi
lV27YYcuWE0lgfsuRW9PwAySzyxEa4OYyDNDEJYW20lB8eTYsusDJAxxiM0X+Ba9
pxf1FQwRoX7C4yjHU1tWb97cTPOMif07O8a5AFod9FPAwmUcwdPC/X/H3eU2CsaP
UP5NEK81Wx1avWdTIBuvrbuPZe5Dj0dwTk0Z5TC5hbKUMYxczDLuFnh/1TnViSRo
4pOUNfXx4Blg4elUrTXASOnPQnZA5X2snVhkQrmqi3nAyRztzTK6x++OqvjlF+q3
T8YiSg66Ssi3iXUFiZlEerCfzpe0Wc+kyvVXh9sM0NhwBs6hErLpmSlLD3785Bxr
P5Lc8JEJpNcnac70K0c=
=L0qD
-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/20180317221835.GA2170%40mutt.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?

On Sat, March 17, 2018 8:13 pm, qubes-li...@riseup.net wrote:

> I get the same error after switching to debian-9 as the dispVM template.
>
>
> So switching to debian-9 for dispVM is unfortunately _not_ a possible
> workaround for this.

I saw Marek confirmed it's a Xen issue too. Thanks for trying it anyways,
and for the heads up!



-- 
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/5ab326d23ae46a73039c116e39658aab.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?

2018-03-17 Thread Marek Marczykowski-Górecki

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, Mar 17, 2018 at 08:04:34PM -, 'awokd' via qubes-users wrote:
> On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote:
> 
> > What would be the step to downgrade to the previous version to
> > get dispVMs working again?
> >
> > qubes-dom0-update --action=downgrade xen something like this or is it
> > necessary to specify all packets individually?
> 
> Depending on how attached you are to Fedora, you might want to temporarily
> try the Debian template instead of downgrading Xen?
> 
> I'm still on -36 so can't confirm...

I think it wouldn't help. It looks like something is broken in Xen, not
in template.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqm/ksACgkQ24/THMrX
1yyvcgf+MPUg0EmPMiT3RhPz2D2lz+CNrVlWsqgnlUPYc2RSYDAZeMZiSM/JUEOp
eAwYYDekz47iWeoVgiuwvv28swlTMMw71kNQcgBR8ZndoBLjPFR/oLG9yr5RP/bI
HhO8gb5TlZai7WWV8/TDbiJ0FHR2WczqD5oXBkcr1+lB6YxsiK6eXmnHbiTRSnvU
8SINDfVoeJhJuXKjUuFK7DddP+Bdoq7UfdRwg1ajqiowrZgItHhxt3Bq0Si+M1rF
Ppo5Hw/vW3LWuy+q1EkhooQX+0hglOaElnbgWyes0iyt04QJdPYShvoQ2qyUnvfK
I+r3ncgZoVmXFDfpDXE0VcixKMt32A==
=4fa7
-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/20180317201430.GE8712%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?



awokd:
> On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote:
> 
>> What would be the step to downgrade to the previous version to
>> get dispVMs working again?
>>
>> qubes-dom0-update --action=downgrade xen something like this or is it
>> necessary to specify all packets individually?
> 
> Depending on how attached you are to Fedora, you might want to temporarily
> try the Debian template instead of downgrading Xen?


I get the same error after switching to debian-9 as the dispVM template.

So switching to debian-9 for dispVM is unfortunately _not_ a possible 
workaround for this.

-- 
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/0f840e7d-5614-5db5-5338-33f436c84fc0%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Dependency error building Qubes

On Sat, March 17, 2018 8:07 am, 'awokd' via qubes-users wrote:
> On Thu, March 15, 2018 5:41 pm, voitsovic...@gmail.com wrote:
>
>> воскресенье, 11 марта 2018 г., 23:22:41 UTC+2 пользователь
>> rucksac...@googlemail.com написал:
>>> I'm trying to build a Qubes ISO on a Fedora 26 System, following the
>>> instructions of the documentation page "Building Qubes OS ISO", and
>>> get this error message:
>>>
>>> make[1]: Entering directory '/home/xy/qubes-builder'
>>> sudo chroot /home/xy/qubes-builder/chroot-fc25 dnf install -y
>>> gcc-6.4.1-1.qubes1.fc25.x86_64 libgcc.x86_64 Qubes OS Builder
>>> Repository
>>> 251 kB/s | 257  B 00:00
>>> No package gcc-6.4.1-1.qubes1.fc25.x86_64 available.
>>> Package libgcc-6.4.1-1.fc25.x86_64 is already installed, skipping.
>>> Error: Unable to find a match.
>>> make[1]: *** [qubes-src/vmm-xen/Makefile.builder:27:
>>> workaround-gcc-upgrade-fc25] Error 1 make[1]: Leaving directory
>>> '/home/xy/qubes-builder'
>>> make: *** [Makefile:224: vmm-xen-dom0] Error 1
>>>
>>>
>>>
>>> How can I fix this?
>>>
>>>
>>
>>
>> Hello guys!
>> Any updates on this?
>> As I'm tried to build qubes-iso and have same issue ;-\
>>
>
> In progress, but it's going to be a few more hours until GCC is done
> building to see if it's fixed...
> https://github.com/QubesOS/qubes-issues/issues/3707
> Note my error is slightly different.

Discussion got consolidated to
https://github.com/QubesOS/qubes-issues/issues/3650. Solution looks to be
to revert a commit by hand (or wait until that reversion gets to
qubes-builder/master), then builds should work. Am confirming but builds
take me a long time. Ignore the discussion about "make dist-clean", that
shouldn't be necessary once the fix goes in.


-- 
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/8b67a1710f2b095940e0f33a4884cc33.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: creating rc5.iso $ cd qubes-secpack/,$ git tag -v `git describe`,,I get "object not found"

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-03-17 15:07, socks wrote:
> On 03/17/2018 08:37 AM, socks wrote:
>> I'm sure it's the newb in me, but I'm trying to verify the rc5.iso and
>> getting stuck here:
>>
>> https://www.qubes-os.org/security/pack/
>>
>>
>> Step 4.
>>
>> Verify signed Git tags.
>>
>> |$ cd qubes-secpack/ $ git tag -v `git describe` I get "object not
>> found" proceeding in the /canaries , it's ok |
>>
>>
> Intriguingly I also get this :
> 
> 
> desktop ~/Downloads/Qubes-R4.0-rc5-x86_64 $ md5sum -c
> Qubes-R4.0-rc5-x86_64.iso.DIGESTS
> Qubes-R4.0-rc5-x86_64.iso: OK
> md5sum: WARNING: 22 lines are improperly formatted
> 
> 
> so:  is this .iso  OK  or ?
> 

That's normal:

https://ask.fedoraproject.org/en/question/10956/checksum-verification-error-message-is-mysterious/

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqtdjkACgkQ203TvDlQ
MDCdfxAAnUrscoBDk/E1MAvVS7UgMP/dluC2VnTAW6aNIm8D0iGDRApjN4kpdm3f
QRtrJhcMTIC5tg9Vyo8hEb78qNvi24pP41TuywOaUfs94mUpHO/44+X6t+y0Emzp
MJkL1whpFKNM1qz6Kgh9TmfB00NHElNmUgz4fXQ3eXSgRlsO6JstiCQOO4XIzvYa
DYqaSwENeJUSp9ImFJBK01OJtHWmp5xEMWlEnt4W9D0XWCSlJm2+Nh0zPcEXS8+2
Gn72ibVkMrmU6rzcedAnbQvAGNHeisJCH9ZGHZ0qItROLH6IO9PepQ7Yeo3bw/pT
YGqafU4ePLeasdYVgg3jA3PHsCcrhkm1R3J8/FsPl6FqUsYER7nQkbHvIe8t3XxI
qNFU6SBxcWbOpjtTJBdSWLLuSV/6hkzJ0MDvvxyzc+ksLE9WhRWN/71pzDb1iJJ1
GVv3UiB3TP5oVMF9d1I3fArG5boilOlfZiJ1YYuc5V68rWIfsg+3dAVOavFZABN3
J8IQkpU0KvM6wFHarQKDr4X38k/huksRcKxJS1TgD4tVezEK028sV+xBk1Q5glyx
BK29WBNJzPQ55nxZC/dKaX5nTK8Do3d9QhQzGo921/2PExPqn5vCQRHWf4N4AZNP
aJxeHPxPxj4eVhhmKUvuDP3GR+cQhFkT7ANfQesb7AOVSW/ksNI=
=aDZR
-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/67d88181-bade-fe61-1d12-b22d6c79da46%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: creating rc5.iso $ cd qubes-secpack/,$ git tag -v `git describe`,,I get "object not found"

2018-03-17 Thread socks


On 03/17/2018 08:37 AM, socks wrote:
I'm sure it's the newb in me, but I'm trying to verify the rc5.iso and 
getting stuck here:


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


Step 4.

Verify signed Git tags.

|$ cd qubes-secpack/ $ git tag -v `git describe` I get "object not 
found" proceeding in the /canaries , it's ok |




Intriguingly I also get this :


desktop ~/Downloads/Qubes-R4.0-rc5-x86_64 $ md5sum -c 
Qubes-R4.0-rc5-x86_64.iso.DIGESTS

Qubes-R4.0-rc5-x86_64.iso: OK
md5sum: WARNING: 22 lines are improperly formatted


so:  is this .iso  OK  or ?



--
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/1681a4ac-c2ed-2c64-75e4-9868349cf44a%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?

On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote:

> What would be the step to downgrade to the previous version to
> get dispVMs working again?
>
> qubes-dom0-update --action=downgrade xen something like this or is it
> necessary to specify all packets individually?

Depending on how attached you are to Fedora, you might want to temporarily
try the Debian template instead of downgrading Xen?

I'm still on -36 so can't confirm...


-- 
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/59491a7fdc2b4436fcfb3ba6cb355f09.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-03-17 14:57, qubes-li...@riseup.net wrote:
> 
> 
> Andrew David Wong:
>> On 2018-03-17 11:40, qubes-li...@riseup.net wrote:
>>
 Have you made sure that you have updated the packages in the 
 template and regenerated the DispVM? That's a common source of 
 these problems and fixed it for me.
>>
>>> Yes I've updated and regenerated the dispvm after the dom0 update.
>>
>>
>> Same here. Updating and regenerating did not resolve the issue.
>> Tracking:
>>
>> https://github.com/QubesOS/qubes-issues/issues/3711
> 
> thank you for filing it on gh!
> 
> Assuming the latest updates introduced this regression:
> 
> What would be the step to downgrade to the previous version to
> get dispVMs working again?
> 
> qubes-dom0-update --action=downgrade xen
> something like this or is it necessary to specify 
> all packets individually?
> 

`dnf history undo` or `dnf history rollback` might work, depending on
which is appropriate:

https://unix.stackexchange.com/q/349238

However, I don't know whether this is the optimal way, or whether
it'll break anything, since these are Xen packages. There's also a
concern that downgrading might render the machine vulnerable to
Spectre SP2 again.

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqtdJIACgkQ203TvDlQ
MDC8Mw//fwCHZ9CeTUEHEA024XJ7WysII+FZvjk8DviLiRfFjaY1wGEYryY32uvo
5pejGc4l6kjnTW1Lolcn7AA7Ne4TpWXP6B7cl2SAWcHPm2+ka9E9lX8gy8S+16rt
dY7uVxawFFQr2MwsW0bPiv8y510k7VjnAvchWWA6UEAYdW5PytrFNKWEIxxttxOc
v+aEwAM5D399vES7++VgknQ9kKgaccN+ymLxdxjhYz666DdrWtBuB7YJDEnXKFWl
7Jux0W26loz1E3ADr/SOapjmxbmSQe/J4xcffpL4NOn6peP6VCtZqLFNzKM0FIVo
aqUQLAuM8dGLOD7I4MjAW0Rxjg65UZV8G/dzY+RcUA7Qls0nw03ywLdnG5HwS9oS
cJel/R8Bbvw7KXHrstENRx34i+UMmLGjvJoC6KAgS194aUzA0touODWlrQyPGaT+
gbRpSKAeDa0tXOX61VOobCFJGFm7oEDEV9l6DH+ln92XQNIwaNcbIBhazC9Zd4xi
zIJB0IkylrjahLZRuwpKNV8kibGgI62uZoq8kcqBQPZ65WC/8n7jyKYafOvXizwS
NGzo7QlQ2js/OcJW/FrxiR1t2+12ObNi8BkwoE5Srf8I2bceKMADNuqQEFxKsExI
0AL0Zd6cZ56fjf1QnIbcVuKvM7vFFZxl7zLIyJo2RER6dhZnUsg=
=KsgK
-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/338ebd7e-285b-fcc8-6858-ef1f5bf132f1%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?



Andrew David Wong:
> On 2018-03-17 11:40, qubes-li...@riseup.net wrote:
> 
>>> Have you made sure that you have updated the packages in the 
>>> template and regenerated the DispVM? That's a common source of 
>>> these problems and fixed it for me.
> 
>> Yes I've updated and regenerated the dispvm after the dom0 update.
> 
> 
> Same here. Updating and regenerating did not resolve the issue.
> Tracking:
> 
> https://github.com/QubesOS/qubes-issues/issues/3711

thank you for filing it on gh!

Assuming the latest updates introduced this regression:

What would be the step to downgrade to the previous version to
get dispVMs working again?

qubes-dom0-update --action=downgrade xen
something like this or is it necessary to specify 
all packets individually?

-- 
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/1379ed33-c305-a7fd-77ea-d1ccfb3023a8%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] re: creating rc5.iso $ cd qubes-secpack/,$ git tag -v `git describe`,,I get "object not found"

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-03-17 13:37, socks wrote:
> I'm sure it's the newb in me, but I'm trying to verify the rc5.iso  and
> getting stuck here:
> 
> https://www.qubes-os.org/security/pack/
> 
> 
> Step 4.
> 
> Verify signed Git tags.
> 
> |$ cd qubes-secpack/ $ git tag -v `git describe` I get "object not
> found" proceeding in the /canaries , it's ok |
> 

Cannot reproduce. Following those exact steps works for me. Perhaps
there was a typo?

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqtcw0ACgkQ203TvDlQ
MDAOWQ/9Ek3SUOJJzZ1Wf3GwYY5tI5ZkUvqObkTFqluhCyNgAwzGE/X4YXfeaJwj
/07zdXpsih6nBpHm2SZOGggSEgP0rFQYMdS49GIPvIceujuREI0ol6GtqPesrG02
ID5Vkwu4rvpt9OMVei4MInhml41mRT6M3SkO3S+JwP/x4lJpUrHV2rG0dtrNna8b
Dy4rrKOvqP0i0xUNDHVGEvnATCcHT7el/ndSpwo070+6Y4hCTSCqKFsKNtvnCiiA
1CbOjWeSSHi6tb+UtVhoneSXO1vqDtIsviHy2546ZtvdzWRIH+uhsmGmNyRRdOtq
CZb3W5Z7D5zRQRttVpsdSsOLl0/xjyOVecu2ACBhWpkxOnZeIe0pOcxHSG8P6hlx
bD5SbaqQ5BeGEx1+xmAaIGKbqQawt43/gEjfZiUFEZQYXS35C4G/Fky4InNUwsky
t7YE2tAYyLXwYm4+N/buCqKdWDxXJDibZ747LRSfkpdb7a8QnkAPJPf2Kgnz3Q8m
6trZbHG2yrsS7WeKK8OiYjMeIhB5DJgJdMzAsHNnGkc04A/zPx81RNI9/gneqHF6
pCo1jleWkXXQzGRLHrXXNX7t9LieDaXXDqEqDiSc0DP2KjgBtuel660fNR3gzXQG
jt7RjQWfINT2OSZd9ZDrgX2aice6TR/+NRs/R2j6R53yqt8V/PE=
=FZe4
-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/62421a9b-28d0-f2dd-1bd4-f3aabd0a2420%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-03-17 11:40, qubes-li...@riseup.net wrote:
> 
>> Have you made sure that you have updated the packages in the 
>> template and regenerated the DispVM? That's a common source of 
>> these problems and fixed it for me.
> 
> Yes I've updated and regenerated the dispvm after the dom0 update.
> 

Same here. Updating and regenerating did not resolve the issue.
Tracking:

https://github.com/QubesOS/qubes-issues/issues/3711

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqtcQcACgkQ203TvDlQ
MDCQpw/+KBAcs3K4hqLv9XrgbSM3q7FyiDbNtvM/bd78v3/OI9Dmd74HW1R+irUP
jbDCpunKhMJs8y/a0i7urrYPRSQ4Yy2j3QT4OduZj1YjqvxvtUzSD7i6NNdWgrV9
oCsKLjrZBvTtSMv2TbqlyMIbCwuvvUCUvCqN7478iGw0mNUvdjk0BJEwRqFmcPKK
oHH/NKI9Ay8azjuFGu0l6Z+L1m73FYuJ8imch9GgAucJqx+YjMvX4cMfUoqMgu/m
YougHWC9Ddyq4VFZ3tojrIaANOHRZeU2DzWVK58I/iDxMmWKHCV8xfD6iZLKT9VG
zrONSZrAcbEUY+CBdEu45wcmhs7U6MD5DBx4LSXdVwF5yBYXPpuqcLiVgkhS6ro/
LBpSgGRQdHs8ePAr4BdaKA9Y/VRHjm8TNtHW5AriQ+kwnQtPl6VHjTNKOxn/xRoc
02MMDXQXkd2YPHcTYqSGpp61tuhBUgMO06+I09kjxzGIyGf0CFGUY47CDRUTvpXJ
/IeXbu+ag3DvDezg18vkKo/WAALJyhSpnyBgk1LWGAohvk/t4AtKGeSZP3hTUTXJ
l/UbnZEeJ2hPMq6Vb0X4qBzewioe74Qw0G263F5giYeOzBBDcUPt46+e8MulWmEW
tEt3Y4lx3p3TnyasWK4slASj+sulKwX/BQ/t7yVygyEoJPKi+UQ=
=WmKY
-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/01bbd9d1-cdfe-3f9c-16c1-43b3eb15aa8b%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] mouse lagging with sys-usb in Qubes 3.2

2018-03-17 Thread snowboard789

Since I created a sys-usb device and connected the mouse with passthrough to 
dom0 (I answered yes the first time) the mouse is lagging significantly. I even 
changed the attributes from mouse properties from the GUI menu but nothing 
happens. It's a laptop so touchpad is working perfectly.

Why does it lag so much?

Output of qubes.InputMouse:

sys-usb dom0 allow,user=root
$anyvm $anyvm deny



-- 
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/e9cace2d-da6e-4644-aedf-2b5e7c91bc4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Coreboot + Qubes :: Best Practises / Coreboot docs page

2018-03-17 Thread 799

Hello,

I had Coreboot running on my X230 with Qubes 3.2 + Windows Dualboot and
reflashed to stock room before installing Qubes 4.
Now I want to reinstall Coreboot without using Dualboot, thereof I have
more options regarding 2nd payload.

Question:
What is the best configuration to run Coreboot and Qubes?
Seabios or Grub and are there any special options which might make sense?

Some information has been provided in
https://groups.google.com/forum/m/#!topic/qubes-users/I6kt6362PR0
But I'd like to see a special page in the documentation and would be
willing to contribute or create to such a page.

Should I use Seabios or Grub?

[799]

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

Re: [qubes-users] DispVM broken in 3.2?


> Have you made sure that you have updated the packages in the template
> and regenerated the DispVM?
> That's a common source of these problems and fixed it for me.

Yes I've updated and regenerated the dispvm after the dom0 update.

-- 
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/ce5666fd-bf86-f2f0-25c7-7b0ce3fb9758%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Runing Qubes on: HP ProBook 430 G2 or HP EliteBook 820

2018-03-17 Thread Linus Stridbeck

Den lördag 17 mars 2018 kl. 00:29:51 UTC+1 skrev tai...@gmx.com:
> How inexpensive?
> 
> You can get an G505S for $150 or so and it is the the last and best 
> x86_64 owner controlled laptop, it supports qubes 4.0 and doesn't have 
> ME/PSP.
> It supports coreboot with open source hardware initiation for the 
> cpu/ram and while there are blobs for video and power they are 
> theoretically replaceable and are restricted from doing anything nasty 
> via the IOMMU.
> 
> Note: as a new qubes user you should be aware that purism laptops are 
> NOT open source, libre or "privacy and security respecting" - their 
> marketing is very dishonest.

Tai,  the lenovo is to large in my opinion.. the 430 is 227  USD and has a i3, 
G2 modem but only 4 gig of ram.  

Is it inappropriate to select one with less than 8 gigabyte of ram?

I can by a number of 820 one with 8 gigabytes of ram, i5 and 4G modem I guess 
that would work because has all the features of the 820 in the compatibility 
list aside from have a better modem. But apparently 1G is supposed to be enough?

I'm trying get it as inexpensive as possible so it would be god if the 430 
would work. But maby he cpu is to old.   

Anyway all the 820 has one interesting feature: is its  possible to put an 
extra hard drive in them would it be possible to have two seperate operating 
system and select which one to start the computer from?  
   
How important is modem? can it be presumed that 1g works for all the 820?  

-- 
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/74753488-e083-4418-889f-af8752d7246d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Runing Qubes on: HP ProBook 430 G2 or HP EliteBook 820

2018-03-17 Thread Linus Stridbeck

Den lördag 17 mars 2018 kl. 10:21:36 UTC+1 skrev Vincent Adultman:
> Linus Stridbeck  wrote:
> 
> > I came across very inexpensive HP computers:
> > 
> > HP ProBook 430 G2
> > 
> > HP EliteBook 820
> > 
> > They both have i3 procesor and I wonder if someone tried ryning Qubes on 
> > one of them?
> > 
> > 
> > 
> 
> I'm typing this on an 820 G3 with an i5 6200u cpu. Once I've had a bit more 
> of a chance to play I'll post a proper HCL entry.
> 
> My existing 3.2 install has no problems booting on the machine, the features 
> needed for 4 are supported (SLAT/EPT and interrupt remapping), but I haven't 
> tested 4. The CPU should support 32gb, but the manual states 16gb is the max, 
> I currently have one 16gb stick in one ram slot and this works fine. 
> Virtualisation needed to be turned on in the BIOS.
> 
> Unlike older Elitebooks, it only seems to have a single USB controller, which 
> is a pity, as it seems to mean ports, webcam and fingerprint reader are on 
> the same controller, a pity as machine has interrupt remapping.
> 
> Issues I'm currently working through:
> 
> Screen brightness cannot be controlled using f5/f6 keys, however the 
> brightness slider available from the power manager on the xfce system tray 
> does control it.
> 
> Webcam doesn't seem to work with cheese in fedora 26, light on webcam flashes 
> then cheese exits. 
> 
> Screen backlight stays on when screen is locked.
> 
> If you're looking at an older 820 with an i3, check the processor at ark 
> https://ark.intel.com/ it's quite likely it may be missing some of the 
> features required for Qubes / Qubes 4.
> 
> 

god to hear that its working. that seams to be what they recomende on the 
compatabilaty list. how important is modem the one on the list has only 1g 
could it be presumed that 1g is will work on alla 820?  

-- 
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/c2f0ca9e-be25-47a1-b2a9-4dd565aadf32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DispVM broken in 3.2?

On Sat, Mar 17, 2018 at 11:53:00AM +, qubes-li...@riseup.net wrote:
> DispVM functionality does no longer work for me in Q3.2 since yesterday.
> 
> First I assumed the template is broken but after reinstalling the fedora-26 
> template
> from the rpm repo and recreating the DVM I get the very same error.
> 
> Has anyone else the same problem after installing the latest dom0 updates?
> 
> from the dom0 yum.log the latest installed updates were (2018-03-15):
> 
>  libgcc-5.3.1-6.qubes1.fc23.x86_64
>  2001:xen-licenses-4.6.6-37.fc23.x86_64
>  2001:xen-libs-4.6.6-37.fc23.x86_64
>  2001:xen-hypervisor-4.6.6-37.fc23.x86_64
>  2001:xen-runtime-4.6.6-37.fc23.x86_64
>  libstdc++-5.3.1-6.qubes1.fc23.x86_64
>  2001:xen-hvm-4.6.6-37.fc23.x86_64
>  2001:xen-4.6.6-37.fc23.x86_64
>  qubes-gpg-split-dom0-2.0.28-1.fc23.x86_64
>  libgomp-5.3.1-6.qubes1.fc23.x86_64
> 
> 
> I also tried a reboot but that did not change anything either.
> 
> 
> This is the error I get when trying to start xterm (or anything else) in a 
> DispVM:
> 
> 
> echo xterm| /usr/lib/qubes/qfile-daemon-dvm qubes.VMShell dom0 DEFAULT red
> time=1521287074.5, qfile-daemon-dvm init
> time=1521287074.51, creating DispVM
> time=1521287075.04, collection loaded
> time=1521287075.05, VM created
> time=1521287075.06, VM starting
> time=1521287075.06, creating config file
> time=1521287075.06, calling restore
> Traceback (most recent call last):
>   File "/usr/lib/qubes/qfile-daemon-dvm", line 217, in 
> main()
>   File "/usr/lib/qubes/qfile-daemon-dvm", line 205, in main
> dispvm = qfile.get_dvm()
>   File "/usr/lib/qubes/qfile-daemon-dvm", line 167, in get_dvm
> return self.do_get_dvm()
>   File "/usr/lib/qubes/qfile-daemon-dvm", line 103, in do_get_dvm
> dispvm.start()
>   File 
> "/usr/lib64/python2.7/site-packages/qubes/modules/01QubesDisposableVm.py", 
> line 193, in start
> domain_config, libvirt.VIR_DOMAIN_SAVE_PAUSED)
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4405, in 
> restoreFlags
> if ret == -1: raise libvirtError ('virDomainRestoreFlags() failed', 
> conn=self)
> libvirt.libvirtError: internal error: libxenlight failed to restore domain 
> 'disp1'

Have you made sure that you have updated the packages in the template
and regenerated the DispVM?
That's a common source of these problems and fixed it for me.

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

[qubes-users] DispVM broken in 3.2?

DispVM functionality does no longer work for me in Q3.2 since yesterday.

First I assumed the template is broken but after reinstalling the fedora-26 
template
from the rpm repo and recreating the DVM I get the very same error.

Has anyone else the same problem after installing the latest dom0 updates?

from the dom0 yum.log the latest installed updates were (2018-03-15):

 libgcc-5.3.1-6.qubes1.fc23.x86_64
 2001:xen-licenses-4.6.6-37.fc23.x86_64
 2001:xen-libs-4.6.6-37.fc23.x86_64
 2001:xen-hypervisor-4.6.6-37.fc23.x86_64
 2001:xen-runtime-4.6.6-37.fc23.x86_64
 libstdc++-5.3.1-6.qubes1.fc23.x86_64
 2001:xen-hvm-4.6.6-37.fc23.x86_64
 2001:xen-4.6.6-37.fc23.x86_64
 qubes-gpg-split-dom0-2.0.28-1.fc23.x86_64
 libgomp-5.3.1-6.qubes1.fc23.x86_64


I also tried a reboot but that did not change anything either.


This is the error I get when trying to start xterm (or anything else) in a 
DispVM:


echo xterm| /usr/lib/qubes/qfile-daemon-dvm qubes.VMShell dom0 DEFAULT red
time=1521287074.5, qfile-daemon-dvm init
time=1521287074.51, creating DispVM
time=1521287075.04, collection loaded
time=1521287075.05, VM created
time=1521287075.06, VM starting
time=1521287075.06, creating config file
time=1521287075.06, calling restore
Traceback (most recent call last):
  File "/usr/lib/qubes/qfile-daemon-dvm", line 217, in 
main()
  File "/usr/lib/qubes/qfile-daemon-dvm", line 205, in main
dispvm = qfile.get_dvm()
  File "/usr/lib/qubes/qfile-daemon-dvm", line 167, in get_dvm
return self.do_get_dvm()
  File "/usr/lib/qubes/qfile-daemon-dvm", line 103, in do_get_dvm
dispvm.start()
  File 
"/usr/lib64/python2.7/site-packages/qubes/modules/01QubesDisposableVm.py", line 
193, in start
domain_config, libvirt.VIR_DOMAIN_SAVE_PAUSED)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4405, in 
restoreFlags
if ret == -1: raise libvirtError ('virDomainRestoreFlags() failed', 
conn=self)
libvirt.libvirtError: internal error: libxenlight failed to restore domain 
'disp1'

-- 
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/70bf5c3f-2eb2-023e-0944-1a3d1d31d47f%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Runing Qubes on: HP ProBook 430 G2 or HP EliteBook 820

2018-03-17 Thread 'Vincent Adultman' via qubes-users

Linus Stridbeck  wrote:

> I came across very inexpensive HP computers:
> 
> HP ProBook 430 G2
> 
> HP EliteBook 820
> 
> They both have i3 procesor and I wonder if someone tried ryning Qubes on one 
> of them?
> 
> 
> 

I'm typing this on an 820 G3 with an i5 6200u cpu. Once I've had a bit more of 
a chance to play I'll post a proper HCL entry.

My existing 3.2 install has no problems booting on the machine, the features 
needed for 4 are supported (SLAT/EPT and interrupt remapping), but I haven't 
tested 4. The CPU should support 32gb, but the manual states 16gb is the max, I 
currently have one 16gb stick in one ram slot and this works fine. 
Virtualisation needed to be turned on in the BIOS.

Unlike older Elitebooks, it only seems to have a single USB controller, which 
is a pity, as it seems to mean ports, webcam and fingerprint reader are on the 
same controller, a pity as machine has interrupt remapping.

Issues I'm currently working through:

Screen brightness cannot be controlled using f5/f6 keys, however the brightness 
slider available from the power manager on the xfce system tray does control it.

Webcam doesn't seem to work with cheese in fedora 26, light on webcam flashes 
then cheese exits. 

Screen backlight stays on when screen is locked.

If you're looking at an older 820 with an i3, check the processor at ark 
https://ark.intel.com/ it's quite likely it may be missing some of the features 
required for Qubes / Qubes 4.

V

-- 
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/eXFuzuxjvoru542I-jpWt2-KxF--sYhODPj3RIvTp570ZDreyu0S39dnKzAiYBUJVSPGCF6Tyi9PeHVxddyunDr0LMC_y-0P9IEl42i-ElA%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Disk problems when installing ReactOS 0.4.5 on HVM

2018-03-17 Thread Giulio

|Hello,
i need to run some simple windows applications that should run on
ReactOS that compared to Windows has the advantage to be open source and
very lightweight.

I have read
- https://github.com/QubesOS/qubes-issues/issues/2809
-
https://github.com/Jeeppler/QubesOS-notes/blob/master/ReactOS/Qubes-ReactOS.md
-
https://mark911.wordpress.com/2017/12/09/procedure-for-installing-newest-reactos-operating-system-in-stand-alone-hvm-in-qubes-os-3-2/

My HCL report is attached.

This is the command i use to create the StandaloneVM

qvm-create reactos --class StandaloneVM --property virt_mode=hvm
--property kernel="" property memory=4096 --property maxmem=4096 --label
green

If i try booting the installation ISO the the procedure fails because it
cannot recognize the block device. (install_error.png)
If i convert the VirtualBox image a similar error occur during boot.
(virtualbox_error.png)

Is there someway i can change the device type in HVM? i.e. set it as an
IDE device? I tried also installing Windows XP and it failed for a
related reason.

--
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/3699c348-a6ba-b10e-00e4-d0e81339992f%40anche.no.
For more options, visit https://groups.google.com/d/optout.

Qubes-HCL-LENOVO-429136G-20180317-100650.yml
Description: application/yaml

Re: [qubes-users] Re: Dependency error building Qubes