Re: [qubes-users] AEM failure after upgrade

2017-07-14 Thread Rusty Bird 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

loke...@gmail.com:
> The AEM package was upgraded recently (probably because of this
> thread:
> https://groups.google.com/forum/#!topic/qubes-users/3ZkmS5v7E38),
> and after I installed the updated version, AEM stopped working
> completely.
>
> Now, it asks me for the AEM password. I type it in, and it doesn't
> display my secret message. Instead, it immediately asks me for the
> disk password, and while it boots the system, I see a message
> telling me: "PCR sanity check failed".

Below that, it should say "See /usr/share/doc/anti-evil-maid/README
for details." You can find some hints for debugging there.

> This is the content of the journalctl log:
> 
> Jul 07 16:25:36 dom0 systemd[1]: Starting Anti Evil Maid sealing...
> Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: tpm_z_srk: detecting whether 
> SRK is password protected
> Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: Tspi_Key_CreateKey failed: 
> 0x0001 - layer=tpm, code=0001 (1), Authentication failed
> Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: tpm_z_srk: yes, SRK is 
> password protected; resetting dictionary attack lock...
> Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-17: FF FF FF FF FF FF FF 
> FF FF FF FF FF FF FF FF FF FF FF FF FF
> Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-18: FF FF FF FF FF FF FF 
> FF FF FF FF FF FF FF FF FF FF FF FF FF
> Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-19: FF FF FF FF FF FF FF 
> FF FF FF FF FF FF FF FF FF FF FF FF FF
> Jul 07 16:25:39 dom0 systemd[1]: anti-evil-maid-seal.service: Main process 
> exited, code=exited, status=1/FAILURE

Looks like tboot/SINIT is not working correctly on your system. The
new AEM version refuses to seal in this situation, so that you don't
get a false sense of security.

Rusty
-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJZaMNAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfytAP/ArUcgXB5vKoBz+SP6My2QQQ
SXsjK1jqCqgXYziK/JI6r7LUEhXIvJfMsJKW/mdjd7OQv4davlSZxXVT9mxqA/0E
rCzF0AoIoAqtNYRSy0r+5t301KGy2I9efr0aziIFv591JEnOqKJK+F/MFNn7Zitb
+IY8YCQ6s+pgJcuKOycF2vz/9Dc817cILTfW+tzcSDMkG1NcbI4AbxXPxNwvMxkw
OZ0BJ9IMPfGVfAmKCGsouvnVc7vg/9mPgG7BhjD5Nojwwyb2dle8mhGiiWKtNPRw
2Eksk/m/NqCQb2F5NiQnQDOjJTwLvzf3hnEKSIwuKxLjrlVUyvsbmSrMwIbAUK7v
VdG2iCpCSgIPwTqUOlVPmQ2TNWhA3cDP2jGRSSi1RRWS2nGQd2w1tYKw3dibr/K7
RD6KQUgJdyxW3Y6cBidQ+zy0vbmMFyuQ6DyTF/T3Zmq2XvvBVaq6U/LwMZOpt+s+
X56JQa1HDdVBKTEXbPnxI+sT0ehMhfn1YOZBZ93lYkJyiyrIAvwCiQKfPLsVQqZH
M9e6L1C+CePEqNyb2btMUPJOuRtVd0059mgQ+x5PpdhnQOia0RR4A9Bn6oW5515m
qGsqY2wIg2wb7xG8O+Gl9sxQk8jtQX7Or/V4oixfGEqMb5Xi6a97nFKLha22lc7J
A5aT5+xMPvsk+02b33sg
=mUFf
-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/20170714131232.GA5546%40mutt.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: heads up, qubes 3.2 still vuln to cve-2016-4484 (minor severity)

2017-07-14 Thread pixel fairy 
On Thursday, July 13, 2017 at 10:36:25 PM UTC-7, qubester wrote:

> So, to exploit this, someone would need physical access to  the computer 
> at risk?

physical or any network available OOB. heres an example of what can go wrong 
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5689

on a simpler level, you dont want someone compromising that plain text part of 
your drive, maybe your workstation at the office. this way, they really would 
need physical access to remove your drive and compromise that boot sector. 

or, if you have a laptop, you can use other means, like glittery nail polish to 
see if anyone physically entered your laptop. of course, there may be other 
vulns, so its still good to have anti aem, or sed. 

-- 
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/618d1f42-bf20-4b3e-babd-5a94da00dd6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Just realized one of the major disadvantages of Qubes OS...

2017-07-14 Thread pixelfairy 
This thread should be renamed ipv6, and there was such a thread in
qubes-devel. one of the issues is what to do when moving from an ipv6
enabled network to one without. netvm can easily note the difference and
adapt, but weather your bridging or natting, all the appvms wont know any
better and will start trying to use the non existent ipv6.

one possible solution is dns filtering. dont return  records when no
global address is present, but then your going down another rabbit hole.

On Thu, Jul 13, 2017 at 11:34 PM Alex  wrote:

> On 07/14/2017 05:30 AM, motech man wrote:
> > On Thursday, July 13, 2017 at 12:05:34 PM UTC-5, geoff.m...@gmail.com
> > wrote:
> >> A bit of thread necromancy here, but - if you're using a smartphone
> >> in the US with mobile data, there's a *very* good chance you're
> >> already using IPv6.
> >> [...]>>
> >> --Geo
> >
> > I also expect to see routers for home market that will talk ipv6
> > externally and ipv4 internally. That will help a lot of people
> > transition.
> Here in Italy (and a lot of other countries too) home routers just
> started distributing /64 internally, in full dual-stack mode, during
> this spring for the major ISPs.
>
> Public institutions are expected to be fully dual-stack connected and
> publicly available by the end of the year by law.
>
> I don't see any advantage in having a situation like you described - why
> not just full dual stack, and the devices connect to the technology they
> support?
>
> Apart from us qubes aficionados, any win10 pc, apple or android device,
> and the vast majority of linux workstation/server distros fully support
> dual stack configurations, and happily work preferring ipv6 when available.
>
> --
> Alex
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "qubes-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/qubes-users/rJYmO78ckxM/unsubscribe.
> To unsubscribe from this group and all its topics, 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/809adbd0-7716-c7b8-9adf-df3d56787d34%40gmx.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CACr%3DtZdrVO15Dc0FrEibXkH1Tz9_VwHrYHyMmx3t4oNxyXtpWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Install issues Sager / Clevo laptop (7700k/GTX1080)

2017-07-14 Thread kenflyy14 
Booting the installer goes to text based install. Then complains about no LUKS 
password set for drive when I select destination drive.

I then came across this thread:
https://groups.google.com/forum/m/#!msg/qubes-users/-9qRHSkwfy8/CCx08nnTVEAJ

Followed this to a T with my edited ks file. Got it to install. For the Fedora 
kernel, I used 4.11.9-300.fc26.rpm , but after the last boot. it seems its 
still booting the default kernel it came with :/ So im dumped to a command 
login with a bunch of X server errors in the beginning.

Is there a different kernel I should be using?

Grub doesn't even show other options to boot from other than the default kernel

-- 
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/b656cec3-7166-4d82-97c2-bb825749fbd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Lenovo Yoga 900 for BIZ 80SD

2017-07-14 Thread tsadowski 
Hello,

after some painful troubles I have it running with Qubes 3.2. As might be 
expected there are some issues:

Touchpad/Touchscreen do not work. I could not even find a touchpad USB device. 
It worked in the Qubes 4.0 preview.

No Wifi after resume. Reloading the iwlwifi module did not help.

Either hibernate or suspend works. I have to check which.

Resolution is erratic in AppVMs between reboots. I the have to stop and restart 
the AppVM or use a magnifying glas.

Most annoying was that 3.2 can't add a boot entry. 4.0 can. Refind helps but I 
installed a small Xubuntu 17.04 on the Lenovo driver partition for helper tasks.

The Laptop has a TPM 2.0 but this does not seem to be supported.

Thanks for the great work!

Cheers, Torsten

Sorry, I did not find an upload button:

---
layout:
  'hcl'
type:
  'notebook'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  LENOVO
model: |
  80SD
bios: |
  0TCN14T
cpu: |
  Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Skylake 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])
