date:20161204

On Sunday, December 4, 2016 at 5:13:19 PM UTC-5, Patrick Bouldin wrote:
> On Sunday, December 4, 2016 at 4:00:47 PM UTC-5, Patrick Bouldin wrote:
> > Hi, after returning to Qubes (I waited for 3.2 since my video was having 
> > issues) - seems to be working fine now.
> > 
> > However, when the machine times out into sleep, and if I've turned off my 
> > hdmi monitor I can't seem to wake up the video. I can tell Qubes is 
> > running, but have tried many ways to wake up the hdmi, haven't found a way.
> > 
> > Any suggestions?
> > 
> > Thanks,
> > Patrick
> 
> ** Update **
> 
> I just discovered that turning off the hdmi monitor may be putting the cpu to 
> sleep and locking the keyboard. If I momentarily push the power button and 
> hit the keyboard or mouse it will come up with the hdmi monitor asking for a 
> password. Maybe I'm about to be embarrassed that this is in the doc? Or is it 
> a machine based variable?
> 
> Thank you,
> Patrick

** 2nd update ** while the above update is true, unfortunately when the machine 
hibernates the only thing that brings the display back is a cold boot.

So it seems to be associated with losing the hdmi somehow - causing the machine 
not to be responsive to keyboard wake-up.

Any clues?

Thanks,
Patrick

-- 
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/9ff17cb2-8132-4d77-907b-e68251f8d3be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes OS v3.2 on Chromebook Pixel 2015

2016-12-04 Thread rspeiglvera

On Saturday, December 3, 2016 at 9:04:32 PM UTC-8, rspei...@gmail.com wrote:
> On Saturday, December 3, 2016 at 7:19:08 PM UTC-8, raah...@gmail.com wrote:
> > On Saturday, December 3, 2016 at 7:09:25 PM UTC-5, rspei...@gmail.com wrote:
> > > I've tried to install Qubes on my Pixel twice. The install boots nicely 
> > > and everything seems to go well. Once I reboot, the boot process gets 
> > > hung up and never makes it past to the decryption step.
> > > 
> > > Any ideas or recommendations?
> > 
> > bios settings?
> 
> The Chromebook has legacy bios support through SeaBios on CoreBoot. There 
> isn't anything to setup.

Basically after a successful installation of Qubes and rebooting the laptop 
gets to this message:
"Booting from Hard Disk..."
And nothing happens. It just hangs there.




-- 
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/22ae2b8f-60b0-4685-a702-456803efc9cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [possible bug] after restoring from backup hwm template not at the list of creating new vm


On 12/05/2016 04:00 AM, Eva Star wrote:

After restoring system from backup I have win7template at the list of
VM. QubesManager show it with TYPE TemplateHVM
But at the Create New Vm this template does not listed.
How to fix?
Bug?



Sorry! Found the solution. Need to remove default checkbox from 
"Standalone" to get it on the list.



--
Regards

--
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/2faa2147-e57b-c634-809d-254e4e855efa%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [possible bug] after restoring from backup hwm template not at the list of creating new vm

After restoring system from backup I have win7template at the list of 
VM. QubesManager show it with TYPE TemplateHVM

But at the Create New Vm this template does not listed.
How to fix?
Bug?


--
Regards

--
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/e1e04ce5-74ca-28bd-9fc2-6fa50caa1a86%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Install on Dell XPS 13 (9350)

2016-12-04 Thread miaoski

Hi Marek,

Thanks for the suggestion.  Just tried kernel 4.8.12_12 but same dmesg popped 
up.

Will try to copy a working firmware and parameters tonight.


Thanks
Miaoski

-- 
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/da99a1b2-e52c-4504-a290-b8671817f007%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2016-12-04 Thread zachkeaton93

Could you PM me one as well?

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

