Re: [qubes-users] Updates, security

2017-01-18 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-01-18 18:00, haxy wrote:
> On 2017-01-16 13:22, haxy wrote:
 On 2017-01-14 20:04, haxy wrote: Qubes onion repos have just
 been implemented. Minimal documentation available here:
 
 https://www.qubes-os.org/doc/hidden-service-repos/
 
> 
> 
 First of all, thanks for making the onion repos available!
 
 Following directions to onionize repositories I made a 
 mistake inputting the onion address.  Re-running the 
 commands, dom0 example, "sudo sed -i 
 's/yum.qubes-os.org/qubes-yum.kk63ava6.onion/' 
 /etc/yum.repos.d/qubes-dom0.repo && cat 
 /etc/yum.repos.d/qubes-dom0.repo" has no effect.  Cat still 
 shows the input made with the incorrect onion repo.  Tried 
 using "sudo sed -i 
 's/yum.qubes-os.org/yum.qubesos4z6n4.onion/' 
 /etc/yum.repos.d/qubes-dom0.repo && cat 
 /etc/yum.repos.d/qubes-dom0.repo" with the same results.'
 
 (Noticed the command from the whonix wiki differs slightly 
 from the qubes wiki command. "qubes-yum" vice "yum" before 
 the onion address.)
 
 Was able to get the debian and fedora repos functioning by 
 manually inputting the correct onion address in their 
 respective files but am unable to do that in Dom0. How can I 
 correct this issue in Dom0?
 
> 
> You can do it the same way in dom0: by manually editing the file.
> 
> For example:
> 
> $ sudo vim /etc/yum.repos.d/qubes-dom0.repo (Edit the file, save, 
> and close.)
> 
>> 
>> 
> Thanks Andrew.  Using vim worked. :)
> 
> Do you know why re-running the command, "sudo sed -i 
> 's/yum.qubes-os.org/yum.qubesos4z6n4.onion/' 
> /etc/yum.repos.d/qubes-dom0.repo && cat 
> /etc/yum.repos.d/qubes-dom0.repo" did not work to overwrite the 
> first incorrect address entry?  Curious if it's reproducible or 
> something on my end only?
> 

It's possible that 'yum.qubes-os.org' was no longer present in the
text and therefore couldn't be found in order to be replaced.

> Also, a couple of other questions.
> 
> 1. Seems there are 2 distinct onion addresses that can be used for 
> the qubes repos, "qubesos4z6n4.onion" or "whonix 
> kk63ava6.onion". Is there any reason to prefer one over
> the other?
> 

No, both point to the same server.

> 2. Which onion address should be used for Qubes website access? 
> "http://qubesos4z6n4.onion/; or 
> "http://qubesosmamapaxpa.onion/;? Looks like the
> "qubesosmamapaxpa" site is not up to date.
> 

http://qubesos4z6n4.onion/ should be used. We don't have any
control over http://qubesosmamapaxpa.onion/ (it appears to be updated
only infrequently).

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

iQIcBAEBCgAGBQJYgCMuAAoJENtN07w5UDAwGMsQAJ/eqXk4yOOssNyYvokwkJs+
zvFR4xaX4LillkIceHroYy3yDhl7o7QergoDUPkUZqLhBrl+zakabJjWrPw9jDMV
LWgmldy2vq4mM/1jlU5wfHM9aja/497lpm7kgkMfYSZRHdgeY2eX96h/v3qg6Sqa
L9Xe3K9w5PMMpN4e2QeqNtPj1OMNGF96xx06Z4Kd0kN5fuVDEmf9t5UIjYp21nUD
DtPBS/nJzCcempxPKFsDbKWHrDvNV/kB+hXfzc7OyqlnM69aJPrNyxjsGKQTF7j6
0wQGtDUY3/1dRq4QZgOblMvRUO8KhixnHxgbXg2qXd39WEqPvlc0f5GsNIhaNlYK
6OhrbnABPjOCb7qWLCNDudSjVlBORb+kYHF67R5mwXK09P7on87sbz6pjrTCgZuv
oYR1mPIB+k0xbZc1/+L4fDmvUjg3jLSvY5qvZpG77xzOJhklS1aEpJL69z43Hpkq
nxWynqKGuvpoq1+oeAlICwiaC3pQXPWgPdmcKJLQ7kKDZixF9UL1D5Pq21jnrT0/
nrKNRYDwCVNLbs7oYbIdXTnY9TSR6JLkzQmgXLG17uYRMFRf1yEquCdOgH2cecZx
7+mvxlQBWALcerfe3py5/qYcd9srnaO+eNDadYnNc7AN5p9B1XXrvBMy5ZWtTh27
QuwsQhFCJ0laMXPz0rOP
=BU76
-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/41262301-b580-a5b6-77de-aa68ee6e908f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Drive Passthrough not functioning correctly.

2017-01-18 Thread '01v3g4n10' via qubes-users
On Thursday, January 19, 2017 at 12:48:17 AM UTC, Drew White wrote:
> Hi folks,
> 
> Here is what I was trying to do..
> Pass the drive to the guest.
> 
> 
> [{user}@dom0 {folder}]$ qvm-block -a {vmname} dom0:/dev/sdc
> Usage: qvm-block -l [options]
> usage: qvm-block -a [options]  :
> usage: qvm-block -A [options]  :
> usage: qvm-block -d [options] :
> usage: qvm-block -d [options] 
> List/set VM block devices.
> 
> qvm-block: error: Invalid device name: dom0:/dev/sdc
> 
> 
> 
> Why does it say that it's invalid device?
> 
> Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> 
> The device is there, so what's happenned?
> 
> Hope someone can help please.
> 
> Sincerely,
> Drew.
Try removing /dev/ from /dev/sdc and instead use dom0:sdc
qvm-block -a {vmname} dom0:sdc
https://www.qubes-os.org/doc/usb/