gpu-short: |
  FIXME
network: |
  Intel Corporation Wireless 8260 (rev 3a)
memory: |
  16289
scsi: |

usb: |
  1
versions:

- works:
'yes'
  qubes: |
R3.2
  xen: |
4.6.5
  kernel: |
4.4.14-11
  remark: |
FIXME
  credit: |
tsadowski
  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/fadda9eb-f1b1-437e-8de9-6324c25d1fc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

2017-07-14 Thread 'Essax' via qubes-users 
Was just reading through the qubes docs. You can delete your current sys-usb 
and make a new sys-usb and make it an appVM(sys-usb). Then you could attach it 
to a sys-firewall or sys-net . Im not 100% sure this will help but it is worth 
a try. Sorry I don't have time to write out the instructions. The link to the 
doc: [Qubes-doc-usb](https://www.qubes-os.org/doc/usb/)

Essax
Sent with [ProtonMail](https://protonmail.com) Secure Email.

>  Original Message 
> Subject: Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes
> Local Time: July 14, 2017 11:42 AM
> UTC Time: July 14, 2017 3:42 PM
> From: p...@mailbox.org
> To: Patrik Hagara 
> qubes-users@googlegroups.com
>
> Actually I do have the qubes-proxy-usb installed on my sys-usb (that's how 
> I'm able to use my mouse) however I'm not sure if the qubes-proxy-usb can be 
> used to pass the HW wallet.
>
> How I'm I suppose to pass my Ledger nano s or trezor via the proxy?
>
>> On 14 July 2017 at 15:40 Patrik Hagara  wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On 07/14/2017 02:19 PM, Mr. DONG wrote:
>>
>>> Unfortunately that doesn't work either.
>>>
>>> The "qvm-usb -l" doesn't show my legder nano s. In fact I can only
>>> see it attached on the sys-usb, not on dom0.
>>>
>>> The qvm-usb list output shows no difference either I attach or not
>>> the HW wallet. The only way I can attach to another appvm is if I
>>> attach the entire PCI controller, via the usb-passthrough does not
>>> work.
>>>
>>> Any alternatives?
>>>
>>> On 14 July 2017 at 10:48 Patrik Hagara 
>>> wrote:
>>>
>>> On 07/14/2017 02:54 AM, 'Essax' via qubes-users wrote:
>>>
>>> Have you tried these steps:
>>>
>>> 1) Attach hardware wallet to sys-usb 2) Go to the dom0 Gui and and
>>> right click on the appVM you want to attach it to. 3) In the box
>>> that opens scroll down to Attach/detach block devices and your
>>> hardware wallet should show up to the right. 4) Right click on
>>> your hardware wallet to attach it to your appVM.
>>>
>>> /Essa*x*/
>>>
>>>  Original Message  Subject: [qubes-users] Re:
>>> Working with a BTC hardware wallet on Qubes Local Time: July 13,
>>> 2017 4:23 PM UTC Time: July 13, 2017 8:23 PM From: p...@mailbox.org
>>> To: qubes-users@googlegroups.com
>>>
>>> I do have a sys-usb vm, however I cannot attach a netVM to it since
>>> the sys-usb is also a netvm.
>>>
>>> I possibly will need to create a new sys-usb vm or is there any
>>> other alternative?
>>>
>>> Attaching it as a block device won't work, since bitcoin hardware
>>> wallet is not a mass storage device. Luckily, it's not emulating a
>>> HID device either, which would get picked up by the dom0 USB
>>> keyboard/mouse input proxy. Thus, there's no graphical means of
>>> attaching USB bitcoin hardware wallet in Qubes to another VM...
>>>
>>> You can, however, attach it via the qvm-usb command line tool:
>>>
>>> 1) connect the bitcoin hardware wallet 2) in dom0 terminal, run
>>> |qvm-usb -l| to list USB devices attached 3) locate the line with
>>> bitcoin wallet and note the first column (eg. "sys-usb:2-1.6") 4)
>>> run |qvm-usb -a bitcoin sys-usb:2-1.6| from a dom0 terminal to
>>> attach the wallet to bitcoin AppVM
>>>
>>> Cheers, Patrik
>>
>> Most likely you don't have qubes-usb-proxy installed in the sys-usb's
>> template (make sure to also install this package in the target bitcoin
>> banking AppVM's template). See [1] for more info.
>>
>> [1]
>> https://www.qubes-os.org/doc/usb/#attaching-a-single-usb-device-to-a-qub
>> e-usb-passthrough
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2
>>
>> iQIcBAEBCAAGBQJZaMnNAAoJEFwecd8DH5rlmTkP/jiwIpUlTMr6OMEUw3afH46X
>> h1Z+hcADH40Z1M2FVTH3oqginIjoGs0kJyd490vcpaic3Js1EO6+I0eXtvF4n2qt
>> J5LWSHQ/AQg3xjfBAFSsl2kEXnNa0CGF9hl0ZLCJOaHKcbpcJfS69fH79kT7KtJG
>> KJ4bOgENGCHaxgHb6vqtvdaYgnj8ltHqRvIZjwThai1PBsQcmw1HSf+uBMzQNRFw
>> 5E39a1Rb6vkvpdG1EDjEXrtzU8TdLH/96eCGODD0+t6vbAAp0t9EEheeqFjDdtz1
>> 65FNUWYx+WxkCvjcDaMK6GR/NY447C9cCM3xm55rQlFH7/vzH9CkMTM52+ZW0bqB
>> 27B8d+BatKYaIKQbrxHBWxdN7LDsJkcr+YHVHGt2F7nqt14LsLaRf+52gj6A+MHq
>> utn+5cVUpVT//GKlox+vEwfxZC/TjRqr4Im6tqAWQX+OZrpH9q4yP+asb6Ca2YdY
>> 3K9qoJZmtUVCaMiVQLqTRcjzHdVpMllS7scSs4wcJDHvi+KxhIOafG3iH2zAx7VC
>> CKXj2JltK7BXv4rlRUmcsIO6f4vTq/ylzZ4pP9bUp3VuQQum3wJ4dQnC9GdOoN6B
>> rTwgfZ5ovA+Fo37FVdRR6k5tc/Gh1emhiFHNfOMAtO6364O0GxWo6NkERTHhVF94
>> ZdhPoB3Ggx9FoTiAyNPI
>> =9Dw6
>> -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 
>

[qubes-users] Re: off topic - invite codes to 'riseup'

2017-07-14 Thread uwotm8 
On Saturday, 2 May 2015 15:04:38 UTC-4, Noah Vesely  wrote:
> I just PM'd you one. You don't need to give me anything in return.

pm me one too

-- 
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/dbf55a89-d9f3-4758-b0eb-c70f81eb5c97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] off topic - invite codes to 'riseup'