Re: [qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Dec 04, 2016 at 12:18:23AM -0800, Benjamin Richter wrote:
> Am Sonntag, 4. Dezember 2016 01:33:31 UTC+1 schrieb Marek 
> Marczykowski-Górecki:
> 
> > > I've attached the ethernet dongle to the same port as the logitech 
> > > keyboard, but it does not show up anywhere.
> > 
> > If you see the device in dom0 in some configuration, take a look at its
> > sysfs path - it will have a hint on which controller is it. Like this:
> > lrwxrwxrwx 1 root root 0 Dec  4 01:32 /sys/bus/usb/devices/3-1 ->
> > ../../../devices/pci-0/pci:00/:00:02.0/usb3/3-1
> > 
> > - -- 
> > 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-
> > Version: GnuPG v2
> > 
> > iQEcBAEBCAAGBQJYQ2RWAAoJENuP0xzK19csKxMH/3rkY6pxlWVSjltPRc1r2jGn
> > njWyqDEA6Zoe56gAQ3zS1ORX54hgpEw6omZgzB3bY9KI2U3ihLncJ4jF8mVwxa+S
> > rTCFF1Flqp8Olk2jTXc2lobdLcOQBMQXXfNq4GbpHkl0C+ZVIa1n7lndfJI9WA21
> > TKA3gsW/SY8EgBjYtFO0Emnhr5WMi3jYyt/qSWU8jrYn92IoZnx6CbpQp8xA/S8L
> > KLvt7WUnBjuFX+k4z9hodXHq6eU00YNqOEI4fm0+y92PPSjIGKbDhClCstSMMXRE
> > RqlbJmWpBasYBPm2pOg+1C0Vkeg593TtxahLd2k8MuFZUjrCjY4OXwA7+YkHFRA=
> > =4hF8
> > -END PGP SIGNATURE-
> 
> That's really quite clear, here's a lsusb output from dom0 with both usb 
> controllers. Here the ASIX and Realtek ethernet deivces show up on bus 004.
> 
> Bus 004 Device 004: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
> Ethernet
> Bus 004 Device 005: ID 0bda:8153 Realtek Semiconductor Corp. 
> Bus 004 Device 003: ID 05e3:0620 Genesys Logic, Inc. 
> Bus 004 Device 002: ID 05e3:0620 Genesys Logic, Inc. 
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 004: ID 046d:c51e Logitech, Inc. 
> Bus 003 Device 007: ID 1e4e:0898 Cubeternet 
> Bus 003 Device 006: ID 0572:1703 Conexant Systems (Rockwell), Inc. 
> Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
> Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 004: ID 0b05:1838 ASUSTek Computer, Inc. 
> Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
> Bus 001 Device 002: ID 04f2:b5b1 Chicony Electronics Co., Ltd 
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> lsusb of dom0 after attaching the controller to sys-net:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 004: ID 0b05:1838 ASUSTek Computer, Inc. 
> Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
> Bus 001 Device 002: ID 04f2:b5b1 Chicony Electronics Co., Ltd 
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> and of sys-net:
> sudo lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 002 Device 004: ID 046d:c51e Logitech, Inc. 
> Bus 002 Device 006: ID 1e4e:0898 Cubeternet 
> Bus 002 Device 005: ID 0572:1703 Conexant Systems (Rockwell), Inc. 
> Bus 002 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
> Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> The Logitech keyboard attached to the docking station is there, but neither 
> the asix dongle nor the docks ethernet port show up. It seems dom0s usb bus 
> 004 got lost somewhere.
> Interestingly, if I switch the ethernet dongle and the logitech keyboard, the 
> keyboard shows up on another port, but the dongle does not show up.
> 
> I have no idea what's going on.

It looks like none of devices from that bus show up (just root hub).
Anything interesting in dmesg there? I'd recommend looking for more than
just "grep usb" - for example some messages may contain only xhci, or
just pci BDF.

- -- 
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-
Version: GnuPG v2

iQEcBAEBCAAGBQJYRJG7AAoJENuP0xzK19csxUMIAIRJL6cJEwZhTWJ6+VubNKl1
nlZ//ruZ39jmXevc3GCQQydxyxcpF96ZXXTeAHjHp977nLSqByeD1DjdJdaIrCVW
MExKtvHWX3Bz7ddgMdoIWAGF8j4VbLC4thjgxFxuvbnHYVcZcq31CXb8ipcKXyTl
YyNMSEhAtx+FLIk0NNI+mlVLpUEfg2fGH1bRCewkY+Ptu9PingXi+M/AR4BIAACt
ri8nVL3yhAIcxoeV3sdBPnSEzijb6iBBz7KpbGvSsxRgua3cYuGJnKCrZ2oTv6CF
vEbr5ekTIHOuhj12T5kvqPRtTOR4RWCN69brGksMjMSjN9zyYGHQSVytRZesA/Q=
=r5Zg
-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: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

On Wednesday, November 30, 2016 at 6:56:11 PM UTC-5, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Dear Qubes Community,
> 
> Since the initial launch [01] of Qubes OS back in April 2010, work on Qubes
> has been funded in several different ways.  Originally a pet project, it was
> first supported by Invisible Things Lab [02] (ITL) out of the money we earned
> on various R and consulting contracts. Later, we decided that we should try 
> to
> commercialize it. Our idea, back then, was to commercialize Windows AppVM
> support.  Unlike the rest of Qubes OS, which is licensed under GPLv2, we 
> thought
> we would offer Windows AppVM support under a proprietary license. Even though 
> we
> made a lot of progress on both the business and technical sides of this
> endeavor, it ultimately failed.
> 
> Luckily, we got a helping hand from the Open Technology Fund [03] (OTF), which
> has supported [04] the project for the past two years. While not a large
> sum of money in itself, it did help us a lot, especially with all the work
> necessary to improve Qubes' user interface, documentation, and outreach to new
> communities.  Indeed, the (estimated) Qubes user base has grown [05]
> significantly over that period. Thank you, OTF!
> 
> But Qubes is more than just a nice UI: it's an entirely new, complex system --
> a system that aims to change the game of endpoint security. Consequently, it
> requires expertise covering a wide spectrum of topics: from understanding
> low-level aspects of hardware and firmware (and how they translate to the
> security of a desktop system), to UI design, documentation writing, and
> community outreach. Even if we consider only the "security research" aspect of
> Qubes, this area alone easily scales beyond the capabilities of a single human
> being.
> 
> In order to continue to deliver on its promise of strong desktop security, 
> Qubes
> must retain and expand its core team, and this requires substantial funding. 
> At
> this point, we believe the only realistic way to achieve this is through
> commercialization, supplemented by community funding.
> 
> 
> Commercialization
> =
> 
> We're taking a different approach to commercialization this time.  Building on
> the success of the recent Qubes 3.2 release, which has been praised by users 
> for
> its stability and overall usability, we will begin offering commercial 
> editions
> (licenses) of Qubes OS to corporate customers. We believe that the maturity of
> Qubes, combined with its powerful new management stack [06], makes it ripe
> for adoption by any corporation with significant security needs.
> 
> Commercial editions of Qubes OS will be customized to meet special corporate
> requirements. For example, two features that might be particularly attractive 
> to
> corporate customers are (1) "locking down" dom0 in order to separate the user
> and administrator roles and (2) integrating our local management stack with a
> corporation's remote management infrastructure. These are both examples of
> features that our developers are capable of implementing now, on Qubes 3.2.
> 
> We plan to partner with one to three corporate clients in order to run a pilot
> program throughout the first half of 2017.  After it has been successfully
> completed, we'll then widen our offer to more corporate customers and,
> ultimately, to small business customers. Our main constraint is the 
> scalability
> required to cover each additional client. Hence, we plan to focus on larger
> customers first.
> 
> Let there be no misunderstanding: Qubes OS will always remain open source. We
> anticipate that the majority of our commercialization efforts will involve the
> creation of custom Salt configurations, and perhaps writing a few additional
> apps and integration code. In the event that any corporate features require
> reworking the core Qubes code, that new code will remain open source.
> 
> We considered many other ways of attempting to commercialize Qubes before
> arriving at this model. One possibility that some of our users have inquired
> about is that we sell dedicated Qubes hardware (i.e. laptops). However, there
> are a number of challenges here, both in terms of making the hardware
> trustworthy enough to merit our "seal of approval", and from a business and
> logistics perspective. For these reasons, we don't plan to pursue this option 
> in
> the immediate future.
> 
> 
> Community funding
> =
> 
> Unfortunately, the financial necessity of shifting our priorities to 
> commercial
> clients will mean that we have less time to work on features that benefit the
> wider, security-minded open source community, which has been our focus for the
> past seven years.  This deeply saddens us. (We all use Qubes on our personal
> computers too!) However, the reality is that ITL can't afford to sustain the
> open source development of Qubes for much longer. We're running out of time.
> 
> In an

Re: [qubes-users] Re: Install on Dell XPS 13 (9350)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Dec 04, 2016 at 08:03:48AM -0800, miaoski wrote:
> I can use my USB WiFi dongle by running NetworkManager on sys-usb VM.
> After WiFi is connected, set the NetVM of sys-firewall to sys-usb.

Yes, this is one way to use USB network adapter (IMO the simplest, if
that's your only network adapter). You may want to enable
network-manager in "services" tab of sys-usb settings.

> I think BCM4350 has some issue with kernel 4.4.14.  dmesg shows,
> [3.558678] brcmfmac :00:00.0: Xen PCI mapped GSI16 to IRQ22
> [3.560707] brcmfmac: brcmf_chip_recognition: SB chip is not supported
> [3.560724] brcmfmac: brcmf_pcie_probe: failed 14e4:43a3

There is 4.8.x kernel in "unstable" repository. You may try it but, as
the name suggests, it's much less tested. To do so, open dom0 terminal
and execute:

sudo qubes-dom0-update --enablerepo=qubes*unstable kernel-qubes-vm

- -- 
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-
Version: GnuPG v2

iQEcBAEBCAAGBQJYRI7oAAoJENuP0xzK19csF4cIAIpY0S3JNh8WXRun4Q6m9Ti2
VpfMirr5iSC05kvDaWwgEek4/k5pz12o9bfZ8exWHwlr2CxZpou4WWr3Sx4cDXWD
Nt4OiUXXiMutaRDBj8kcn69Mt6H4qnTzOrzjXewg2Rx5SV6XUIDZeO33ZqBby2Hz
p6AwQz4Jrsl1TN/RQkAt5LArO2Rtu/W6AvT1py+B8NaOICS1ZVXmQfrFs1YtdDn3
qn6AG+KWrBvb6tLSo5fJOczVWD4f6KL21GmMWNP0ElShVQzs2WBZyWs81Ft/8l/g
C1YyMZflS8JvfuCDSkSSSxvFVm8T969f0rDFrZF70duDWmtcLDf9L7xZB8U8Ops=
=slcC
-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/20161204214718.GT1145%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Dec 04, 2016 at 07:49:13AM -0800, Lorenzo Lamas wrote:
> Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM fails to 
> start serviceVM's(netVM, usbVM, firewallVM). When the boot process finally 
> completes, trying to manually launch the VMs through VM Manager doesn't work 
> either. When I choose to boot without AEM, everything works as expected. 
> Problem remains with the latest Xen 4.6.3-24.
> It is on a HP Elitebook 8460p with IOMMU running Qubes 3.2
> 
> I'm not very familiar with Linux, so if you want logs, please tell me where 
> to find them.

What exactly you get when starting sys-net manually? Also, take a look
at /var/log/libvirt/libxl/libxl-driver.log and
/var/log/xen/console/hypervisor.log for any related messages. For
example you can use `tail -f` while starting sys-net manually, to see
what messages will show up there:

sudo tail -f /var/log/libvirt/libxl/libxl-driver.log
/var/log/xen/console/hypervisor.log

- -- 
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-
Version: GnuPG v2

iQEcBAEBCAAGBQJYRIoyAAoJENuP0xzK19csBTEH/AtfVWEDUUToA/MLt2sLxbmc
wW2fhRsegzJNKNZhBDmXlZw1Oa+B7oFqVL5o1lFrCrvpwXhNatL3GV78XBK2hI/F
sWi6Yi/WkAz68I71dKWX9ixKY1/UZxXhf8Cl6pnFWmFBeyePL/U/vLtFG7mR2qNd
MTP/7jnKsKBJMsuwvX2Maa0EJe+apjetgmSyCybvFw/Sgvozc2NEDKyxJhMn82Ss
Na9MTNbN6CB5RA/5jPpU0ppS0EO3GH4TfN9AGBPWLimdvJkObgJmtCOHweSHn6h2
Dpm+eL78UTqHN7HNrAifi9rufEzz0yeAMXYfXRi1Nj/Oa9QD/IxUYBcY6ewsWAc=
=02Xd
-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/20161204212713.GS1145%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Issue with hdmi

Hi, after returning to Qubes (I waited for 3.2 since my video was having 
issues) - seems to be working fine now.

However, when the machine times out into sleep, and if I've turned off my hdmi 
monitor I can't seem to wake up the video. I can tell Qubes is running, but 
have tried many ways to wake up the hdmi, haven't found a way.

Any suggestions?

Thanks,
Patrick

-- 
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/9f0d2310-4b73-416c-b2d3-3b86fe5d3da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Where is Chrome once installed?

Hi, newbie question.

I am using 3.2 and an HP I7 processor.

I created a Fedora VM. I wanted to run a Chrome browser, so I used Firefox to 
download and save in the Fedora VM file section, where I installed Chrome. Then 
it asks if I want to run it, and I do - no problem. However, I don't see a way 
to actually launch Chrome anywhere (other than when it asks me after 
installing). No trace of Chrome anywhere.

Any help is appreciated.

Thanks,
Patrick

-- 
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/96b80fa8-19f0-4fdf-8b33-b6bc8b115ad5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot start qubes-guid

2016-12-04 Thread ferddej

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Sat, Dec 03, 2016 at 05:22:05PM -, ferd...@sigaint.org wrote:
>> Hi
>> Each time that I create a new appVM based on whonix-ws, the appVM shows
>> a
>> message "Error starting VM: Cannot start qubes-guid!", after 30 seconds
>> the message leaves and all works normally. This doesn't appear with new
>> appVM based on fedora or debian.
>> Is it anything that can be considered normal?
>
> Do applications in such Whonix AppVMs work anyway? How do you start the
> VM - from the menu, or "start" button from Qubes Manager?
> Is it fresh install, or upgraded from previous Qubes release?
>
> Also, take a look at guid log - it's in /var/log/qubes/guid.VMNAME.log
> (replace VMNAME with actual VM name) - also accessible from Qubes
> Manager - right click on the VM).
>
> - --
> 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-
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJYQxXwAAoJENuP0xzK19csdf4H/Aw5RrEHoiKQdqRbIhvCdj0x
> ZI180Lwt3OS31EjzNAePrjuhAEmF3cSaoPxgLK+5FnZ+ah2mN6M+YPolN2Q70JYl
> Kvp8oplQWdN9FQqe4n0oC/BL5gUFoJJjZ/U8LpD9eAfUrq1urODLj/xWW8tZilg4
> G8sG2dU7QpprAWHAbXil4kpsYVrSgyfXjdVLbts7wafBCIgMtnfAPQhzeKm36yZ7
> fSjoLP9ICGjXBaR0QfU8eTLlltAKcx2ewQgszbk46bIgy8vnoeKtFiAbUyc8YwN2
> nbuS0jCR2rII3tbEY2y8rybenka11gmG0DhmDnrNWdUbFo2NGxoDmxAeONl12Uw=
> =jb4m
> -END PGP SIGNATURE-
>
Hi
Application in VM works anyway, this message appears only from the first
start of the appVM created
Start VM from Qubes Manager
I reinstalled whonix-ws

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

Re: [qubes-users] First impressions

On 12/03/2016 04:07 PM, Ray Brainer wrote:

1) No way of desktop sharing, though I need it very much. I read some ideas on
the point here
https://groups.google.com/forum/#!msg/qubes-users/-JEfgOF-TaI/kIU_JCmUCAAJ
It sounds almost impossible. I use Zoom and Viber to share screen. Have no idea
of screen forwarding to a VM.