-- 
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/23da9da5-96ba-4cd7-a815-156d8445cb14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: All audio on streaming video out of sync

2017-01-18 Thread Gaijin

On 2017-01-18 16:23, raahe...@gmail.com wrote:

On Wednesday, January 18, 2017 at 12:44:28 AM UTC-5, Gaijin wrote:

On 2017-01-18 04:35, raahe...@gmail.com wrote:
> On Friday, January 13, 2017 at 9:03:03 PM UTC-5, Gaijin wrote:
>> All of the audio for videos played on my AppVMs, regardless of what
>> template it's based on (Fedora 24/Debian 8), or what browser I try
>> (Firefox/Chrome/Vivaldi), is completely out of sync. It's not just
>> YouTube, but Vimeo, self-hosted, etc.
>>
>> I tried uncommenting audio_low_latency in /etc/qubes/quid.conf in dom0
>> That didn't fix things.
>> I tried playing with the realtime-priority in /etc/pulse/daemon.conf
>> That didn't seem to make any difference.
>>
>> Are there any other places where I could try to fix this latency
>> issue?
>> I assume it's dom0 as everything is affected.
>
> whats your pc specs/ what soundcard?

I'm running Qubes R3.2
Sound is going through an nVidia GeForce GTX 560 Ti card. I don't have
nVidia drivers installed.
This machine has an Intel Core i7 2600 @ 3.40GHz CPU and 16.0GB
Dual-Channel DDR3 @ 665MHz RAM.


How are you plugging it in?  HDMI? if so you got further then I did.
I dont' get sound from hdmi only video.   Why not just use the onboard
sound card?


Oops I was going off an old hardware report from when this machine ran 
Windows. Got under the desk to check, and sound is going through the 
motherboard: ASRock H67DE


It operates fine usually, and never showed this sort of issue from Qubes 
1.x-3.1. When I upgraded to Qubes 3.2 I started noticing this lag. I 
don't watch a lot of video so it took me a while to notice.


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


[qubes-users] Re: QUBES 3.2 won't install... EFI_MEMMAP is not enabled... ESRT header is not in the memory map

2017-01-18 Thread xxthatnavyguyxx
This fixed the issue for me. Thank you S MUCH!

-- 
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/eb18f577-a7ea-445a-9450-7d372b4c8d3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Detection - Best Way

2017-01-18 Thread raahelps
On Wednesday, January 18, 2017 at 12:27:54 AM UTC-5, Asterysk wrote:
> It struck me that Qubes could be very useful for Detection of "malware" by 
> placing a monitoring capability . My question is in two parts:
> 
> (1) Is Wireshark the best tool to use for this within Qubes
> (2) Should it be placed in Dom 0 (if indeed thats possible) or in the sys-net 
> or sys-firewall

would be safer in sys-net,  although sys-firewall would tell you which vm 
making the connection.

-- 
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/526e10af-725a-4e45-a54c-4d2d2bac7c5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: USB & PCIe devices management questions

2017-01-18 Thread podmo
bb.alas...@gmail.com wrote:
> What about PCIe USB cards? Could I assign such pcie device to specific
> cube, so USB ports on that card are available only for that qube, as there
> is another controller on the card(I think so at least), or is my reasoning
> wrong?

Keep in mind you can passthrough a single USB device to a qube by
following the steps at the bottom of https://www.qubes-os.org/doc/usb so
you don't really need to use all these separate USB controllers, but the
method you are describing would work 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/d19965b0b6b79a1266f08b2897148668.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: USB & PCIe devices management questions

2017-01-18 Thread bb . alastor
What about PCIe USB cards? Could I assign such pcie device to specific cube, so 
USB ports on that card are available only for that qube, as there is another 
controller on the card(I think so at least), or is my reasoning wrong?

W dniu środa, 18 stycznia 2017 10:58:00 UTC+1 użytkownik Grzesiek Chodzicki 
napisał:
> W dniu sobota, 14 stycznia 2017 16:43:35 UTC+1 użytkownik B napisał:
> > Hello, for starters, pardon my ignorance, I am at the very beginning of the 
> > learning curve.
> > I am planning out a new workstation build, I want to plan it out with Qubes 
> > in mind. But I have few questions, as I do not have a Qubes compatible 
> > desktop right now, and my laptops are not really good to experiment with it.
> > 
> > I want to add and assign a secondary GPU to a Windows based VM, to be used 
> > as a gaming and CAD machine. If I do that, what about monitor output, if 
> > primary GPU is in dom0, do I need to connect second GPU to a monitor, or 
> > can I route the signal somehow without additional hardware?
> > I want to use few, separate, color coded USB hubs(spray paint for the win), 
> > each attached to different domain, with same color coding. I want it to 
> > work as seamlessly as possible, preferably with no additional steps after I 
> > attach/detach any device to/from a hub. It simply shows into a VM and acts 
> > accordingly. I have problem understanding how the qvm-pci and USB 
> > management works in this area. Is my planned use case even achievable or do 
> > I need to manage each device every single time I attach it?
> > Is assigning devices to vms persistent after booting, or can be made 
> > persistent?
> 
> GPU passthrough should work out of the box now so that's doable although I'm 
> afraid You're going to need a second monitor for that to work.
> 
> As for the hubs, this might be tricky without a large number of separate USB 
> controllers.

-- 
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/baa9a82f-6fc4-4437-a8f8-2b3c7e871b3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.