2017-07-14 Thread Mr. DONG 
Please can someone also send one to me!

Very, very appreciated!!


Thank you a million!

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

[qubes-users] Re: off topic - invite codes to 'riseup'

2017-07-14 Thread uwotm8 
On Tuesday, 28 October 2014 14:26:49 UTC-4, bm-2cu9wcijafoqtf6...@bitmessage.ch 
 wrote:
> Dear qubes-users,
> 
> I am long time qubes follower and user. I apologize in advance if anyone 
> feels this request is spam.
> 
> I am looking for two invite codes needed to sign up to anonymous 
> riseup.net email service.
> 
> I am hoping there are some qubes users who are riseup.net account 
> holders.
> 
> Can anyone please send me a couple of invite codes that I might be able 
> to sign up?
> 
> Thank you in advance.

please send me one too, thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dfd80568-f8be-45e3-8ccd-b88db194ade8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: off topic - invite codes to 'riseup'

2017-07-14 Thread nova54517 
On Tuesday, 28 October 2014 14:26:49 UTC-4, bm-2cu9wcijafoqtf6...@bitmessage.ch 
 wrote:
> Dear qubes-users,
> 
> I am long time qubes follower and user. I apologize in advance if anyone 
> feels this request is spam.
> 
> I am looking for two invite codes needed to sign up to anonymous 
> riseup.net email service.
> 
> I am hoping there are some qubes users who are riseup.net account 
> holders.
> 
> Can anyone please send me a couple of invite codes that I might be able 
> to sign up?
> 
> Thank you in advance.

please PM me one thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fb251078-65c4-4de5-95e9-5d0d205a7dd9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

2017-07-14 Thread Mr. DONG 
Actually I do have the qubes-proxy-usb installed on my sys-usb (that's how I'm 
able to use my mouse) however I'm not sure if the qubes-proxy-usb can be used 
to pass the HW wallet.

How I'm I suppose to pass my Ledger nano s or trezor via the proxy?