Maybe HMV can help, not regular AppVM :)

2) Cross-clipboard operations don't work by any means. Cross-usage of
applications, user-generated shortcuts to apps - everything seems a problem.
On Windows I have the same problem :) Copy not work every time.
After I migrate to Q, then it works perfectly

5) Templates are based on pretty specific distros like Fedora and Debian. It
takes time for Arch and Windows templates to create.
First, What I do after migration to Q was setup of Windows HVM. After
playing with Qubes and Windows... I does not start Windows, because I
found all application at Fedora which replace the need to start Windows.
Now, I start it one-two times a week for the specific problems only.

Again, the idea is excellent. If there is a way to save my time on points 1-3 I
would be thankful.

Continue learning the system...

--
Regards

--
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/3743b9d4-b562-ae2e-08a7-97f87b5a91d2%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: First impressions


On 12/03/2016 07:20 PM, raahe...@gmail.com wrote:


In KDE it was much easier to make shortcuts to launch specific apps right in 
the menu.  XFCE unfortunately does not make this easy anymore.  You actually 
have to edit a cfg file to do it, but its possible.


It's not true. It's easy to create shortcuts menu. Right click on 
toolbar, then New Item> then Launcher. After it will be visible you can 
change settings and add shortcuts with right click > properties


--
Regards

--
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/cf549f06-8803-1d98-9801-830398a15fc6%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] 2/3 of VMs randomly lose network access; sys-net, sys-firewall, and others normal


On 12/04/2016 05:19 PM, Marek Marczykowski-Górecki wrote:


More troubleshooting steps:

1. When problem appears, try in sys-firewall:

qubesdb-read /qubes-iptables-error

This should print last error of firewall reload. I guess it may be about
some DNS resolution failure (if any rule use DNS name instead of IP).
This shouldn't affect all the VMs - only the one for which name
resolution failed, but maybe something is wrong here.

2. Check status and logs of qubes-firewall service:

sudo systemctl status qubes-firewall

Should be "active (running)" and a series of "qubes-firewall[xxx]:
/qubes-iptables" messages. If you see anything else, let me know.

3. Restart qubes-firewall service and see whether it helps:

sudo systemctl restart qubes-firewall



Okey, I made offline notes 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/3a0f7e9f-4da6-0dce-a4f8-acdaf0b97ed3%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-04 Thread Chris Laprise


On 12/04/2016 10:49 AM, Lorenzo Lamas wrote:

Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM fails to 
start serviceVM's(netVM, usbVM, firewallVM). When the boot process finally 
completes, trying to manually launch the VMs through VM Manager doesn't work 
either. When I choose to boot without AEM, everything works as expected. 
Problem remains with the latest Xen 4.6.3-24.
It is on a HP Elitebook 8460p with IOMMU running Qubes 3.2

I'm not very familiar with Linux, so if you want logs, please tell me where to 
find them.

In case it may not be related to the new Xen version but some other update 
installed at the same time, here is the update history:



This sounds familiar. Try removing the network devices from sys-net to 
see if it will start then. Next, re-add the network devices and try 
starting sys-net again.


Chris

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/aaf2e564-a506-9e4b-1ee7-e01c77192467%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: How to backup an iPhone under Qubes

2016-12-04 Thread Vít Šesták

What bridge do you need for network? With Qubes, you can use iptables to route
a trafic on a specific port to a specific AppVM.

You need to do this on all VMs that are in the path. Usually, you forward a
port from sys-net to sys-firewall and then from sys-firewall to the AppVM you
need. Would this solve your problem?

Alternatively, you can forward USB to Windows using usbip. Again, you need
iptables rules. I did this in older Qubes version with Linux machines, but it
should work the same with Windows.

Security concerns when using usbip this way:

* You trust the VMs where the network goes through (usually sys-firewall).
* The host VM could be attacked if USBIP is vulnerable.
* The guest VM could be attacked if USBIP is vulnerable. I am not sure how much
is the guest software maintained, since the last release is about 5Y ago.
* Other general threats related to USB (BadUSB, USB sniffing etc.)

Maybe none of those concerns is a thread for you, but you have been warned.

Regards,
Vít Šesták 'v6ak'

--
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/3449f6d1-13c3-4e8c-8c95-e5a642805f20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

2016-12-04 Thread Lorenzo Lamas

It's a bit saddening to hear priorities are shifting to commercial clients, but 
for the rest it's great news, a good way to keep Qubes going!

> In an attempt to keep the open source development of Qubes going, we've teamed
> up with Open Collective [07], which makes it easier to donate to the Qubes
> project.  Now, in addition to our Bitcoin fund [08], we can also accept
> donations via credit card. 
Good to hear, but I would recommend adding more payment options like Paypal so 
it's easier for users in other parts of the world, where credit card is not a 
widely used, to support you.

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

Re: [qubes-users] Re: Install on Dell XPS 13 (9350)

2016-12-04 Thread miaoski

I can use my USB WiFi dongle by running NetworkManager on sys-usb VM.
After WiFi is connected, set the NetVM of sys-firewall to sys-usb.

I think BCM4350 has some issue with kernel 4.4.14.  dmesg shows,
[3.558678] brcmfmac :00:00.0: Xen PCI mapped GSI16 to IRQ22
[3.560707] brcmfmac: brcmf_chip_recognition: SB chip is not supported
[3.560724] brcmfmac: brcmf_pcie_probe: failed 14e4:43a3


Thanks.
miaoski

-- 
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/d766d723-e662-4c7e-a495-0960d18f8138%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Dell_Inc_-XPS_13_9350-20161204-135951.yml
Description: Binary data

[qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-04 Thread Lorenzo Lamas

Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM fails to 
start serviceVM's(netVM, usbVM, firewallVM). When the boot process finally 
completes, trying to manually launch the VMs through VM Manager doesn't work 
either. When I choose to boot without AEM, everything works as expected. 
Problem remains with the latest Xen 4.6.3-24.
It is on a HP Elitebook 8460p with IOMMU running Qubes 3.2

I'm not very familiar with Linux, so if you want logs, please tell me where to 
find them.

In case it may not be related to the new Xen version but some other update 
installed at the same time, here is the update history:

Transaction ID : 13
Begin time : Tue Nov 22 19:56:34 2016
Begin rpmdb: 934:24862fb1256d9f648273fa8d88ac172b1a06d3d9
End time   :19:58:15 2016 (101 seconds)
End rpmdb  : 939:d785b8e09d66f2d440768eaa6b01d1e77e21ac7c
User   :  
Return-Code: Success
Command Line   : 
--exclude=qubes-template-fedora-23,qubes-template-fedora-24,qubes-template-whonix-ws,qubes-template-whonix-gw,qubes-template-debian-8,
 upgrade
Transaction performed with:
Installed dnf-1.1.10-1.fc23.noarch@anaconda/rawhide
Installed rpm-4.13.0-0.rc1.13.fc23.x86_64 @anaconda/rawhide
Packages Altered:
Upgraded glusterfs-3.7.16-1.fc23.x86_64@qubes-dom0-cached
Upgrade3.7.17-1.fc23.x86_64@qubes-dom0-cached
Upgraded glusterfs-api-3.7.16-1.fc23.x86_64@qubes-dom0-cached
Upgrade3.7.17-1.fc23.x86_64@qubes-dom0-cached
Upgraded glusterfs-client-xlators-3.7.16-1.fc23.x86_64 @qubes-dom0-cached
Upgrade   3.7.17-1.fc23.x86_64 @qubes-dom0-cached
Upgraded glusterfs-libs-3.7.16-1.fc23.x86_64   @qubes-dom0-cached
Upgrade 3.7.17-1.fc23.x86_64   @qubes-dom0-cached
Upgraded libraw1394-2.1.0-6.fc23.x86_64@anaconda/rawhide
Upgrade 2.1.2-1.fc23.x86_64@qubes-dom0-cached
Upgraded qubes-core-dom0-3.2.11-1.fc23.x86_64  @qubes-dom0-cached
Upgrade  3.2.12-1.fc23.x86_64  @qubes-dom0-cached
Upgraded qubes-core-dom0-doc-3.2.11-1.noarch   @qubes-dom0-cached
Upgrade  3.2.12-1.noarch   @qubes-dom0-cached
Upgraded qubes-db-3.2.1-1.fc23.x86_64  @anaconda/rawhide
Upgrade   3.2.3-1.fc23.x86_64  @qubes-dom0-cached
Upgraded qubes-db-dom0-3.2.1-1.fc23.x86_64 @anaconda/rawhide
Upgrade3.2.3-1.fc23.x86_64 @qubes-dom0-cached
Upgraded qubes-db-libs-3.2.1-1.fc23.x86_64 @anaconda/rawhide
Upgrade3.2.3-1.fc23.x86_64 @qubes-dom0-cached
Upgraded xfce4-datetime-plugin-0.6.2-6.fc23.x86_64 @anaconda/rawhide
Upgrade0.7.0-1.fc23.x86_64 @qubes-dom0-cached
Upgraded xfce4-diskperf-plugin-2.5.5-2.fc23.x86_64 @anaconda/rawhide
Upgrade2.6.0-1.fc23.x86_64 @qubes-dom0-cached
Upgraded xfce4-fsguard-plugin-1.0.2-2.fc23.x86_64  @anaconda/rawhide
Upgrade   1.1.0-1.fc23.x86_64  @qubes-dom0-cached
Upgraded xfce4-systemload-plugin-1.1.2-3.fc23.x86_64   @anaconda/rawhide
Upgrade  1.2.0-1.fc23.x86_64   @qubes-dom0-cached
Upgraded quota-1:4.02-5.fc23.x86_64@anaconda/rawhide
Upgrade1:4.02-6.fc23.x86_64@qubes-dom0-cached
Upgraded quota-nls-1:4.02-5.fc23.noarch@anaconda/rawhide
Upgrade1:4.02-6.fc23.noarch@qubes-dom0-cached
Upgraded libpng-2:1.6.23-1.fc23.x86_64 @anaconda/rawhide
Upgrade 2:1.6.26-1.fc23.x86_64 @qubes-dom0-cached
Upgraded xen-2001:4.6.1-20.fc23.x86_64 @anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 @qubes-dom0-cached
Upgraded xen-hvm-2001:4.6.1-20.fc23.x86_64 @anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 @qubes-dom0-cached
Upgraded xen-hypervisor-2001:4.6.1-20.fc23.x86_64  @anaconda/rawhide
Upgrade 2001:4.6.3-21.fc23.x86_64  @qubes-dom0-cached
Upgraded xen-libs-2001:4.6.1-20.fc23.x86_64@anaconda/rawhide
Upgrade   2001:4.6.3-21.fc23.x86_64@qubes-dom0-cached
Upgraded xen-licenses-2001:4.6.1-20.fc23.x86_64@anaconda/rawhide
Upgrade   2001:4.6.3-21.fc23.x86_64@qubes-dom0-cached
Upgraded xen-runtime-2001:4.6.1-20.fc23.x86_64 @anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 @qubes-dom0-cached
Scriptlet output:
   1 sed: can't read /etc/sysconfig/prelink: No such file or directory
   2 Redirecting to /bin/systemctl start  xenstored.service
   3

Re: [qubes-users] [Security] Anti-evil-maid didn't notice Xen update ?

2016-12-04 Thread Rusty Bird

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Rusty Bird:
> Does /proc/cmdline in dom0 contain "rd.antievilmaid" at the end? If not:
> 
> In the GRUB boot menu, do you choose the entry "AEM Qubes, with Xen
> hypervisor"? If there is no such entry, you may have to rerun the
> "anti-evil-maid-install" command.

Otherwise, the only thing I can think of would be to try tboot 1.9.4:
https://github.com/QubesOS/qubes-issues/issues/2155#issuecomment-263139022

Rusty
-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYRDHAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfFFUP/3Yv0GYD++Fq0UFaEHEttvBP
u7vxv70SpoMPo5SnxN2PLFJCVvbM4/XO+ALmdW8KtgjFUiJ1xr7dTY81Kcbaj0mj
3zPjve/AiUhTP4ye0KqpJnqxDACJPe6EkMlCAY9xESdtIxcK6P6lKaTHKr0XfBLV
3vddZ3a7SqyWOOE8NUqzjwan8uc+cAQ13+aS2jZa1Rp8AB7/GJ7hRu2thPGtF6y3
Z04w9MWAPuqNUV98mPEAK/oxSE1N8gHQsTA/0vUJMVm5j+84iRbvmJI6VsQOLtUq
2eZgcrq+3qxYv2JU6K33eu6XcVoLVp9sNUduzkik+GCZO9EVL2dwKsXCil4MaXOy
H4KERaMiDvuOUecvLUtPdTH/ZlEYmEqBqamOn4/r3XOZxjHhqF9bLZyJT6+M2pgz
Iz+qzFf/8RDxStEXCcWP/0RE3EutS1p3PpqzavAWNzN9PxRctlFlcUwqZJE66MrN
84eB355zvEQEjiB+1YIAIknDMp/I4NG0kWneyj/NEd5Pk+RBJl4CaQy0MfGNyLKl
MiTEAR/DEDILJgPb4pC/ArlCBEhzn0h7iqITQnxv5YwRr/27A3QC3RQ1BRBjgV0q
80Elskoe16nkd08ZCBC1k5a0BxE9UJd5pculKH05alGjl6U2W+uhq2I+mimhRSF8
vwWQ9nQf67H6H05dcaau
=XbOw
-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/20161204150952.GB1048%40mutt.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [Security] Anti-evil-maid didn't notice Xen update ?

2016-12-04 Thread Swâmi Petaramesh


Hi again,

On 12/04/2016 03:54 PM, Rusty Bird wrote:


Maybe your system still doesn't boot into AEM mode for some reason.

Does /proc/cmdline in dom0 contain "rd.antievilmaid" at the end? If not:

Yes, it does.

In the GRUB boot menu, do you choose the entry "AEM Qubes, with Xen
hypervisor"? If there is no such entry, you may have to rerun the
"anti-evil-maid-install" command.

It also does.

I also get correctly prompted for the TPM key, AND I can also see my 
secret image displayed while I am prompted for the HD password.


So I for sure boot in AEM mode, and it "looks like" it's working, but if 
I upgrade the kernel (there was a kernel upgrade today), AEM doesn't 
notice and still happily displays my secret image :-(


Thanks again for your help.

Kind regards.

--
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/59eddd93-d1b7-9542-5497-7e88e1f3d4fe%40petaramesh.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [Security] Anti-evil-maid didn't notice Xen update ?

2016-12-04 Thread Rusty Bird

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Swâmi Petaramesh:
> I now have downloaded 3rd_gen_i5_i7_SINIT_67.BIN from Intel, installed
> it per instructions, completely redone everything (including resetting
> the TPM chip in BIOS, uninstalling and reinstallind the AEM RPM...
> 
> But still, lines 17-19 remain all FF :-(

Maybe your system still doesn't boot into AEM mode for some reason.

Does /proc/cmdline in dom0 contain "rd.antievilmaid" at the end? If not:

In the GRUB boot menu, do you choose the entry "AEM Qubes, with Xen
hypervisor"? If there is no such entry, you may have to rerun the
"anti-evil-maid-install" command.

Rusty
-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYRC4zXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfFM8P/Ayi5lu5Vj/mn8IyAJTjj9QC
o5GKkjKRH+3uF0p6INj7imFUH6B7lU0GAs5b//E/9lImvYZ6BhLgCU1MNElvohWO
uvJ1imhUBDziRsyzcCxFuzaMDwcdzVJ/u+JgKwkkn4v81rTriulr547kfHxan0Vt
dZYX6cdr8psJfuWpfFhUGgWBMMYHbw9rTFsBMglNdA/Qpknv0qFQt3ss8oaWjlA5
VU0yZYKCp0oVgrSZA2SUoo7QA6mCZ18lQFTQFEel+Kj81uZLi74rgn98ZGRtCEsy
DlBi3QsIk1pXJiwRmzBrN/FOCDdcYmqz3GOHyP1jPII5f/YHpaS2VsxyEq4LnctV
VTPMvKxs/yNfIDs4QaBMVJIs36ns/mZPvYjrJ/Br6L0lsRDPpEvNtYoz6Nveg3ea
gYsMm2Jhj5O8XlynAm1KKV+uLI/uIawgNzFvjLoIWPRQTpcTQDjmll8T0mBHKPcG
CVYiirNvHLeBhQF32CFLNXQQmvNYs377f8k/m1x8rtuv+af5EVFdoE0eY/HaF9uj
5+PFE4ruBpgB5rocl3pY35NHjn6W2ciOBYXjjvfE06WiB+0ALHz4m+XcJ0j9m7Xy
qrtVH1BGcr/tz15VOOGJc9ZfEqK5W8mQMLXNQfSmA89adEfjSwR8r8ecRCUfeJwg
RL3FpCGFtnu8RLFz/ha+
=ldBa
-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/20161204145444.GA1048%40mutt.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] 2/3 of VMs randomly lose network access; sys-net, sys-firewall, and others normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Nov 30, 2016 at 09:19:06PM +0300, Eva Star wrote:
> On 11/27/2016 02:04 AM, Marek Marczykowski-Górecki wrote:
> 
> > Do you see some correlation with:
> >  - starting/stopping another VM?
> >  - affected VMs have or not firewall rules?
> > 
> > Also, check if restarting qubes-firewall service in sys-firewall helps
> > (and check it status first).
> > 
> 
> Seems I have the same issue! (Maybe) I think it's correlate with CHECKING
> UPDATES on dom0 or templates. When Qubes do that check - other VM still not
> responsive. I wrote about this at the Xen 4.6.3 thread.

More troubleshooting steps:

1. When problem appears, try in sys-firewall:

qubesdb-read /qubes-iptables-error

This should print last error of firewall reload. I guess it may be about
some DNS resolution failure (if any rule use DNS name instead of IP).
This shouldn't affect all the VMs - only the one for which name
resolution failed, but maybe something is wrong here.

2. Check status and logs of qubes-firewall service:

sudo systemctl status qubes-firewall

Should be "active (running)" and a series of "qubes-firewall[xxx]:
/qubes-iptables" messages. If you see anything else, let me know.

3. Restart qubes-firewall service and see whether it helps:

sudo systemctl restart qubes-firewall

- -- 
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-
Version: GnuPG v2

iQEcBAEBCAAGBQJYRCXvAAoJENuP0xzK19cshjgH/iMyhpSkETZP6FyNKTuhlQaZ
T04mPxIpGtkVYnDythtCkhqmJXg+mrtJPOF8SUuVTh4cMC6SyFfkTdkjCjj+yBPo
elMvBV6OX5H261Jds2tmmBJ3OGQDWrLexp/q5aP/y6qehG/9Bc7rAo2Aj8YjeV0T
i5EwAG6b+YHfKfWDPR4HWSpfaBIHHfrvPABgVmWAcg8Onj5sKFGYEe5pYFMMe8k0
zjzEuZiUNZrQwygnaZHFI26vGpc8WMnavXDXXeMzo1yndhZKs9fcyptYvvu2dNSQ
kvm6akyArHpmv3bYetfx/cTKNLGClSG/XW5cQXPheHCZH0RHWtEUm0lQxeP8uhc=
=PQ/6
-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/20161204141926.GR1145%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Install on Dell XPS 13 (9350)

2016-12-04 Thread miaoski

Hi Marc,

2016年12月4日日曜日 17時04分38秒 UTC+8 Marc de Bruin:
> How different is a 9350 from a 9550? I had no problems using the internal 
> Wifi, e.g.
> 
> lspci? Just to compare?

9350 (2016) is a Skylake with Broadcom 4352.
I'm not sure about XPS 15 9550, but XPS 13 9350 is very similar to XPS 13 9343 
(the Ubuntu developer's version).

lspci shows,
3a:00.0 Network controller: Broadcom Corporation BCM4350 802.11ac Wireless 
Network Adapter [14e4:43a3] (rev 08)

In my previous installation of Ubuntu, I had to install kernel 4.4 or 4.5 to 
use it.

Any possibility to use an external WiFi dongle?

-- 
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/1d70c94e-29a9-4f9a-96c5-3028836614b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Win7 as USB-VM: "No PCI-Reset available" libvirt-Problem

2016-12-04 Thread 'tbffoNewGeneration' via qubes-users

Am Samstag, 3. Dezember 2016 19:07:20 UTC+1 schrieb tbffoNewGeneration:
> Am Samstag, 3. Dezember 2016 18:11:33 UTC+1 schrieb Grzesiek Chodzicki:
> > W dniu sobota, 3 grudnia 2016 17:47:25 UTC+1 użytkownik 
> > game...@googlemail.com napisał:
> > > Am Samstag, 3. Dezember 2016 16:30:40 UTC+1 schrieb Grzesiek Chodzicki:
> > > > W dniu sobota, 3 grudnia 2016 15:35:21 UTC+1 użytkownik 
> > > > game...@googlemail.com napisał:
> > > > > Am Samstag, 3. Dezember 2016 12:54:04 UTC+1 schrieb Grzesiek 
> > > > > Chodzicki:
> > > > > > W dniu sobota, 3 grudnia 2016 12:05:52 UTC+1 użytkownik 
> > > > > > game...@googlemail.com napisał:
> > > > > > > Hi,
> > > > > > > for comfortable use of USB-only scanners and other devices such 
> > > > > > > as this, it would be nice to have Win7 as USB-VM, e.g. have the 
> > > > > > > USB-Controller-PCI-Device assigned to it to use USB-Devices from 
> > > > > > > there. 
> > > > > > > 
> > > > > > > When i try to start Win7, this happens (see the picture 
> > > > > > > https://imgur.com/a/spnRC).
> > > > > > > [The german sentence in the picure is like:
> > > > > > > "libvirt.libvirtError: Internal Bug/Fail: PCI-Device can't be 
> > > > > > > reseted. No FLR, PM or Bus Reset available."]
> > > > > > > I already have the PCI-Device assigned to it, original 
> > > > > > > Qubes-USB-VM dont have it assigned anymore. 
> > > > > > > the "strict pcireset"-qvm-prefs option is already turned on. Any 
> > > > > > > suggestions to fix this?
> > > > > > > Thank you.
> > > > > > 
> > > > > > set pci_strictreset to false and try again.
> > > > > 
> > > > > Wow...yeah, thank you. That was a pointless fail by me.
> > > > > 
> > > > > Anyway: Now, i have the problem that connected usb-devices dont show 
> > > > > in windows7. At first boot after pci-passthough-change, win7 showed 
> > > > > that it couldnt find any driver for the "new" usb-controller. I tried 
> > > > > to fix it with Xen PV Bus-Driver, but it didnt work.
> > > > 
> > > > Check if You have VT-d enabled in BIOS/UEFI
> > > 
> > > Yes, it is. 
> > > But i installed Qubes with vt-d disabled und reenabled it like it is 
> > > mentioned here: https://www.qubes-os.org/doc/thinkpad-troubleshooting/
> > 
> > Can you paste the output of xl dmesg | grep -i vt-d ?
> 
> xl dmesg:
>  Xen 4.6.3-24.fc23
> (XEN) Xen version 4.6.3 (user@) (gcc (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6)) 
> debug=n Wed Nov 23 00:15:57 UTC 2016
> (XEN) Latest ChangeSet: 
> (XEN) Bootloader: GRUB 2.02~beta2
> (XEN) Command line: placeholder console=none dom0_mem=min:1024M 
> dom0_mem=max:4096M iommu=no-igfx
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
> (XEN) Disc information:
> (XEN)  Found 1 MBR signatures
> (XEN)  Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)   - 0009d000 (usable)
> (XEN)  0009d000 - 000a (reserved)
> (XEN)  000e - 0010 (reserved)
> (XEN)  0010 - 99bb9000 (usable)
> (XEN)  99bb9000 - aca89000 (reserved)
> (XEN)  aca89000 - aca8a000 (ACPI NVS)
> (XEN)  aca8a000 - b7f7f000 (reserved)
> (XEN)  b7f7f000 - b7fcf000 (ACPI NVS)
> (XEN)  b7fcf000 - b7fff000 (ACPI data)
> (XEN)  b7fff000 - b810 (reserved)
> (XEN)  b860 - bc80 (reserved)
> (XEN)  f800 - fc00 (reserved)
> (XEN)  fd00 - fe80 (reserved)
> (XEN)  fec0 - fec01000 (reserved)
> (XEN)  fed0 - fed01000 (reserved)
> (XEN)  fed1 - fed1a000 (reserved)
> (XEN)  fed84000 - fed85000 (reserved)
> (XEN)  fee0 - fee01000 (reserved)
> (XEN)  ff80 - 0001 (reserved)
> (XEN)  0001 - 00024280 (usable)
> (XEN) ACPI: RSDP 000F0120, 0024 (r2 LENOVO)
> (XEN) ACPI: XSDT B7FD0188, 00D4 (r1 LENOVO TP-N1C  0 PTEC2)
> (XEN) ACPI: FACP B7FF4000, 00F4 (r5 LENOVO TP-N1C   1150 PTEC2)
> (XEN) ACPI: DSDT B7FDD000, 12331 (r2 LENOVO TP-N1C   1150 INTL 20141107)
> (XEN) ACPI: FACS B7FAA000, 0040
> (XEN) ACPI: TCPA B7FFC000, 0032 (r2 LENOVO TP-N1C  2 PTEC2)
> (XEN) ACPI: SSDT B7FFB000, 03A2 (r2 LENOVO TcgTable 1000 INTL 20141107)
> (XEN) ACPI: UEFI B7FC1000, 0042 (r1 LENOVO TP-N1C   1150 PTEC2)
> (XEN) ACPI: SSDT B7FF6000, 4E0A (r2 LENOVO  SaSsdt  3000 INTL 20141107)
> (XEN) ACPI: SSDT B7FF5000, 05C5 (r2 LENOVO PerfTune 1000 INTL 20141107)
> (XEN) ACPI: ECDT B7FF3000, 0052 (r1 LENOVO TP-N1C   1150 PTEC2)
> (XEN) ACPI: HPET B7FF2000, 0038 (r1 LENOVO TP-N1C   1150 PTEC2)
> (XEN) ACPI: APIC B7FF1000, 00BC (r3 LENOVO TP-N1C   1150 PTEC2)
> (XEN) ACPI: MCFG B7FF, 003C (r1 LENOVO TP-N1C   1150 PTEC2)
> (XEN) ACPI: SSDT

Re: [qubes-users] [Security] Anti-evil-maid didn't notice Xen update ?

2016-12-04 Thread Swâmi Petaramesh

Hi Rusty, Hi all,

Le 01/12/2016 à 20:23, Rusty Bird a écrit :
>> Uh... Lines 17-19 are all FF

> Well, the good news is we've definitely narrowed down the problem. :)
> 
> Are you sure you've successfully copied the *right* SINIT blob for your
> system to /boot? (Intel's download page is... not great.)

Stupid me. I had first thought that if I could see the PCR-* lines and
initialize TPM, it meant that my kernel managed the TPM by itself and
didn't need this file... So I had't installed it at all.

I now have downloaded 3rd_gen_i5_i7_SINIT_67.BIN from Intel, installed
it per instructions, completely redone everything (including resetting
the TPM chip in BIOS, uninstalling and reinstallind the AEM RPM...

But still, lines 17-19 remain all FF :-(

> Does "ls /boot/*SINIT*.BIN" - note the uppercase for both the name and
> the extension) show exactly one file?

Yes, it does.

Thanks again for your help.

ॐ

-- 
Swâmi Petaramesh  PGP 9076E32E

-- 
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/11d0133b-c51e-a5cf-36fb-4f7ebee54c30%40petaramesh.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: [qubes-devel] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-04 02:27, Zbigniew Łukasiak wrote:
> On Sun, Dec 4, 2016 at 3:41 AM, Andrew David Wong  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> On 2016-12-04 00:08, Zbigniew Łukasiak wrote:
>>> On Friday, December 2, 2016 at 6:13:35 PM UTC-5, Andrew David Wong wrote:
> So that's what I'm thinking, maybe it would be good for the 
> "evangelization" of Qubes to make some very simple, brief, and 
> to-the-point videos and howto's?
>

 Yes, certainly. Would you be willing to help us with that? :)
>>>
>>> I am new to Qubes - just installed it on my computer. I can note the 
>>> problems that I encounter. Where to send this?
>>>
>>> Z.
>>>
>>
>> Please take a look at this page:
>>
>> https://www.qubes-os.org/doc/reporting-bugs/
>>
> 
> Well - this is not about bugs but about surprises. From my experiences
> with other OS projects I learned that people quickly forget what was
> difficult at the beginning. It is seasoned developers who make
> documentation who have already internalized many details - so the docs
> often lack information.  It is useful to include the newbies in
> writing the docs. - surely they cannot write the answers - but they
> can note the questions :) And they can also mark the areas of
> difficulties. This is the kind of feedback that I had in mind.
> 
> Cheers,
> Zbigniew
> 

I understand. Please feel free to help us by contributing to the
documentation by following these guidelines:

https://www.qubes-os.org/doc/doc-guidelines/


P.S. - Please keep the mailing list CCed, unless there's a need for
privacy:

https://www.qubes-os.org/mailing-lists/#specific-rules-and-notes

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

iQIcBAEBCgAGBQJYQ/QBAAoJENtN07w5UDAwrFkP/joAsy9FmBT+Ik/PHak1gV7Y
NbvbSoTxrc2AABqIHZzY1FvwJ24qn70N/klIYBN9NlkjZH3jGyt1+z+hBOqMzAnG
CpPC+z1xetyH5fwVgGqL4bffzcW6M9hfcN7oImTeyI7L3vGdhs57aCMVc0a8BOsN
xiDFYTGyiROjkfpu4+12pzQVaB2IT2vRHAnUQOO8yw3aFKAtcY0+uVp11zinLtsq
KPIehVlouXgpAHcopq2YpzQc7qBr06WUe31modMF+PKGXGDA0MNaQxTRi5M26BX5
IbVMHC1o4J7/6bqYZEmrljpX8GHk7hMeodiLWhzs7j9KtA1TMVSCwgFOGNXbNffh
C2olBHvvgyEYxRxS9RslNEZa7wiXgliPZjwMhNpfOmj773J7t31irwqlrGMnK5c0
0DChEWsTPQdZfqy0x+QAEr5K7Fwj8pdxzAR0HeplYXusyitUNFVC/3bmliZv0mmI
yFSyW7rfQDySDJuxAu0rPGTX62mqplr2HGdsfwoy9V3KF42ZQs4V2rMuWLMkuzAZ
PiezOPf4klJnL/0uokCV0nHoFrPMcn3a8ocnOo4OHEZ2+OGKMW6ZQND+XQ0NNa1p
MWOQOTaXG8KVglkwAQsktj/P5H2siZBs9z77/br/LtGKbdQfqultEGQZDK2EPVSQ
fwDrViAzt0IpmPeDpumt
=JKJ2
-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/b58ce4d3-d69c-f987-6969-ddcf1348fb95%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Install on Dell XPS 13 (9350)

2016-12-04 Thread Marc de Bruin

Op 4 dec. 2016, om 07:20 heeft miaoski  het volgende 
geschreven:
> 
> I failed to assign my TP-LINK TL-WN722N wireless USB dongle to sys-net.  
> Google'd a bit and found some docs, still no idea on how to do it.  Help is 
> much appreciated.
> 

How different is a 9350 from a 9550? I had no problems using the internal Wifi, 
e.g.

lspci? Just to compare?

Greetz,
Marc.


-- 
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/9A8E77A8-CD60-451A-AF17-4492DC07982C%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: [qubes-devel] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-04 00:08, Zbigniew Łukasiak wrote:
> On Friday, December 2, 2016 at 6:13:35 PM UTC-5, Andrew David Wong wrote:
>>> So that's what I'm thinking, maybe it would be good for the 
>>> "evangelization" of Qubes to make some very simple, brief, and to-the-point 
>>> videos and howto's?
>>>
>>
>> Yes, certainly. Would you be willing to help us with that? :)
> 
> I am new to Qubes - just installed it on my computer. I can note the problems 
> that I encounter. Where to send this?
> 
> Z.
> 

Please take a look at this page:

https://www.qubes-os.org/doc/reporting-bugs/

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

iQIcBAEBCgAGBQJYQ9bQAAoJENtN07w5UDAwsxcQAIm/HcgRTL78y6xXxVry8uC0
pLN5qR++46uuGQ+5pIT9puuiSZ0ik9pXx0kuCbVPJAWDnD63hfP7l2so74eifaLp
7Z0ZFq/6iR20+s9Cw8zqhkwhtS0eLIZMt+xcLzcWJ77Dk+4OT8j3wYfWxROXZ99y
sLsyp3EQJYC1XOpEeP+r9DnELvwGkhPMEjlQpLh1zQ27JuLhrziYdiNCAYKNYxVb
jx2Vsa2BAThXY6J0wIeQdB2sqb3018uB2g69MEyxMdaRhVz1FiMbWXmuFDOBCV7q
FJlZsB/+6xVeZKtzqOGJ+Z8zwhENunPsosEuYTJvMwvGNDlAhCqJvbDtniCyLn6c
kbWE2KPFOK+WJZ47wq2IU1a7w732MKSouv5IorY0Be3yaa+XQBvezkgs78hooKIe
InPQGV5yyAyhIsOpH1g0H8I3ULsRMqXzW8FKZdpgCRwNt4b79hHzJ7i1rj39tZoZ
YHfIHjuaExgLLHza1n/9tGh4u64i01G+u3Owf7pu/u3fTCeHUFgvzhixW4ce7MaD
ZXSy1p5lJePdjWxMmhGYeu+brtM7UxO5eIrDzfmxBlBMImc7kByZKrV7owQQpYW0
7JNsWuC4i8KmhBunR6fJzm9tdzFKkpcEEH6WMflAtOF4ovsdioTO0dCDhrfr6J+R
QP2R/A6LHWwM1Igf+cXr
=gSbS
-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/034a1390-e09e-dee4-c590-41eec48f7efc%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: [qubes-devel] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-03 06:14, Kopimi Security wrote:
> On Saturday, December 3, 2016 at 12:13:35 AM UTC+1, Andrew David Wong wrote:
>> On 12/02/16 11:17, Kopimi Security wrote:
>>> I'm excited about this, and wish to support Qubes.
>>> My first thoughts are "How can Qubes reach a broader community", and "Can 
>>> the HOWTO's be made more approachable?".
>>> For example, the section 'assigning-devices' on the /doc/, didn't get into 
>>> how to actually use a mouse with a sys-usb qube, before at the very end.
>>> And there, the way it was written gave the impression of giving the answer 
>>> almost as an afterthought, as if it should have been obvious to everybody.
>>> As such, it reads as it was written by somebody "too close to the problem".
>>> Somebody being so familiar with the system that outsiders' inability to 
>>> grasp the "obvious", escapes him. Or her.
>>> This is not a unique issue for ITL though, the same problem pops up 
>>> everywhere when highly technical minded people try to convey something to 
>>> people who just wants to be *users*!
>>>
>>> So that's what I'm thinking, maybe it would be good for the 
>>> "evangelization" of Qubes to make some very simple, brief, and to-the-point 
>>> videos and howto's?
>>>
>>
>> Yes, certainly. Would you be willing to help us with that? :)
>>
> 
> Absolutely!
> Would it be okay if I started with some of the /doc/-articles?
> I've noticed that some of them could benefit from an update, as an example 
> the one on Kali (https://www.qubes-os.org/doc/pentesting/kali/).
> 
> Please let me know if this is something that I could help out with.
> 

Yes. Please take a look here:

https://www.qubes-os.org/doc/doc-guidelines/

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

iQIcBAEBCgAGBQJYQ9XZAAoJENtN07w5UDAwATEP/263uVXxXi7NxUjPJHpgExfN
L+FFMkt9IcDDwJCmaBVxqOuZOAKYq4EzgFOt6n4QXObJVUgfu1i8WmmMVpBRhQ9q
swVfjTKQH7hsICT5xRriLD8erDm0NzEB2lRnv0kvhJVlFHWHiv5/UrZ6S2+v3GmV
wTjfTtaptgyJ5HMEK6Wh2OjYktKSNEf9EAU6CEKHtR7JLawRIvYBERPOdHeUS4Sh
FOsOSy2ke1jITX39YXLzx3Yv8pd/56KDUjArjqmtUWsndt9YJvLjU6aSu2z+FhiZ
aubpamsTsUtd9znbt/YSQcK+hyVQjk15QQtEqCTU04A3mhKKkYQKDM6YZBxxF7EO
2XRSxB29fKD8OqZiHwHgF8KC8EPxZwkfWYiR6CwPCoaT3u/KYyWjPdWBUcEcF94q
l8fzBPCbC/jAm7/tBUTSiHjB6xroElW6GHTr/fsL8Zee+15gfB12kiL+dtsFvpFA
FYxV0Or7f4HKXrGoOQOBqxOHWJXDptw+iMyClpDRhuhSu38krieLQbt0nK9xhdny
AnXLzLP149+jTzKKjfvLg9JEwtZfKErrPFqez+BTKuSubzDofRi5sUquRJUbFeAi
QbbTSCeLm1oQnq8/Eb/Z+C9tj+3ruyuFISIAIrLUulCbsSkynVoo5KwfBxNQ/ukF
vGxZRIhSWUO0837609OI
=FFM1
-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/54e6-5b9a-e482-264a-23ee3b783c79%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-03 05:07, Grzesiek Chodzicki wrote:
> This is a wonderful idea, there are about 20k Qubes users out there, if we al 
> give you guys an equivalent of Windows license price you should be set for a 
> millenium. I'd also love to see some Qubes merchandise available to buy so I 
> can up my swag game while simultaneously contributing funds.
> 

Thanks! The merchandise ideas has been discussed internally, but we've decided 
not to pursue that option at this time.

> Also, you forgot to post this to qubes-announce Andrew.
> 

Didn't forget; qubes-announce is strictly for QSBs and new releases:

https://www.qubes-os.org/mailing-lists/#qubes-announce

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

iQIcBAEBCgAGBQJYQ9WhAAoJENtN07w5UDAw9pEQAKdkd/X7l9SwDJHHaWhVHDFp
CSe0lFuLCbnjQiPH34ygV7oRGAoi5Tmqg/AEnxczpmy9hNZ/TYYHx85h1nwa3T7Z
hhE+8jJgPHsvtpBV37GZwSl/IG0YyUInQ0yaEwCSKFDNGSkb5kn/mWdF3745QgNe
tIn5cyHF5skswcFwxh+6TJFnIN9sAiHbDvqHNbNb5lyFShxyBklt55hmybzZ+2Y8
qopYmMR4MYYRBuzeKx4PPqfBF4+uEHEA9jQzpQBxclpSY4MPGOvgt0gBs+OPBWLG
VGdgcL2yzZIz5667YEO1NVu3FIlKH0B7128tcYEBV5wGTi0KNud7T7kVNSP5Qbvz
BTbaYpri8U/I+i1djHb9aHXkGzMn7oXznwOgCfFJ31YQivjym/E3c/j7ChRqNg0d
FcEQ3Qljz/Qn7LgO94Oj074sFTgBcjKb7pudfByMw1LJrdskCsdiDAGk2u30bLXP
/0l9QRC046NfEjEhVFHZqBpEqEoPiXMDizIy6antlyZx5BrlnIOv1iqETV4gUxaa
WKZx1GTWFZISsGqhPIjGtiO+WLDvhC0QoAzU0dBgxM+4/W3WmP64V1bv4PB5Achf
eYX46kT8SDMLJSVGlD7GQJYpVdbdAUZJfL1TgVTu1+l2xqWRV9F7pzRs5XopmQOX
X33rxAH+Bhc4yM7i41Uv
=GeRw
-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/03cdbcdc-a275-0992-570a-21fc2efeec02%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Asus Transformer 3 Pro T303UA, Thunderbolt issues

2016-12-04 Thread Benjamin Richter

Am Sonntag, 4. Dezember 2016 01:33:31 UTC+1 schrieb Marek Marczykowski-Górecki:

> > I've attached the ethernet dongle to the same port as the logitech 
> > keyboard, but it does not show up anywhere.
> 
> If you see the device in dom0 in some configuration, take a look at its
> sysfs path - it will have a hint on which controller is it. Like this:
> lrwxrwxrwx 1 root root 0 Dec  4 01:32 /sys/bus/usb/devices/3-1 ->
> ../../../devices/pci-0/pci:00/:00:02.0/usb3/3-1
> 
> - -- 
> 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-
> Version: GnuPG v2
> 
> iQEcBAEBCAAGBQJYQ2RWAAoJENuP0xzK19csKxMH/3rkY6pxlWVSjltPRc1r2jGn
> njWyqDEA6Zoe56gAQ3zS1ORX54hgpEw6omZgzB3bY9KI2U3ihLncJ4jF8mVwxa+S
> rTCFF1Flqp8Olk2jTXc2lobdLcOQBMQXXfNq4GbpHkl0C+ZVIa1n7lndfJI9WA21
> TKA3gsW/SY8EgBjYtFO0Emnhr5WMi3jYyt/qSWU8jrYn92IoZnx6CbpQp8xA/S8L
> KLvt7WUnBjuFX+k4z9hodXHq6eU00YNqOEI4fm0+y92PPSjIGKbDhClCstSMMXRE
> RqlbJmWpBasYBPm2pOg+1C0Vkeg593TtxahLd2k8MuFZUjrCjY4OXwA7+YkHFRA=
> =4hF8
> -END PGP SIGNATURE-

That's really quite clear, here's a lsusb output from dom0 with both usb 
controllers. Here the ASIX and Realtek ethernet deivces show up on bus 004.

Bus 004 Device 004: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 004 Device 005: ID 0bda:8153 Realtek Semiconductor Corp. 
Bus 004 Device 003: ID 05e3:0620 Genesys Logic, Inc. 
Bus 004 Device 002: ID 05e3:0620 Genesys Logic, Inc. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 046d:c51e Logitech, Inc. 
Bus 003 Device 007: ID 1e4e:0898 Cubeternet 
Bus 003 Device 006: ID 0572:1703 Conexant Systems (Rockwell), Inc. 
Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0b05:1838 ASUSTek Computer, Inc. 
Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
Bus 001 Device 002: ID 04f2:b5b1 Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb of dom0 after attaching the controller to sys-net:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0b05:1838 ASUSTek Computer, Inc. 
Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
Bus 001 Device 002: ID 04f2:b5b1 Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and of sys-net:
sudo lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 046d:c51e Logitech, Inc. 
Bus 002 Device 006: ID 1e4e:0898 Cubeternet 
Bus 002 Device 005: ID 0572:1703 Conexant Systems (Rockwell), Inc. 
Bus 002 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The Logitech keyboard attached to the docking station is there, but neither the 
asix dongle nor the docks ethernet port show up. It seems dom0s usb bus 004 got 
lost somewhere.
Interestingly, if I switch the ethernet dongle and the logitech keyboard, the 
keyboard shows up on another port, but the dongle does not show up.

I have no idea what's going on.

-- 
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/04d151c7-a36b-4a61-8278-5cafabf141b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] First impressions

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-03 05:07, Ray Brainer wrote:
> This is my first week of usage and impressions about the Qubes.
> The idea of isolation seemed wonderful before using it.
> Now I find very unhandy what I deal with in Qubes.
> 
> 1) No way of desktop sharing, though I need it very much. I read some ideas 
> on the point here  
> https://groups.google.com/forum/#!msg/qubes-users/-JEfgOF-TaI/kIU_JCmUCAAJ
> It sounds almost impossible. I use Zoom and Viber to share screen. Have no 
> idea of screen forwarding to a VM.

It should be easier to share a domU's screen, but sharing dom0's screen is, at 
least to some extent, inherently insecure.

> 2) Cross-clipboard operations don't work by any means. Cross-usage of 
> applications, user-generated shortcuts to apps - everything seems a problem.

Are you following the instructions here?

https://www.qubes-os.org/doc/copy-paste/

> 3) Appear empty windows I've never seen before in usual apps like Skype, 
> qbittorrent, VLC etc.

