Re: [qubes-users] Qubes 3 MacOSX
On Sunday, April 2, 2017 at 5:09:05 PM UTC-7, Drew White wrote: > On Sunday, 2 April 2017 10:31:36 UTC+10, Eric wrote: > > Most of the following removed for brevity: > > > > On Sunday, November 6, 2016 at 4:37:15 AM UTC-8, Achim Patzner wrote: > > > > > > Point is: You can't buy a valid license without buying a machine with > > > it. I guess you could buy *heaps* of Mac mini just to obtain licenses... > > > Just like having to buy defective power supplies to get MagSafe > > > connectors. And Apple does not attack the people breaking the licenses; > > > they are usually aiming at those who enable others to break them (which > > > I regard as a good thing). > > > > > > > > > Achim > > > > > > Most of seems a bit misinformed (or at least very confusingly worded), and > > thankfully Apple's own SLA provides us with very direct answers: > > > > > > "B. License from Mac App Store. If you obtained a license for the Apple > > Software from the Mac App Store, then subject to the terms and conditions > > of this License and as permitted by the Mac App Store Usage Rules set forth > > in the App Store Terms and Conditions > > (http://www.apple.com/legal/itunes/ww/) (“Usage Rules”), you are granted a > > limited, non-transferable, non-exclusive license: > > > > [several sections removed for brevity] > > > > (iii) to install, use and run up to two (2) additional copies or instances > > of the Apple Software within virtual operating system environments on each > > Mac Computer you own or control that is already running the Apple > > Software." > > > > > > This is the license for the NON-SERVER version of Mac OS X Lion, 10.7, and > > every operating system since then has had a similar provision. This means > > that yes, you do need to run it on Apple hardware, but you can run up to > > three copies of OS X, or two in a virtual machine presuming you were using > > Xen or ESXi. > > > > Macs have good VT-d and VT-x support, but since they don't use PS/2 for > > trackpad and keyboard, or have a TPM, it would be a terrible platform to > > run Qubes on (trust me, I've tried). Not to mention that HiDPI support is > > still a work in progress - I miss my retina display something awful. > > > > > > Which brings us to the real question, how do we get this to work on Qubes > > today, on a non-Apple laptop? > > > > 1) accept that the developers will not work on making this happen, because > > Mac hardware is not a good target for Qubes unless something changes, and > > the dev's very limited time is much better spent elsewhere, especially > > given the potential for SLA abuse. I for one would much rather see Qubes 4 > > ship, than have macOS patches land. > > > > 2) accept *individual* responsibility for breaking a software license > > agreement. > > > > 3) try to make it work (not sure if those patches above still work in Xen > > 4.7, but Xen 4.7 might also have some of the newer code needed to make it > > work). ¯\_(ツ)_/¯ > > Also accept that if you have to patch Xen with code downloaded from a > > mailing list, you're probably downgrading your dom0 security, and therefore > > the overall system security, by a fair amount. > > > > 4) google a bunch (IIRC there is some info floating around on the QEMU > > mailing list that might help). > > > > 5) celebrate or drink, depending on the outcome. possibly both. > > > > The thing about the licensing is that IF you get permission from Apple to use > the OS under Qubes then you can. Even if it is not on Apple Hardware. > > If you get permission to do so then you can. There is no issue there. > > 1. The developers won't make it happen because they think it's breaking the > licensing to get permission to run it. > > 2. It isn't breaking the agreement if you have permission from Apple to do > the specified things. > > 3. I have patches and all that allow it to work in 3.0, all that one has to > do is update it to run properly on 4. But it can patch 3.1, however the > updates in 3.2 mean the patches need to be updated more. > > 4. Why use Google "a bunch" when you can just look on this forum and read > this thread? > > 5. Do both, because you should always celebrate both successes and failures. > From failure, you learn, from success, not so much. This thread has some interesting links, for example. (Though many things changed in Mavericks, and again in Sierra 10.12.4, so YMMV). Seems like the best option for now would be to try and get El Capitan running. -- 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/c59b8d70-94f5-4ba0-9054-4b173c618081%40googlegroups.com. For more options, visit http
Re: [qubes-users] Qubes 3 MacOSX
On Sunday, April 2, 2017 at 5:09:05 PM UTC-7, Drew White wrote: > > >The thing about the licensing is that IF you get permission from Apple to use >the OS under Qubes then you can. Even if it is not on Apple Hardware. Good luck. Apple has not done this for ANYONE, even the big names, since Steve Jobs came back. That door is closed. The way is shut. For our purposes, it's not a real option. > >If you get permission to do so then you can. There is no issue there. > >1. The developers won't make it happen because they think it's breaking the >licensing to get permission to run it. > >2. It isn't breaking the agreement if you have permission from Apple to do the >specified things. See the above. Short answer, if we can make it work such that it works on Apple laptops, no issue (and that work would likely carry over to non-Apple laptops, "incidentally" as it were. > >3. I have patches and all that allow it to work in 3.0, all that one has to do >is update it to run properly on 4. But it can patch 3.1, however the updates >in 3.2 mean the patches need to be updated more. So let's make that happen. There's an active ticket open (https://github.com/QubesOS/qubes-issues/issues/1982) but I imagine it would require a fair piece of work. (and I sure as shit don't know enough about hypervisor underpinnings to even take a stab at that). >4. Why use Google "a bunch" when you can just look on this forum and read this >thread? Because there are additional resources that might contribute knowledge and help - specifically the ones involving OS X on QEMU. >5. Do both, because you should always celebrate both successes and failures. >From failure, you learn, from success, not so much. *toasts* -- 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/f3feb181-b59b-41b5-9e24-5e32a9188dce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3 MacOSX
On Sunday, April 2, 2017 at 5:09:05 PM UTC-7, Drew White wrote: > > > The thing about the licensing is that IF you get permission from Apple to use > the OS under Qubes then you can. Even if it is not on Apple Hardware. Good luck. Apple has not done this for ANYONE, even the big names, since Steve Jobs came back. That door is closed. The way is shut. For our purposes, it's not a real option. > > If you get permission to do so then you can. There is no issue there. > > 1. The developers won't make it happen because they think it's breaking the > licensing to get permission to run it. > > 2. It isn't breaking the agreement if you have permission from Apple to do > the specified things. See the above. Short answer, if we can make it work such that it works on Apple laptops, no issue (and that work would likely carry over to non-Apple laptops, "incidentally" as it were. > > 3. I have patches and all that allow it to work in 3.0, all that one has to > do is update it to run properly on 4. But it can patch 3.1, however the > updates in 3.2 mean the patches need to be updated more. So let's make that happen. There's an active ticket open (https://github.com/QubesOS/qubes-issues/issues/1982) but I imagine it would require a fair piece of work. (and I sure as shit don't know enough about hypervisor underpinnings to even take a stab at that). > 4. Why use Google "a bunch" when you can just look on this forum and read > this thread? Because there are additional resources that might contribute knowledge and help - specifically the ones involving OS X on QEMU. > 5. Do both, because you should always celebrate both successes and failures. > From failure, you learn, from success, not so much. *toasts* -- 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/e2a529c5-4a1e-4fef-8f3a-0e5143bf4864%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [bug, 3.2, qubes manager] sys-whonix restart
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-04-02 13:45, Eva Star wrote: > Trying to restart running sys-whonix constantly give us this > assert: https://i.imgur.com/YU8sv3H.png > Known issue: https://github.com/QubesOS/qubes-issues/issues/2438 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJY4c5aAAoJENtN07w5UDAwv/MP/2QjoiW9rKpJLyrfib7B5/6q 2J8WPLamLlR0CgX3JSIMOkxCeAyOPOnyuX2Fj1WcQidiClQYjHdDF1S+Bi2ifyVN YM5czh2Pfn0h0k1UzLY29XMjpQbsmbsNpxvSFp92kvI6G8b5ZmqqlQ5CFKFsFxPf TjXyGji7f1fR8b8U/8e+p+/4VukgPD/P2DuBT+oN9nqHLxD+aYrj3SB6PXcRW/qV CO4M9MxJF4drBGklbCamV2WXzDt6nZItILIHpBZKjoHbWK8PCAPUPiB+ZC1ynA3X /2ZVufpZhfZXHiThJiExfBlmcJUOtvJUJNurwY5brOYrRkLSvthqF7fhUuZstiqD 1A9XoEY1IVcj3ksRhOrfMPDXrNPDBmrULVtAmk2OMeZ3ujODHvFFZZHC7qxizTa0 g7Wbb4qe/JrSKPnbqWxuf1snQjHm6MyJTICpXyrl8/HXEJXj+svFCfBQNKL6kB0O L74RlENEGsE4Iwvm9MnIzGxMltQDgf2xtEi0NUjcRjhaPgIXx+Eh1fPRDkRALSYS fFU+RgiSeUEHpWaQS09HZhDlX1vJSQCUT0YIJYyJF1H+qog1yYbnUmRz8hp7A4o5 o1rcCqXnVyB16upL87ckt0DVJRfPhiQKIHPHdkmjuo+Ua5USx0FQS3aspWbMUmza Y+/qXewqCY9dlSklJpoZ =q+33 -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/6d740b0d-89aa-d379-dd67-296776afddfa%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3 MacOSX
> The thing about the licensing is that IF you get permission from Apple to use > the OS under Qubes then you can. Even if it is not on Apple Hardware. Sure. This, however, essentiually means you get a different license. Well, anything that the original license does not allow can be solved by licencing the software under a different license – provided that the vendor wishes to do so. But the key question is, how hard is it to get the license. I doubt Apple will give the license to anyone who asks. If they did, why would they put the restrictions on the standard license? 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/8d13a4c7-1d29-4f29-801a-7a084b1c146b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3 MacOSX
On Sunday, 2 April 2017 10:31:36 UTC+10, Eric wrote: > Most of the following removed for brevity: > > On Sunday, November 6, 2016 at 4:37:15 AM UTC-8, Achim Patzner wrote: > > > > Point is: You can't buy a valid license without buying a machine with > > it. I guess you could buy *heaps* of Mac mini just to obtain licenses... > > Just like having to buy defective power supplies to get MagSafe > > connectors. And Apple does not attack the people breaking the licenses; > > they are usually aiming at those who enable others to break them (which > > I regard as a good thing). > > > > > > Achim > > > Most of seems a bit misinformed (or at least very confusingly worded), and > thankfully Apple's own SLA provides us with very direct answers: > > > "B. License from Mac App Store. If you obtained a license for the Apple > Software from the Mac App Store, then subject to the terms and conditions of > this License and as permitted by the Mac App Store Usage Rules set forth in > the App Store Terms and Conditions (http://www.apple.com/legal/itunes/ww/) > (“Usage Rules”), you are granted a limited, non-transferable, non-exclusive > license: > > [several sections removed for brevity] > > (iii) to install, use and run up to two (2) additional copies or instances of > the Apple Software within virtual operating system environments on each Mac > Computer you own or control that is already running the Apple Software." > > > This is the license for the NON-SERVER version of Mac OS X Lion, 10.7, and > every operating system since then has had a similar provision. This means > that yes, you do need to run it on Apple hardware, but you can run up to > three copies of OS X, or two in a virtual machine presuming you were using > Xen or ESXi. > > Macs have good VT-d and VT-x support, but since they don't use PS/2 for > trackpad and keyboard, or have a TPM, it would be a terrible platform to run > Qubes on (trust me, I've tried). Not to mention that HiDPI support is still a > work in progress - I miss my retina display something awful. > > > Which brings us to the real question, how do we get this to work on Qubes > today, on a non-Apple laptop? > > 1) accept that the developers will not work on making this happen, because > Mac hardware is not a good target for Qubes unless something changes, and the > dev's very limited time is much better spent elsewhere, especially given the > potential for SLA abuse. I for one would much rather see Qubes 4 ship, than > have macOS patches land. > > 2) accept *individual* responsibility for breaking a software license > agreement. > > 3) try to make it work (not sure if those patches above still work in Xen > 4.7, but Xen 4.7 might also have some of the newer code needed to make it > work). ¯\_(ツ)_/¯ > Also accept that if you have to patch Xen with code downloaded from a mailing > list, you're probably downgrading your dom0 security, and therefore the > overall system security, by a fair amount. > > 4) google a bunch (IIRC there is some info floating around on the QEMU > mailing list that might help). > > 5) celebrate or drink, depending on the outcome. possibly both. The thing about the licensing is that IF you get permission from Apple to use the OS under Qubes then you can. Even if it is not on Apple Hardware. If you get permission to do so then you can. There is no issue there. 1. The developers won't make it happen because they think it's breaking the licensing to get permission to run it. 2. It isn't breaking the agreement if you have permission from Apple to do the specified things. 3. I have patches and all that allow it to work in 3.0, all that one has to do is update it to run properly on 4. But it can patch 3.1, however the updates in 3.2 mean the patches need to be updated more. 4. Why use Google "a bunch" when you can just look on this forum and read this thread? 5. Do both, because you should always celebrate both successes and failures. >From failure, you learn, from success, not so 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/41e259da-2a73-430e-b384-4cfdaf35eae0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Testers wanted
On Sun, Apr 2, 2017 at 4:49 PM, Eva Star wrote: > On 04/02/2017 09:23 PM, John Casey wrote: >> Apologies as I am not totally familiar with mailing list etiquette, but >> would it be better to include the mailing list so as to maintain a record >> of volunteers? > > Or full list of tasks that need to do on some page and when done by someone > and reported to Unman then remove the task from the page. You can just filter them: https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.1+updates%22 Issues that get closed will disappear from that list automatically. -- 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/CABQWM_ACJ0P8aTg0TGeWkK_sqp%3DmktyRVfbC_6U_mPRRgvw%3DwQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HDMI-related threats in Qubes OS
> We may want to open an issue for this, or at least a thread in qubes-developer. IMHO not at this time: * Now, we don't know the current state. There might be nothing to change. * AFAIR users/devel distinction is mostly based on stable/devel versions. Since this question does not address any specific version, it is probably OK to be in users list. * Developers seem to read both lists. > I don't believe this means that HDMI features carry over to DVI outputs Neither do I. But if both endpoints do support HDMI, it could be theoretically negotiated even over DVI cable, provided that no mandatory wire is missing. Note that I considered this connection: laptop HDMI –> HDMI-to-DVI –> DVI-to-HDMI –> TV HDMI. > If the compression is only in one direction (out to the display) then I don't > think it matters Sure. But what would be the point of using it on some places without using it at others, except of reducing attach surface (which I don't believe was an objective of HDMI design)? > even good-old VGA has a bidirecional serial communication build-in I know. But the complexity is quite different, which is what matters. > A side remark is that this may be turned in a feature rather than a problem Sure, it is a double-edged sword. Actually, I originally wondered if HDMI could be used for connecting mouse and keyboard without having an extra USB controller. But then I realized that such feature cam be used also for attacks. 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/eb13f9c7-6d29-498c-a922-a3053736003e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Testers wanted
On 04/02/2017 09:23 PM, John Casey wrote: Apologies as I am not totally familiar with mailing list etiquette, but would it be better to include the mailing list so as to maintain a record of volunteers? Or full list of tasks that need to do on some page and when done by someone and reported to Unman then remove the task from the page. -- 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/51c231e5-442c-d762-eb8f-16f60408a8e7%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] [bug, 3.2, qubes manager] sys-whonix restart
Trying to restart running sys-whonix constantly give us this assert: https://i.imgur.com/YU8sv3H.png -- 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/686f404c-55a6-bac1-c959-21c182869fc5%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Testers wanted
On Sunday, 2 April 2017 04:17:20 UTC+1, Unman wrote: > > Hello all, > > Now that r3.1 is end of life, we need to do some work to clear the 113 > bugs that are still open. > > A first step would be to triage the bugs to see what still affects 3.2 > and what can be closed. > If you are interested in helping out, please reply to me rather than to > the list. Ideally you will have a fairly vanilla 3.2 you can use for > testing. If you can send me a note of your hardware that would help in > allocating bugs where the original report referred to specific hardware. > > Apologies as I am not totally familiar with mailing list etiquette, but would it be better to include the mailing list so as to maintain a record of volunteers? Regardless, I'm running 3.2 on a MBP Early 2013 (i5-3230M). I also am able to run on a desktop (GA-X99-UD4P, i7 5820k, GTX 660). More than happy to help if I can. > With a bit of effort we should be able to clear these pretty quickly, > and you will have helped make Qubes that little bit better. > > cheers > > unman > Regards, John -- 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/f5e8258d-c812-4ba5-b370-cf5b03fc9962%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HDMI-related threats in Qubes OS
> I think having a graphics driver that disables any auxiliary modes (on > the GPU) would be a reasonable first step in addressing the issue. It > may also be possible to disable HDMI ports in favor of simpler ones like > VGA. I'm not sure how much input DVI and Displayport allow, but I think > there's a chance that DVI is similar to VGA in this regard. I just mention that even good-old VGA has a bidirecional serial communication build-in (google: vga & I2C). Bernhard P.S: A side remark is that this may be turned in a feature rather than a problem : it is a way to replace usb for some applications (yubikey type cards for example, where transmission speed is not a problem). -- 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/bfdd3d8e-2a16-c8ab-b927-02a78b78f370%40web.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HDMI-related threats in Qubes OS
On 04/02/2017 03:42 AM, Vít Šesták wrote: Yes, disabling those features can prevent thise threats. But I wonder if Qubes does this by default or if I can disable it manually. We may want to open an issue for this, or at least a thread in qubes-developer. I have also an idea how to disable it, but I am unsure if it will work properly: Connect laptop HDMI port -> HDMI to DVI -> DVI to HDMI -> TV HDMI port. But since no conversion is needed, you might end up with full HDMI connection. Related quotation: “HDMI implements the EIA/CEA-861 standards, which define video formats and waveforms, transport of *compressed*, uncompressed, and LPCM audio, auxiliary data, and implementations of the VESA EDID.[5][6](p. III) *CEA-861 signals carried by HDMI are electrically compatible with the CEA-861 signals used by the digital visual interface (DVI). No signal conversion is necessary*, nor is there a loss of video quality when a DVI-to-HDMI adapter is used.[6](§C)” (https://en.m.wikipedia.org/wiki/HDMI, emphasis is mine) I don't believe this means that HDMI features carry over to DVI outputs on computers, just that HDMI ports can output to DVI displays. But it would be good to know what an HDMI-capable monitor can do, for instance, if a DVI-only card is plugged into one of its DVI ports. My notes on this: 1. Compressed audio is not what I want for Audio return channel :(. 2. The [6](§C) links to Appendix C of HDMI spec (see http://www.microprocessor.org/HDMISpecification13a.pdf ), which defines *bidirectional* compatibility level between HDMI and DVI. Regards, Vít Šesták 'v6ak' If the compression is only in one direction (out to the display) then I don't think it matters... or its a feature you want to keep. What we need is a breakdown of the supported protocols along with a description of their interactivity and flow. -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/50c99240-23e8-0327-a252-a5a4b39b5b95%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HDMI-related threats in Qubes OS
Yes, disabling those features can prevent thise threats. But I wonder if Qubes does this by default or if I can disable it manually. I have also an idea how to disable it, but I am unsure if it will work properly: Connect laptop HDMI port -> HDMI to DVI -> DVI to HDMI -> TV HDMI port. But since no conversion is needed, you might end up with full HDMI connection. Related quotation: “HDMI implements the EIA/CEA-861 standards, which define video formats and waveforms, transport of *compressed*, uncompressed, and LPCM audio, auxiliary data, and implementations of the VESA EDID.[5][6](p. III) *CEA-861 signals carried by HDMI are electrically compatible with the CEA-861 signals used by the digital visual interface (DVI). No signal conversion is necessary*, nor is there a loss of video quality when a DVI-to-HDMI adapter is used.[6](§C)” (https://en.m.wikipedia.org/wiki/HDMI, emphasis is mine) My notes on this: 1. Compressed audio is not what I want for Audio return channel :(. 2. The [6](§C) links to Appendix C of HDMI spec (see http://www.microprocessor.org/HDMISpecification13a.pdf ), which defines *bidirectional* compatibility level between HDMI and DVI. 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/27688cd4-1552-4dd0-858e-a08555c29cfe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Installation from a tarball: any Qubes OS particulars?
When I install something from a tarball, I try to minimize processing the software in the particular TemplateVM. I try not to run any script from it. Even unpacking is a potential threat (in case of vulnerability in the unpacker). This is also the reason why I don't prefer compilation from source. Maybe DVM could resolve some of those problems. Unfortunately, this is going to be slow if the DVM is based on the currently running template. Qubes 4 will have redesigned DVMs that seem to avoid this issue. 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/90077405-fbdd-44e5-83b2-c1687a25d2c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: USB Headset
Forgot to mention: AFAIR, Qubes 4.0 will have Linux-based stubdoms. Maybe they will support USB passthrough or even sound directly. I am not 100% sure about it, but Linux-based stubdom seems to be a step towards those features. 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/95aed386-bba2-4737-a942-68f7f3d52d98%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: USB Headset
Note that even having multiple USB controllers does not imply a win. Some controllers might be just internal (for integrated webcam, touchscreen etc.) and some might be needed for another purposes (e.g., keyboard attached to dom0, phone attached to sys-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/4b39b498-2078-4968-a01c-928c70d03d7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