> 
> On 14 July 2017 at 15:40 Patrik Hagara  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On 07/14/2017 02:19 PM, Mr. DONG wrote:
> 
> > > 
> > Unfortunately that doesn't work either.
> > 
> > The "qvm-usb -l" doesn't show my legder nano s. In fact I can only
> > see it attached on the sys-usb, not on dom0.
> > 
> > The qvm-usb list output shows no difference either I attach or not
> > the HW wallet. The only way I can attach to another appvm is if I
> > attach the entire PCI controller, via the usb-passthrough does not
> > work.
> > 
> > Any alternatives?
> > 
> > On 14 July 2017 at 10:48 Patrik Hagara 
> > wrote:
> > 
> > On 07/14/2017 02:54 AM, 'Essax' via qubes-users wrote:
> > 
> > Have you tried these steps:
> > 
> > 1) Attach hardware wallet to sys-usb 2) Go to the dom0 Gui and and
> > right click on the appVM you want to attach it to. 3) In the box
> > that opens scroll down to Attach/detach block devices and your
> > hardware wallet should show up to the right. 4) Right click on
> > your hardware wallet to attach it to your appVM.
> > 
> > /Essa*x*/
> > 
> >  Original Message  Subject: [qubes-users] Re:
> > Working with a BTC hardware wallet on Qubes Local Time: July 13,
> > 2017 4:23 PM UTC Time: July 13, 2017 8:23 PM From: p...@mailbox.org
> > To: qubes-users@googlegroups.com
> > 
> > I do have a sys-usb vm, however I cannot attach a netVM to it since
> > the sys-usb is also a netvm.
> > 
> > I possibly will need to create a new sys-usb vm or is there any
> > other alternative?
> > 
> > Attaching it as a block device won't work, since bitcoin hardware
> > wallet is not a mass storage device. Luckily, it's not emulating a
> > HID device either, which would get picked up by the dom0 USB
> > keyboard/mouse input proxy. Thus, there's no graphical means of
> > attaching USB bitcoin hardware wallet in Qubes to another VM...
> > 
> > You can, however, attach it via the qvm-usb command line tool:
> > 
> > 1) connect the bitcoin hardware wallet 2) in dom0 terminal, run
> > |qvm-usb -l| to list USB devices attached 3) locate the line with
> > bitcoin wallet and note the first column (eg. "sys-usb:2-1.6") 4)
> > run |qvm-usb -a bitcoin sys-usb:2-1.6| from a dom0 terminal to
> > attach the wallet to bitcoin AppVM
> > 
> > Cheers, Patrik
> > 
> > > 
> Most likely you don't have qubes-usb-proxy installed in the sys-usb's
> template (make sure to also install this package in the target bitcoin
> banking AppVM's template). See [1] for more info.
> 
> [1]
> https://www.qubes-os.org/doc/usb/#attaching-a-single-usb-device-to-a-qub
> e-usb-passthrough
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iQIcBAEBCAAGBQJZaMnNAAoJEFwecd8DH5rlmTkP/jiwIpUlTMr6OMEUw3afH46X
> h1Z+hcADH40Z1M2FVTH3oqginIjoGs0kJyd490vcpaic3Js1EO6+I0eXtvF4n2qt
> J5LWSHQ/AQg3xjfBAFSsl2kEXnNa0CGF9hl0ZLCJOaHKcbpcJfS69fH79kT7KtJG
> KJ4bOgENGCHaxgHb6vqtvdaYgnj8ltHqRvIZjwThai1PBsQcmw1HSf+uBMzQNRFw
> 5E39a1Rb6vkvpdG1EDjEXrtzU8TdLH/96eCGODD0+t6vbAAp0t9EEheeqFjDdtz1
> 65FNUWYx+WxkCvjcDaMK6GR/NY447C9cCM3xm55rQlFH7/vzH9CkMTM52+ZW0bqB
> 27B8d+BatKYaIKQbrxHBWxdN7LDsJkcr+YHVHGt2F7nqt14LsLaRf+52gj6A+MHq
> utn+5cVUpVT//GKlox+vEwfxZC/TjRqr4Im6tqAWQX+OZrpH9q4yP+asb6Ca2YdY
> 3K9qoJZmtUVCaMiVQLqTRcjzHdVpMllS7scSs4wcJDHvi+KxhIOafG3iH2zAx7VC
> CKXj2JltK7BXv4rlRUmcsIO6f4vTq/ylzZ4pP9bUp3VuQQum3wJ4dQnC9GdOoN6B
> rTwgfZ5ovA+Fo37FVdRR6k5tc/Gh1emhiFHNfOMAtO6364O0GxWo6NkERTHhVF94
> ZdhPoB3Ggx9FoTiAyNPI
> =9Dw6
> -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/1441642922.1727.1500046931339%40office.mailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

2017-07-14 Thread Patrik Hagara 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/14/2017 02:19 PM, Mr. DONG wrote:
> Unfortunately that doesn't work either.
> 
> The "qvm-usb -l" doesn't show my legder nano s. In fact I can only
> see it attached on the sys-usb, not on dom0.
> 
> The qvm-usb list output shows no difference either I attach or not
> the HW wallet. The only way I can attach to another appvm is if I
> attach the entire PCI  controller, via the usb-passthrough does not
> work.
> 
> 
> Any alternatives?
> 
> 
> 
> 
> On 14 July 2017 at 10:48 Patrik Hagara 
> wrote:
> 
> On 07/14/2017 02:54 AM, 'Essax' via qubes-users wrote:
> 
> Have you tried these steps:
> 
> 1) Attach hardware wallet to sys-usb 2) Go to the dom0 Gui and and 
> right click on the appVM you want to attach it to. 3) In the box 
> that opens scroll down to Attach/detach block devices and your 
> hardware wallet should show up to the right. 4) Right click on
> your hardware wallet to attach it to your appVM.
> 
> /Essa*x*/
> 
>  Original Message  Subject: [qubes-users] Re: 
> Working with a BTC hardware wallet on Qubes Local Time: July 13, 
> 2017 4:23 PM UTC Time: July 13, 2017 8:23 PM From: p...@mailbox.org
> To: qubes-users@googlegroups.com
> 
> I do have a sys-usb vm, however I cannot attach a netVM to it since
> the sys-usb is also a netvm.
> 
> I possibly will need to create a new sys-usb vm or is there any 
> other alternative?
> 
> Attaching it as a block device won't work, since bitcoin hardware 
> wallet is not a mass storage device. Luckily, it's not emulating a
> HID device either, which would get picked up by the dom0 USB 
> keyboard/mouse input proxy. Thus, there's no graphical means of 
> attaching USB bitcoin hardware wallet in Qubes to another VM...
> 
> You can, however, attach it via the qvm-usb command line tool:
> 
> 1) connect the bitcoin hardware wallet 2) in dom0 terminal, run
> |qvm-usb -l| to list USB devices attached 3) locate the line with
> bitcoin wallet and note the first column (eg. "sys-usb:2-1.6") 4)
> run |qvm-usb -a bitcoin sys-usb:2-1.6| from a dom0 terminal to 
> attach the wallet to bitcoin AppVM
> 
> Cheers, Patrik