This might be a hardware incompatibility issue. I haven't experienced this, and 
I don't recall any other reports of this.

> 4) No free space for software and libraries. There is a huge risk of loosing 
> data when resizing images. I lost it twice, though I repeated every step from 
> the guide.

Can you provide more detail or context about what happened and what you're 
trying to achieve? The problem you're describing sounds like something that 
shouldn't be happening as a consequence of normal usage.

> 5) Templates are based on pretty specific distros like Fedora and Debian. It 
> takes time for Arch and Windows templates to create.

We welcome help in streamlining the process.

> 6) It is not very easy to direct webcam on a particular VM.

I suppose difficulty is relative, but it should be easier now with USB 
passthrough:

https://www.qubes-os.org/doc/usb/#attaching-a-single-usb-device-to-a-qube-usb-passthrough

> Again, the idea is excellent. If there is a way to save my time on points 1-3 
> I would be thankful.

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

iQIcBAEBCgAGBQJYQ9DzAAoJENtN07w5UDAwJHMP/it/vJ2tq3tCgq9esXaSwS1h
us+ppF9iWRKQBK0zMDjgjAZKKvxZyIyPfkm5wqrb6JEiXckhyPspI7ZhP1E+rijK
K9HzJHeSx8OJ4B4YwHhXjHAP+IiCoiE15I8fJTlmoMFX88vptuncPzHFxeD0uwoX
s2HX+kdKUvaXrooVqCNRxCq9ezWR8fa/Ex56c27k7joa3lLa8mL34MXo+hIHAMaY
LNZitXu2XKViQfh72bBgGMsQbI1l2Sifa46L9728+ajo8hOgT3uSKoLQK3P1W4UG
VGXSy8i9oNkRICZs/EPYv8xe7oQP6j/EtniWMWWU4OXZQarBthE3m725zksjpGfM
o66aaPA8GIN098vf53HPvr2Guq5G6xEQ+OdJSSyaJrKMz7CcmcdD9J4x0JzY8CO7
DaErCfP7tIThIx2ekVMVmFn/lcwFNQZUm+y8xTyrJeBk7UVLKUu0WiYXL6wYe4c5
k0cO9lbiW5cQ14QKQpD9adzjQrEeW/ZFuBhWNFIAOzalOKTsTpfLDBvhQaYuSoyf
xhc6y0jlRmja4NScfl49tzo5SekqtHK+DA+wO2fl9tMmmelWKi4RGygFXmnWlB6Z
2ci6flFM3qIGMwF7QDTrzZ153fyS1Rg9mrggu4ikqNIoZ2MjnfkEkcV09RdI+D/4
6lMf4Cxdgus84MQDjher
=m2cf
-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/d60cef24-8418-6b0d-cbf6-067d6af5b0f3%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

2016-12-04 Thread Zbigniew Łukasiak

On Friday, December 2, 2016 at 6:13:35 PM UTC-5, Andrew David Wong wrote:
> > So that's what I'm thinking, maybe it would be good for the 
> > "evangelization" of Qubes to make some very simple, brief, and to-the-point 
> > videos and howto's?
> > 
> 
> Yes, certainly. Would you be willing to help us with that? :)

I am new to Qubes - just installed it on my computer. I can note the problems 
that I encounter. Where to send this?

Z.

-- 
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/5efd008f-27de-4d6c-9c57-919664342fa1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-block man page inconsistency