Most likely you don't have qubes-usb-proxy installed in the sys-usb's
template (make sure to also install this package in the target bitcoin
banking AppVM's template). See [1] for more info.

[1]
https://www.qubes-os.org/doc/usb/#attaching-a-single-usb-device-to-a-qub
e-usb-passthrough
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZaMnNAAoJEFwecd8DH5rlmTkP/jiwIpUlTMr6OMEUw3afH46X
h1Z+hcADH40Z1M2FVTH3oqginIjoGs0kJyd490vcpaic3Js1EO6+I0eXtvF4n2qt
J5LWSHQ/AQg3xjfBAFSsl2kEXnNa0CGF9hl0ZLCJOaHKcbpcJfS69fH79kT7KtJG
KJ4bOgENGCHaxgHb6vqtvdaYgnj8ltHqRvIZjwThai1PBsQcmw1HSf+uBMzQNRFw
5E39a1Rb6vkvpdG1EDjEXrtzU8TdLH/96eCGODD0+t6vbAAp0t9EEheeqFjDdtz1
65FNUWYx+WxkCvjcDaMK6GR/NY447C9cCM3xm55rQlFH7/vzH9CkMTM52+ZW0bqB
27B8d+BatKYaIKQbrxHBWxdN7LDsJkcr+YHVHGt2F7nqt14LsLaRf+52gj6A+MHq
utn+5cVUpVT//GKlox+vEwfxZC/TjRqr4Im6tqAWQX+OZrpH9q4yP+asb6Ca2YdY
3K9qoJZmtUVCaMiVQLqTRcjzHdVpMllS7scSs4wcJDHvi+KxhIOafG3iH2zAx7VC
CKXj2JltK7BXv4rlRUmcsIO6f4vTq/ylzZ4pP9bUp3VuQQum3wJ4dQnC9GdOoN6B
rTwgfZ5ovA+Fo37FVdRR6k5tc/Gh1emhiFHNfOMAtO6364O0GxWo6NkERTHhVF94
ZdhPoB3Ggx9FoTiAyNPI
=9Dw6
-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/2b98b7a2-921a-c18f-f079-88a1e5fe752d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


0x031F9AE5.asc
Description: application/pgp-keys


0x031F9AE5.asc.sig
Description: PGP signature

Re: [qubes-users] i3 not working on two screens

2017-07-14 Thread Noor Christensen 
On Fri, Jul 14, 2017 at 04:07:15AM -0700, zioasterb...@gmail.com wrote:
> Yes, by "separating them" i mean to extend the desktop to two screens,
> since now I see them mirrored (i.e. the eternal one is a copy of the
> laptop's display)

You can use xrandr to set up the different display outputs.

For example, the following command defines my external display (VGA1) as
being positioned to the right of my internal display (LVDS1):

$ xrandr --output VGA1 --right-of LVDS1 --preferred

To get the names of your display outputs, run xrandr without flags:

$ xrandr

It's a bit unclear whether or not you are using XFCE or i3wm as your
window manager, but the xrandr method should be effective in either
case. 

Another solution is to set up your xorg.conf properly, so your desired
display outputs are configured when X starts, before any window manager
is run.

Here is an example config for a Thinkpad X220:

Section "Device"
# Specify the device we are configuring
Identifier "Intel HD 3000"
Driver "intel"
BusID  "PCI:0:2:0" # Video card PCI address

# Give friendly names to the display outputs
Option "Monitor-LVDS1" "LCD"
Option "Monitor-VGA1"  "VGA"
EndSection

# Internal monitor (LVDS1)
Section "Monitor"
Identifier "LCD"
Option "Enable" "true"
Option "PreferredMode" "1366x768"
EndSection

# External monitor (VGA1)
Section "Monitor"
Identifier "VGA"
Option "Enable" "true"
Option "PreferredMode" "1680x1050" # Acer AL2216W
Option "RightOf" "LCD"
EndSection

This config has the same effect as the xrandr example shown before -
external display output VGA1 positioned to the right of LVDS1.

You can put the file in /etc/X11/xorg.conf.d and it will be read by X on
next start.

Use the "Enable" option to specify whether you want it to activate on X
start, or manually (via xrandr). See the documentation for X.org and the
graphics driver you are using for more options.

NOTE: You probably have to replace some/all values to fit your specific
scenario. Obviously the "Device" section (first paragraph) of the
xorg.conf in particular, but also the xrandr parameters.

-- noor

|_|O|_|
|_|_|O|  Noor Christensen  
|O|O|O|  n...@fripost.org ~ 0x401DA1E0

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


signature.asc
Description: PGP signature

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

2017-07-14 Thread Mr. DONG 
Unfortunately that doesn't work either.

The "qvm-usb -l" doesn't show my legder nano s. In fact I can only see it 
attached on the sys-usb, not on dom0.

The qvm-usb list output shows no difference either I attach or not the HW 
wallet. The only way I can attach to another appvm is if I attach the entire 
PCI  controller, via the usb-passthrough does not work.


Any alternatives?




> 
> On 14 July 2017 at 10:48 Patrik Hagara  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On 07/14/2017 02:54 AM, 'Essax' via qubes-users wrote:
> 
> > > 
> > Have you tried these steps:
> > 
> > 1) Attach hardware wallet to sys-usb 2) Go to the dom0 Gui and and
> > right click on the appVM you want to attach it to. 3) In the box
> > that opens scroll down to Attach/detach block devices and your
> > hardware wallet should show up to the right. 4) Right click on your
> > hardware wallet to attach it to your appVM.
> > 
> > /Essa*x*/
> > 
> > > > > 
> > >  Original Message  Subject: [qubes-users] Re:
> > > Working with a BTC hardware wallet on Qubes Local Time: July 
> > > 13,
> > > 2017 4:23 PM UTC Time: July 13, 2017 8:23 PM From:
> > > p...@mailbox.org To: qubes-users@googlegroups.com
> > > 
> > > I do have a sys-usb vm, however I cannot attach a netVM to it
> > > since the sys-usb is also a netvm.
> > > 
> > > I possibly will need to create a new sys-usb vm or is there 
> > > any
> > > other alternative?
> > > 
> > > > > 
> > > 
> Attaching it as a block device won't work, since bitcoin hardware
> wallet is not a mass storage device. Luckily, it's not emulating a HID
> device either, which would get picked up by the dom0 USB
> keyboard/mouse input proxy. Thus, there's no graphical means of
> attaching USB bitcoin hardware wallet in Qubes to another VM...
> 
> You can, however, attach it via the qvm-usb command line tool:
> 
> 1) connect the bitcoin hardware wallet
> 2) in dom0 terminal, run qvm-usb -l to list USB devices attached
> 3) locate the line with bitcoin wallet and note the first column (eg.
> "sys-usb:2-1.6")
> 4) run qvm-usb -a bitcoin sys-usb:2-1.6 from a dom0 terminal to
> attach the wallet to bitcoin AppVM
> 
> Cheers,
> Patrik
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iQIcBAEBCAAGBQJZaIU1AAoJEFwecd8DH5rlHfsP/1jkZ1IDWrTy60wBno/MUIU7
> bVzDx7i81zRWdIaDn4d7rl6DrTetGmqa7MZLferLNilZldA/DymTrXH33/+Ewvfu
> JCGtc4BpNkkigOV+fjj7ov49flEjCP1nIDoZK3PzHvxN8lS6MnuGIPnbw+z97cew
> aOJAoZqFhaWO9oj31x/fiLqAjl+oYodU4n7L/342Xn7qmc1AiFtURzA9yVBJNoyW
> 6nfdmKKBSEUkdsbvhNTIznAqbfKg35Xf9lZOflO0CjTg2o+TCFIoLexceCi1IgaB
> +k10IF9BkYkimF0GclplZ4dZ9w/G2iL2bheXBy0gWL15dTsasM3PJgmjj2HEusIA
> xlg6EetjmDF8roUym8QldepNsIAPW5/8SuXz4vkl5uxChh54V+BMQx3cBGImVxSf
> UwM+hd8/1pfyMmAmsYiK+UFX3rHdIdBKTxEuJjZrJhqRjAnpymBjGe1clwkE4ziy
> 33VeRSqKi4s46yhH2NpjXmCL256na/seNdILAYBlLW15tXgQCKUFZ9EI6Sj3Z4GZ
> qhAnlsuN3yXZ/FX/vv+SLkZpNGKdZj7bqbuJx0j3rtMfXdx0yJPBEeEQjkGzWz/5
> tNy9N2V0C+f0LKpXIMNd8npEOyFBKmb9HL8NNcb7u9IQvMEx6YCArcbqqw5ElOix
> UJGME31rhswPB/0vLAil
> =frd+
> -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/1478102745.308.1500034795491%40office.mailbox.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Debian Buster repo

2017-07-14 Thread ali . mirjamali 
On Friday, June 23, 2017 at 11:04:01 PM UTC+4:30, Dominique St-Pierre Boucher 
wrote:
> Hello,
> 
> Anyone switched their template from Stretch to Buster? I want to try but 
> there is no qubes repo for it!!
> 
> Dominique

Hi Dominique.

I cloned my Debian Stretch template last night and gave it a shot:

user@debian-10:~$ screenfetch
 _,met$gg.   user@debian-10
  ,g$$$P.OS: Debian testing buster
,g$$P""   """Y$$.".  Kernel: x86_64 Linux 
4.9.35-19.pvops.qubes.x86_64
   ,$$P'  `$$$.  Uptime: 25m
  ',$$P   ,ggs. `$$b:Packages: 2188
  `d$$' ,$P"'   .$$$ Shell: bash 4.4.12
   $$P  d$' ,$$P Resolution: 1368x768
   $$:  $$.   -,d$$' DE: GNOME
   $$\;  Y$b._   _,d$P'  WM: Qubes
   Y$$.`.`"YP"'  GTK Theme: Adwaita [GTK2/3]
   `$$b  "-.__   Icon Theme: Adwaita
`Y$$ Font: Cantarell 11
 `Y$$.   CPU: Intel Core i7-3667U @ 2x 2.494GHz [60.0°C]
   `$$b. GPU: Gallium 0.4 on llvmpipe (LLVM 3.9, 256 
bits)
 `Y$$b.  RAM: 175MiB / 574MiB
`"Y$b._
 
I only changed /etc/apt/sources.list to buster repos, using Qubes repos for 
Stretch.

Qubes QUI agent works. Qubes VCHAN Sink sound interface works. Clipboard works. 
Copying files between VMs is also OK.

I will keep this experimental Debian Buster Template-VM and will track the 
developments.

-- 
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/81fadcf5-a188-4f9a-9d37-3954659d734b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] i3 not working on two screens

2017-07-14 Thread zioasterbald 
Yes, by "separating them" i mean to extend the desktop to two screens, since 
now I see them mirrored (i.e. the eternal one is a copy of the laptop's display)


I adopted the solution listed here, but with no success at all  (it just 
changed the border of the windows in i3)
https://github.com/QubesOS/qubes-issues/issues/2084



On Friday, July 14, 2017 at 12:21:05 PM UTC+2, Noor Christensen wrote:
> On Thu, Jul 13, 2017 at 12:37:27PM -0700, zioasterb...@gmail.com wrote:
> > Hi,
> > I've just tried i3 on qubes3.2 but there is an issue with my external
> > monitor. I cannot separate them, even when I split and dispose
> > properly the screen in the settings, as you can see in the image. The
> > screens did not even refresh. 
> 
> Could you elaborate what you mean by "separating them"? 
> 
> Are the monitors showing the same image, and you want to have two
> separate desktops instead?
> 
> -- noor
> 
> |_|O|_|
> |_|_|O|  Noor Christensen  
> |O|O|O|  n...@fripost.org ~ 0x401DA1E0

-- 
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/5076aaa2-770c-4bbf-9da1-0e58801cdad8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [marma...@invisiblethingslab.com: [qubes-devel] Fedora 25 template for Qubes 3.2]

2017-07-14 Thread Noor Christensen 
Good news everyone!

/noor

- Forwarded message from Marek Marczykowski-Górecki 
 -

From: Marek Marczykowski-Górecki 
To: qubes-devel 
Date: Thu, 13 Jul 2017 22:49:53 +0200
Subject: [qubes-devel] Fedora 25 template for Qubes 3.2

Hi all,

We've uploaded Fedora 25 template for Qubes 3.2. It was already possible
to perform in-place upgrade[1], but now we also provide full template.

You can install it with:

sudo qubes-dom0-update qubes-template-fedora-25

We've tested it internally, but you can help us here too!
This is one of things to be included in Qubes 3.2.1.

[1] https://www.qubes-os.org/doc/template/fedora/upgrade-24-to-25/


- End forwarded message -

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


signature.asc
Description: PGP signature

Re: [qubes-users] i3 not working on two screens

2017-07-14 Thread Noor Christensen 
On Thu, Jul 13, 2017 at 12:37:27PM -0700, zioasterb...@gmail.com wrote:
> Hi,
> I've just tried i3 on qubes3.2 but there is an issue with my external
> monitor. I cannot separate them, even when I split and dispose
> properly the screen in the settings, as you can see in the image. The
> screens did not even refresh. 

Could you elaborate what you mean by "separating them"? 

Are the monitors showing the same image, and you want to have two
separate desktops instead?

-- noor

|_|O|_|
|_|_|O|  Noor Christensen  
|O|O|O|  n...@fripost.org ~ 0x401DA1E0

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


signature.asc
Description: PGP signature

Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes

2017-07-14 Thread Patrik Hagara 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/14/2017 02:54 AM, 'Essax' via qubes-users wrote:
> Have you tried these steps:
> 
> 1) Attach hardware wallet to sys-usb 2) Go to the dom0 Gui and and
> right click on the appVM you want to attach it to. 3) In the box
> that opens scroll down to Attach/detach block devices and your
> hardware wallet should show up to the right. 4) Right click on your
> hardware wallet to attach it to your appVM.
> 
> /Essa*x*/
> 
>>  Original Message  Subject: [qubes-users] Re:
>> Working with a BTC hardware wallet on Qubes Local Time: July 13,
>> 2017 4:23 PM UTC Time: July 13, 2017 8:23 PM From:
>> p...@mailbox.org To: qubes-users@googlegroups.com
>> 
>> I do have a sys-usb vm, however I cannot attach a netVM to it
>> since the sys-usb is also a netvm.
>> 
>> I possibly will need to create a new sys-usb vm or is there any
>> other alternative?


Attaching it as a block device won't work, since bitcoin hardware
wallet is not a mass storage device. Luckily, it's not emulating a HID
device either, which would get picked up by the dom0 USB
keyboard/mouse input proxy. Thus, there's no graphical means of
attaching USB bitcoin hardware wallet in Qubes to another VM...

You can, however, attach it via the qvm-usb command line tool:

1) connect the bitcoin hardware wallet
2) in dom0 terminal, run `qvm-usb -l` to list USB devices attached
3) locate the line with bitcoin wallet and note the first column (eg.
"sys-usb:2-1.6")
4) run `qvm-usb -a bitcoin sys-usb:2-1.6` from a dom0 terminal to
attach the wallet to bitcoin AppVM


Cheers,
Patrik
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZaIU1AAoJEFwecd8DH5rlHfsP/1jkZ1IDWrTy60wBno/MUIU7
bVzDx7i81zRWdIaDn4d7rl6DrTetGmqa7MZLferLNilZldA/DymTrXH33/+Ewvfu
JCGtc4BpNkkigOV+fjj7ov49flEjCP1nIDoZK3PzHvxN8lS6MnuGIPnbw+z97cew
aOJAoZqFhaWO9oj31x/fiLqAjl+oYodU4n7L/342Xn7qmc1AiFtURzA9yVBJNoyW
6nfdmKKBSEUkdsbvhNTIznAqbfKg35Xf9lZOflO0CjTg2o+TCFIoLexceCi1IgaB
+k10IF9BkYkimF0GclplZ4dZ9w/G2iL2bheXBy0gWL15dTsasM3PJgmjj2HEusIA
xlg6EetjmDF8roUym8QldepNsIAPW5/8SuXz4vkl5uxChh54V+BMQx3cBGImVxSf
UwM+hd8/1pfyMmAmsYiK+UFX3rHdIdBKTxEuJjZrJhqRjAnpymBjGe1clwkE4ziy
33VeRSqKi4s46yhH2NpjXmCL256na/seNdILAYBlLW15tXgQCKUFZ9EI6Sj3Z4GZ
qhAnlsuN3yXZ/FX/vv+SLkZpNGKdZj7bqbuJx0j3rtMfXdx0yJPBEeEQjkGzWz/5
tNy9N2V0C+f0LKpXIMNd8npEOyFBKmb9HL8NNcb7u9IQvMEx6YCArcbqqw5ElOix
UJGME31rhswPB/0vLAil
=frd+
-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/a23c09e8-6e01-1457-6fc4-d549f604a87a%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


0x031F9AE5.asc
Description: application/pgp-keys


0x031F9AE5.asc.sig
Description: PGP signature

Re: [qubes-users] How can I test that my AEM configuration is correct?

2017-07-14 Thread Patrik Hagara 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/14/2017 09:45 AM, loke...@gmail.com wrote:
> On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki 
> wrote:
> 
>> Oh, it isn't listed in updates-status[1], so I completely forgot.
>> Probably it was uploaded to testing before introducing that
>> system. Of course it should be migrated to current, will do.
> 
> I updated to the latest AEM, but after I did that, nothing worked 
> anymore. I outlined it in this post, but no one replied to it. Is 
> there anything I can do to collect more information?
> 
> https://groups.google.com/forum/#!topic/qubes-users/JMipWyv2heU
> 
> Regards, Elias
> 

This error means that your AEM setup never worked, even before
updating. The AEM boot would always succeed no matter what, even if a
hundred evil maids tampered with it.

Did you follow the AEM installation instruction to the letter? Do you
have Intel TXT enabled in BIOS? Did you download the right SINIT
module and add it to the GRUB config as a module loaded last? Does
GRUB load the SINIT module successfully?

If it still doesn't work, try fully resetting the TPM (usually only
possible from the BIOS) and setting it up again.

See the relevant GitHub issue [1] for details.


Cheers,
Patrik


[1] https://github.com/QubesOS/qubes-issues/issues/2569
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZaH3KAAoJEFwecd8DH5rl2QIP/0dUdW+8Ld74b5McCW5g7HVu
YMTJFORcRRr6/8yyS1h+yplwB4osnI16PhsTNYSJTjMmy/pkKNIm9e9PWE0oOSp7
aVpFKnNVuuupvDFuehJMjtw5fsPkckTbBFBfVIld48Ei/r/C0cTCtU3KTma0BNRN
BJsfN6DuB9bfctbqrywox4l1TyOGlcp0ToVvDB5VQ6zc0gt1qfLfHSd79Il2CrpH
+NqHPbOmLNNAzAEd7iLuoR80mD4AE3tDJBu1RFrIgBHt1Jgu1lxcKjjC2fHHP9Sh
hKZ/TwvbXphGEndLh6vYzuCLCdhvxj/pn2pxJBPWelWiZ3H9PRdmnJ50iNUob/+m
ioS0/NA3hzm0tlTfXpk5AiE964EzbeHokOjJgm6vwgiwELqOviiRwPy8FetjXqMR
Iea39hgKGBAKahbKDEBTkWYW15RjKmG0McjszR7C8e80KVAuaXQyczUU86xyzH8D
jY9mQiM1aliNsRwCKAsq7bHBnozcewYX2WdPqkr9eqd75Gj3Jfnu1Kwi4RSvrbdA
H/Kbx1WxK0deAVT5pxfF1VQTT3h1efZqKZn+BElf2F3f9dk7mp2FOwpe4Sfb+HhT
UpSDV4DE//eCCLYVy5um7iVqKg4n0km0kRIf+/2CVJsQd/P839KDmdsxVf8KjAab
JJXtks6Wai807VtbGHcV
=Bvxj
-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/764dee58-ec40-4b8f-b642-776108b376b5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


0x031F9AE5.asc
Description: application/pgp-keys


0x031F9AE5.asc.sig
Description: PGP signature

Re: [qubes-users] How can I test that my AEM configuration is correct?

2017-07-14 Thread lokedhs 
On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki  wrote:

> Oh, it isn't listed in updates-status[1], so I completely forgot.
> Probably it was uploaded to testing before introducing that system. Of
> course it should be migrated to current, will do.

I updated to the latest AEM, but after I did that, nothing worked anymore. I 
outlined it in this post, but no one replied to it. Is there anything I can do 
to collect more information?

https://groups.google.com/forum/#!topic/qubes-users/JMipWyv2heU

Regards,
Elias

-- 
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/3ca8e6a9-35d7-48f2-a271-8887f8d97070%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Just realized one of the major disadvantages of Qubes OS...

2017-07-14 Thread Alex 
On 07/14/2017 05:30 AM, motech man wrote:
> On Thursday, July 13, 2017 at 12:05:34 PM UTC-5, geoff.m...@gmail.com
> wrote:
>> A bit of thread necromancy here, but - if you're using a smartphone
>> in the US with mobile data, there's a *very* good chance you're
>> already using IPv6.
>> [...]>>
>> --Geo
> 
> I also expect to see routers for home market that will talk ipv6
> externally and ipv4 internally. That will help a lot of people
> transition.
Here in Italy (and a lot of other countries too) home routers just
started distributing /64 internally, in full dual-stack mode, during
this spring for the major ISPs.

Public institutions are expected to be fully dual-stack connected and
publicly available by the end of the year by law.

I don't see any advantage in having a situation like you described - why
not just full dual stack, and the devices connect to the technology they
support?

Apart from us qubes aficionados, any win10 pc, apple or android device,
and the vast majority of linux workstation/server distros fully support
dual stack configurations, and happily work preferring ipv6 when available.

-- 
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/809adbd0-7716-c7b8-9adf-df3d56787d34%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: How do I upgrade to Fedora 26?

2017-07-14 Thread Alex 
On 07/14/2017 12:59 AM, Salmiakki wrote:
> But those should work in 3.2 just fine, right?
> 
Probably not; both because forcing the repository to the 4.0 will try to
upgrade a lot of other system components, so the actual update may
involve very convoluted command lines to avoid anything but the
template, and because AFAIR the architecture for 4.0 should be different
enough for the qubes-vm-tools not to work correctly (or at all, I don't
know).

It's strange that the templates are in one repo and not in the other,
especially since fedora 25 works perfectly in qubes 3.2, and you can get
that just upgrading the fedora 24 template.

-- 
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/923a9d20-7f10-e192-008a-7f66a9880f7a%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: How do I upgrade to Fedora 26?

2017-07-14 Thread Alex 
On 07/14/2017 01:00 AM, Salmiakki wrote:
>> The problem is that there are no yum sources for qubes-related things
>> for fedora 26, as Foppe said, so the upgrade will likely fail and, in
>> case you manage to complete the upgrade, you will be left with a
>> non-updatable set of qubes software for a while.
> 
> So where do people who make their own templates get these things?
I started cloning the original fedora 24 template, which is already
configured for the correct yum repositories, and upgraded that to 25.
Since the yum config is dynamically expanded to the actual distro
release number, it just works. I'm on Qubes R3.2, and I don't understand
both why the fedora 25 template is missing from the 3.2 repository and
why a user should wait for such a template to be available in the
repository, while he/she could just clone the 24 and update that, if
having a cutting-edge-stable system is important in their scenario
(like, in mine it is so I did just that).

If you start with a template from scratch you can either use the yum
repositories or the debian ones, depending on what your distribution
supports, or you can include a specific version of the tools you
compile/make yourself - the vast majority of them is in Python, so there
should be little trouble using them in another distro. If you do include
a specific version updates will likely have to be manually detected and
installed, unless you also set up a custom repository and package
manager system and maintain that.

-- 
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/8e07a47a-58aa-6464-3180-d61e14d1b1d6%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature