Re: [qubes-users] Re: How to view Youtube in Fullscreen ? (for dummies)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-28 04:14, Manuel Amador (Rudd-O) wrote: > On 10/27/2016 01:31 AM, raahe...@gmail.com wrote: >> On Wednesday, October 26, 2016 at 5:15:53 PM UTC-4, jamie wrote: >>> does not matter if I use fedora, debian or whonix ... whenever I press >>> fullscreen on any youtube video the brower freezes.. >>> >>> it also does not matter which browser I use firefox, chromium,... >>> all of them freeze. > > I can confirm this issue. It's not that they freeze, they continue to > run and you can see window updates when you resize the window, but it's > simply that they stop updating after hitting that damn fullscreen > button. This is a new bug and I recommend you file a ticket in > https://github.com/QubesOS/qubes-issues/new . > Issue filed: https://github.com/QubesOS/qubes-issues/issues/2406 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYFCSlAAoJENtN07w5UDAwSwsP+wfRmMCy1Hr/CPvFbFL8i2sl RlGVctDOoG7PUYZhdrQoSq89EcgjVwAgUS1VVBQjKCd2t69iQvplLofNvbf/wstk 9+kz1e1c9MACUup6p/v3UM1fmx+sjQW6BB+fWWWZAs2osZHoRDnKIaW+FNi5ZMal tbXbv7EoXSISAZ6FRyBqOuMq74xuBgdByBGm8fhZrcFEIBsm5l0dYU+1jxvh30Cg HEOsT/e6BE4tmYUnvekKtAMlDA8NG0UK27F3XdPe1AdK3+1alVc4SgyWdqQplCsf lwO0OwkIdL0X41J6bZBG5PXBpZCKlzQa/DfQ9t6GSadWfApDhxHOa5TLjMKgSX8W W8TezKBOGbFC2wXZ8ZqmR8kJ82mfXX1B4DvEZmVrH0AuoApl+M2XaGUylPv83B7q tuZrmVStdG1HKZlH62tnBw6xGbSpE+f4K3LiBJXDEG2T6XuTZpY9BExh75PrgB0o nSeSJq8uxzjS2tSTmTots+SQ/CrhflQ8AxgFPoV5Aij/gdtehotMN8RPOSMQf+4p M022qEvsbweDRZU1RcNOJEMQAAGWbpBq9z8BJtbFve/sykhzA8YhAUmDC7BHDgSB hKZn7PmOkdJBoyFpFFumRtlLTEG+DHOdtMRf22UGYDPuxhr4BDC71HZ27xjJ+Z+z ww9WpjSmrvVUTjhYYZ6R =nCch -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/1862a072-a631-95fc-7e5c-e63bbff43824%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to turn Windows HVM into Fullscreen ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-28 16:13, farty wrote: > I want to use my windows HVM for watching youtube videos. > > for audio support I simply assign my audio card to the windows HVM > and install the drivers into the windows HVM > > but how can I scale the windows screen to fullscreen (till taskbar) > like in my fedora appvm ? > Have you tried this? https://www.qubes-os.org/doc/full-screen-mode/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYFCJAAAoJENtN07w5UDAwUPQP/AxOSYbo9TXQYEmJXrh3ptOd jrISjz3r1bUyCFbjl7kkK7cB5X13UD3UEBLjAGmjOGDltbsghQvV6PHK0yBBVKxq DLZ/vjgklPA2YmFYiFeXZF8nFWAL+MTxE1DdfyUUpeCUIfhcSoWexQSjtpKLcu7t z4kW2JqBml/oTEkdDL8PV7W6aMtEdeDShFPcT1c3JIvzUmPEVxt8peYbtLzJj63a Y5abQeeVYTdRYXiiYvAqhqtwMgFz6kRjGoa+Jbb3hOZeeh5jkfaSbOMzaB+FJmm8 Rn6SR0RBabITEC3q/v7dXXM7mXfo0GLtHAhYnvQZtSLyTH4A2IQCoutFV/t7AFwg xmm9wtUYj/KHesUwwxdTbchyL3HCUiKWA7500H3QGGTyfqFmkpvalTMYRFUrQOiw dJnQDnlHY+cPItgM2uRXEaPc8Gb4AvrtG1zaUcF8JtzD+mUXxyo3QgWCe/bYoTyg 30HPKhC4fH4C1ZZjijUwLzrQ5YAsQmQRLPINjkCT1MMcxRD2Uwup5gEFeEQfAWxR rig/yZRfeisNfjTiShpdvM+DTbROmRXI8FjFvGbMiC4Td4NCNiCiDGy0qSoP1puH U45tbKMz914ybR2tFuC4/62Wg2JOXLdtGaZPC2WHSETaX3PT60kDGykPaUQYv8cQ PvPgkBiLPaNadEmgaWYN =7lRk -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/0f48dae4-9416-372c-813e-b409c6f7de36%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] XScreenSaver for dom0 pops up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-28 14:25, Gaijin wrote: > On 2016-10-27 04:42, Andrew David Wong wrote: > On 2016-10-26 15:53, Gaijin wrote: On 2016-10-26 13:38, John Maher wrote: > On Wednesday, October 26, 2016 at 9:05:48 AM UTC-4, Gaijin wrote: >> On 2016-10-26 12:43, John Maher wrote: >> > I'm getting the strangest thing on my screen. I'll be working and the >> > XScreenSaver dialog pops up (indicating the screen is locked) and the >> > screen goes black. However, the screen is not locked. I have to move a >> > window around to redraw my screen. This has always happened since I >> > started using Qubes about 3 weeks ago. There appears to be no pattern >> > that prompts this response. Bizarre! Any thoughts? >> > >> > Thanks. >> > >> > John >> >> Yeah. I had the same thing happen when I upgraded to R3.2 as well. I >> asked the same thing but nobody replied. >> https://groups.google.com/forum/#!topic/qubes-users/xjHi2TcYBAQ >> >> It still happens from time to time. Seems to happen less if I have a lot >> of free memory. Closing down some memory hungry AppVMs seems to lessen >> it, but I haven't been able to specifically replicate it. > > Interesting, because I think I have more than enough memory (32 GB). > Thanks. I've got 16GB myself. It's not that the memory is full, but it seems to happen more when I have a lot of VMs open in one desktop. That may just be a coincidence though. I'm glad to see it wasn't just me though. I never had this happen with earlier versions of Qubes on the same hardware. Not sure if it might be the XFCE or a video driver issue. (I've never installed the nVidia drivers.) > > Thank you both for reporting this. Gaijin, I'm sorry I missed your thread. > > Just to confirm: Are you both using Xfce4? > > Tracking the issue here: > > https://github.com/QubesOS/qubes-issues/issues/2399 > > > I used the default install parameters of R3.2. xfce4-about in dom0 shows I'm > using version 4.12. The same hardware since R2 has not experienced this. > Understood. Thanks. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYFCE7AAoJENtN07w5UDAwDdkP/RUMyUrw2tWGU+BO6NlYIgwT O6M7eN8doCxr/gMyWoag1vt4DGBr9AkHeQwSU+UvLMfARDueDVx4Wm2xH27nlUpo SIfkcwMHt6ZhPjCtqgwH39axM8K+35le8Amx+tEw7iPMTPDQ2qDxRV6CrViXkcUp IEG3Os/Izv4IkKFXtV0D/EQuwD7VgoPpsc7DFA1JlhzBk51n6UkloCinwz5c01lw 0i/eAGIF1A+CI+QtT7/0Clf4aIMOnM0xNLYUH9UC4+puiyULKJ0Ic+I+tSEViCye a7nmdnO4tUrvfr+RIvVzj57cZdM+R+mU5yYJIZqn4zwPicq2Ew4puSe9fInCnApH ZeCLOYv/LaOmbW8QOUsUFP5VF1JphwFDb8cH67Z28nWpVQfJRqocvL96wOirC58l J8fYxuEEdVeXWibVnxUJA/I2hv9hsguOhlU15jkuQ+jIi9bOkn5xUqm6hHIq9W5y IKgA/hTARiZzwi1u7suqDGpYQ593iRktBGblo5HnUgmXG3zOmt7sVXJ2fv89NX6B T9v3gKVOD8+dj1QmqrsZIyhwP7lXWzteIogwsvgzRtJlMhLshHtqityFpsYCvs87 lyu/ycoCgggJglzOsD7xcC9gVyoxjI3OV+B+W88pNla5OUu0APAkwTeIYBwGkAFZ QGAa5RsZQzXyspk6jTs3 =sE6O -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/d599b4ff-84d1-4965-2fa7-b50e88a1473e%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't figure out how to install a couple of things in dom0
On Tuesday, 25 October 2016 06:02:08 UTC, Andrew David Wong wrote: > > Enabling RPMFusion in dom0 is generally not recommended, but it should be > possible if you're willing to accept the risks. I would start by trying doing > it in the standard Fedora way (but I haven't tried this myself). > > As for searching for packages, you can pass most of the standard yum/dnf > commands to qubes-dom0-update. Personally, I like to do the searches (`dnf > search`) in an AppVM, then, once I've found the correct package names, > install them in dom0 (`qubes-dom0-update package-name`). Thanks, this answers my question :) -- 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/393ddcc9-2fa1-4cb9-be9d-363af118b408%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2 - Whonix GW VM Update
On Saturday, October 29, 2016 at 2:18:35 AM UTC, Vincent Elliott wrote: > Hi, > > I am very new to Qubes. > > In trying to update the Whonix GW VM, the updater reports that the file sizes > are different from what the server reports. In every instance I have rolled > back the updates. > > Is this normal? > > Vincent It's not normal in that it shouldn't be happenning. It is normal in that it is happening to everyone. But no need for concern: https://forums.whonix.org/t/size-of-file-dists-jessie-main-binary-amd64-packages-gz-is-not-what-the-server-reported/3074/2 -- 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/614722cd-e3ee-42f8-bc19-ad6ab154f18f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to view Youtube in Fullscreen ? (for dummies)
On Friday, October 28, 2016 at 7:06:30 PM UTC-4, blmabo wrote: > I still can not get it to work?? > > what command do I need to type that stays permanently > I dont want to type it in over and over again What did you do to get it working temporarily? -- 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/bb4c640e-846d-4298-a81a-729603050ab0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 - Whonix GW VM Update
Hi, I am very new to Qubes. In trying to update the Whonix GW VM, the updater reports that the file sizes are different from what the server reports. In every instance I have rolled back the updates. Is this normal? Vincent -- 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/CANNetsNFR5q0Kw4kJWLSs3ORJ9181d6he9kOAyPeYMrmg_zTZw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 - TeamViewer not connecting
Hi, Am very new to Qubes OS and am trying to get TeamViewer v11 working. The problem is it will not connect and is requesting proxy settings. Anyone had any success with this? Vincent -- 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/CANNetsMTu0TqU2jBSO3TcmLyqMSm7kzjnY25edkm7bKmhkfUSQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 3.2 Install: Error unpacking qubes-template-fedora-23
I just tried to do so, it says these files are different: On sdX1: images/efiboot.img Packages/q/qubes-template-fedora-23-3.06-201608081228.noarch.rpm On sdX2: System Volume Information/WPSettings.dat Didn't got any further informations, and I'm quite unexperienced with diff, so I hope it helps. Also, I just checked that Rufus is the newest version (Checked it because I had the binary on my computer for a couple weeks, but its still up2date). I'll take a closer look at them tomorrow evening. -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 28, 2016 at 02:24:02PM +0200, Fabian Wloch wrote: I can confirm that error under certain circumstances. If I write the ISO (checked via Sha256+GPG) with Rufus from Windows 10, I get the exact same error under multiple computers with totally different hardware. If I write it on my USB drive with dd under Fedora 24, it works without any errors. Used the same hardware to write the same iso onto the same usb drive, just once with Win10 and once with Fedora. Maybe you try it this way aswell if you didnt already found another solution. Any chance to check what is different between such created USBs? For start, I'd run `diff -Nrb` on them. If that yields no difference, then compare hexdumps, like this (works on bash): diff <(hexdump -n 4246732800 -C /dev/sdb) <(hexdump -n 4246732800 -C /dev/sdc) where /dev/sdb and /dev/sdc are two device created using different methods. The -n parameter to hexdump is installation image size, to not compare the whole device. - -- 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 iQEcBAEBCAAGBQJYE7nDAAoJENuP0xzK19csSo0H/3XCgRTQlrJxkftyk3qo63FF qPiZ19s+PouAbNPHHH3t4ulvzupsO8S6XxLyo+b97fwF9sEWEgCRViQJ5mlNu3M0 wmB7qYMHHurhXfSV2DljHGvvN871WnY7ZkliMGcvpu646zv5zT1d4a+CghHn2dcc IMzYYKDIN4HcmWhSS5NPezhwXjw6KjCLXMwxJW3dIwSz/jOcSM9CTAwcTXlhfZDu E4fZaUbTEPiCZPptDywnwdPlB71Ea9YKsXVj+Alq2a7g4t3AaBkujQICd0qaW9lL IXSZFGEsLr03KbPYcQDIW8XfCUfn5hCYV4o0lXCVwIuETtN3u9IKjF04nXht52k= =wIE1 -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/1580daf40b8.275d.db864a7b1d5e2becb017b42ae5cd9fc6%40posteo.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to turn Windows HVM into Fullscreen ?
On Saturday, October 29, 2016 at 1:13:21 AM UTC+2, farty wrote: > I want to use my windows HVM for watching youtube videos. > > for audio support I simply assign my audio card to the windows HVM > and install the drivers into the windows HVM > > but how can I scale the windows screen to fullscreen (till taskbar) > like in my fedora appvm ? EDIT: just assigned my notebook audio card to the windows hvm and my whole system did not work anymore... how to fix that? -- 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/3c23fb96-e7a7-423b-aee6-94fe20c6e31b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How to turn Windows HVM into Fullscreen ?
I want to use my windows HVM for watching youtube videos. for audio support I simply assign my audio card to the windows HVM and install the drivers into the windows HVM but how can I scale the windows screen to fullscreen (till taskbar) like in my fedora appvm ? -- 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/0e40ff31-f1a1-4a4c-a91e-c6134ee350d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to view Youtube in Fullscreen ? (for dummies)
I still can not get it to work?? what command do I need to type that stays permanently I dont want to type it in over and over again -- 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/8a8103d4-146b-45f2-9ae3-c1227553c5dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] XScreenSaver for dom0 pops up
On 2016-10-27 04:42, Andrew David Wong wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-26 15:53, Gaijin wrote: On 2016-10-26 13:38, John Maher wrote: On Wednesday, October 26, 2016 at 9:05:48 AM UTC-4, Gaijin wrote: On 2016-10-26 12:43, John Maher wrote: > I'm getting the strangest thing on my screen. I'll be working and the > XScreenSaver dialog pops up (indicating the screen is locked) and the > screen goes black. However, the screen is not locked. I have to move a > window around to redraw my screen. This has always happened since I > started using Qubes about 3 weeks ago. There appears to be no pattern > that prompts this response. Bizarre! Any thoughts? > > Thanks. > > John Yeah. I had the same thing happen when I upgraded to R3.2 as well. I asked the same thing but nobody replied. https://groups.google.com/forum/#!topic/qubes-users/xjHi2TcYBAQ It still happens from time to time. Seems to happen less if I have a lot of free memory. Closing down some memory hungry AppVMs seems to lessen it, but I haven't been able to specifically replicate it. Interesting, because I think I have more than enough memory (32 GB). Thanks. I've got 16GB myself. It's not that the memory is full, but it seems to happen more when I have a lot of VMs open in one desktop. That may just be a coincidence though. I'm glad to see it wasn't just me though. I never had this happen with earlier versions of Qubes on the same hardware. Not sure if it might be the XFCE or a video driver issue. (I've never installed the nVidia drivers.) Thank you both for reporting this. Gaijin, I'm sorry I missed your thread. Just to confirm: Are you both using Xfce4? Tracking the issue here: https://github.com/QubesOS/qubes-issues/issues/2399 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYEYWaAAoJENtN07w5UDAwvq8P/1hFm/owsEasSXroxzK9JnTn DSBZ9udjO+TWQypb4Hh4RO48MtJnQhKfdgJJWWJwf9dTp62LUBkVWskKDtvOfyo+ aoVFGRBexb7yzRT90kBsjHiVPeysA4bTBftQZEZzTQBz/UzRzMkcBWj7/vbYrTkL zeG42ZCuM75jzOv2dhrG2TeP+OlTfdnFIyFQFmdaRJyHTOBtf7Mjauuj4gFEiKNr ztMO4jE/kn+/E79cGu33VfrxITmiH7Z5tqZQuAS0Mud9YnBuCDumIugPuSleV3IL xARHjYjui+yPOzB66yZiDlQhTMRaEhEEQVR6UWMU+SC/nec+dTpWq/b7EgktXdud NpJr+jIDfaoNdVBtDFIXRBo6vbR05dtWQFfLIeewGIhIC9VwLJSwEW2TvCTWFOcO kXWV4xsg1xAJNbNBm9V42yZ6M1P+ClXlAcJYPVqrk+xisLtlWAweqT4yKw3zq5HW rlgkLYoNAjU3ZvTHYa/2JtyQZKbUUw+ck8nRRuLUp0jqM/2TlZfQ7tmfsfb5z1HS mzNe6UHhg5ZtoV0HKbyMIWa5ePVZaMJCkhNOMAuAQ9QBpJgqE7dWZx28S5eqnAno WTFQI9nT6JCQz7YvmIkrxQDCUmG5JQqZlqIXArRS0WNjAzNMraKBsWeHTOqha4he HiI1LB04rOraNysdPTpj =MANy -END PGP SIGNATURE- I used the default install parameters of R3.2. xfce4-about in dom0 shows I'm using version 4.12. The same hardware since R2 has not experienced 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/96c98a10bb822b711c83816b3d189de3%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 3.2 Install: Error unpacking qubes-template-fedora-23
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 28, 2016 at 02:24:02PM +0200, Fabian Wloch wrote: > I can confirm that error under certain circumstances. > If I write the ISO (checked via Sha256+GPG) with Rufus from Windows 10, I > get the exact same error under multiple computers with totally different > hardware. > If I write it on my USB drive with dd under Fedora 24, it works without any > errors. > > Used the same hardware to write the same iso onto the same usb drive, just > once with Win10 and once with Fedora. > > Maybe you try it this way aswell if you didnt already found another solution. Any chance to check what is different between such created USBs? For start, I'd run `diff -Nrb` on them. If that yields no difference, then compare hexdumps, like this (works on bash): diff <(hexdump -n 4246732800 -C /dev/sdb) <(hexdump -n 4246732800 -C /dev/sdc) where /dev/sdb and /dev/sdc are two device created using different methods. The -n parameter to hexdump is installation image size, to not compare the whole device. - -- 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 iQEcBAEBCAAGBQJYE7nDAAoJENuP0xzK19csSo0H/3XCgRTQlrJxkftyk3qo63FF qPiZ19s+PouAbNPHHH3t4ulvzupsO8S6XxLyo+b97fwF9sEWEgCRViQJ5mlNu3M0 wmB7qYMHHurhXfSV2DljHGvvN871WnY7ZkliMGcvpu646zv5zT1d4a+CghHn2dcc IMzYYKDIN4HcmWhSS5NPezhwXjw6KjCLXMwxJW3dIwSz/jOcSM9CTAwcTXlhfZDu E4fZaUbTEPiCZPptDywnwdPlB71Ea9YKsXVj+Alq2a7g4t3AaBkujQICd0qaW9lL IXSZFGEsLr03KbPYcQDIW8XfCUfn5hCYV4o0lXCVwIuETtN3u9IKjF04nXht52k= =wIE1 -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/20161028204907.GR7073%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 3.2 Install: Error unpacking qubes-template-fedora-23
On Friday, October 28, 2016 at 5:24:07 AM UTC-7, Fabian Wloch wrote: > I can confirm that error under certain circumstances. > If I write the ISO (checked via Sha256+GPG) with Rufus from Windows 10, I > get the exact same error under multiple computers with totally different > hardware. > If I write it on my USB drive with dd under Fedora 24, it works without any > errors. Thanks Fabian, that pattern held true for me as well. Writing Qubes-R3.2-x86_64.iso with Rufus from Windows 10 had the error. Writing Qubes-R3.2-x86_64.iso with dd from macOS to if=/dev/disk2 and if=/dev/rdisk2 had the error Writing Qubes-R3.2-x86_64.iso with dd from the fedora-23 qube resulted in install media that worked completely. -Evan -- 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/7e1bb053-75a5-46e3-914b-543409504060%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: HCL - DELL PRECISION T7400
Updating the bios might fix your VT-d issue however a lot of the older dell computers have bad implementations/DMAR tables - you are also stuck with an earlier processor with IOMMU V1 which lacks interrupt remapping (a security feature). Worse comes to worse you can always use flashrom and write the bios externally. -- 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/d9b92bab-16cb-1f31-e014-f2df09c63235%40gmx.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] windows7 hangs on installation
Thanks for your answer. I wait about 6 hours but nothing happens. Of course you´re right. I just installed the QWT to dom0. -- 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/0a0c0a64-b18e-449d-99ca-f7ad4c329d62%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] No Kernel update since dirtycow (copy-on-write) exploit?
Qubes still use 4.4.14-11. So it's still vulnerable, right? Even qubes not like a normal linux distribution i would sleep better if we get a update. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/nv0587%24t27%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Introducing the qubes-announce read-only mailing list
Am 28.10.2016 um 12:32 schrieb Manuel Amador (Rudd-O): > Forgive me for asking this: Forgiveness granted. > Anyone else beginning to get annoyed No. I'm so far beyond the beginning that I'll probably start being unfriendly to him soon. Achim -- 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/00509084-0c7e-2822-5b1b-f8f270f1f1d5%40noses.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Windows HVM doesn't get updates
Try to install KB3020369 first and then KB3020369 (May 2016 Rollup Update). That worked for us. Searching for updates is reasonably fast now on our Qubes Win HVMs -- 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/a9350c8c-ddc1-504c-a2f7-8c8d3140a662%40digitrace.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Crashplan?
I think your approach is actually better though. Vincent On Oct 27, 2016 5:34 PM, "Andrew David Wong"wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-10-27 13:38, Vincent Elliott wrote: > > On Friday, 21 October 2016 22:54:53 UTC-5, Andrew David Wong wrote: > > On 2016-10-21 11:08, Max wrote: > On Monday, 27 June 2016 04:21:20 UTC+8, Andrew David Wong wrote: > On 2016-06-26 12:07, Niels Kobschaetzki wrote: > >>> On 16/06/26 08:40, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > > On 2016-06-26 04:27, Niels Kobschaetzki wrote: > > Hi, > > > > does anyone have experiences with running Crashplan in Qubes? > > If yes, how did you install it? > > > > Niels > > > > I installed it in a StandaloneVM with the installer's default > options. > > (As I'm guessing you've discovered, attempting to install it in > an AppVM with the default options doesn't allow it to persist > across reboots since it tries to install parts of itself to the > read-only root filesystem.) > >>> > >>> Ok, thanks. And then you transfer the data from the other VMs to > >>> that VM to back it up via Crashplan? Sounds like a lot of redundant > >>> data or do you have multiple disks (like a fast SSD for daily usage > >>> and a slow spinning disk for your backup-VM) in your computer? > >>> > >>> Niels > >>> > > I just send my Qubes backups there. > > > Hi Andrew, just to confirm my understanding... > > You put your Qubes backups on a standalone VM which has Crashplan > installed so these backups can be selected as files and stored offsite on > another machine? > > > > > Correct. > > > > > > I installed it twice, once on the template so the service would start > and run, and also on the VM so that the client side would be persistent. > Used the default options both times. It works. > > > > Vincent > > > > Yes, that's certainly another way to do it. I didn't want it installed in > any of my templates, so I opted for a StandaloneVM. Whichever you prefer is > fine. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJYEoDcAAoJENtN07w5UDAwc3sP/iQigEMpz80WTvpMo+GJL3rV > 8K3ZJ+L1dpsXZKyl9Uyexdtkx8YKGqk6kniq/1pQoikcimU+jN9RESBeO6ra3q5Y > hoS8Gqtdr4N61Grv7MNEJrB05ieMV6BFsKdAv+L568r3s9yKh28cNyq00KVWJf75 > Aoq8AFj06O/cyhUgDdk2MQsPiVCSmVia38+LQ91N8epej+t/tkvvQk155PkxQYUZ > IMczEuDkJf6Ao00PyUo5fCq+kKVAa1/F6soXRUepzMBj56yLs4NmHUwVt3Po1QGg > ruYmiWrxN5V/ghUlmFC2j8cxzgvhcjWIVayDmTcCuLQaTM2l5sh4eSjCzIindBXM > RTD8Xc0/4C0CkVjNJi7gIv9fLxBZqAkb+2NBYj4y+B5NLEUPY2PMWeFQOS0uP2xT > 8pDNKma3v324TfiZh1UqZA9A0o2ZCO0H8DaSoWZ/dYs3DDYCALmSIlAckCiSOaQ9 > ucjFGpTEoY72lEgLtwDzUC4NiGffeZQ/hz/eqDIsXHCVF89v36urSAE+kQeXatp0 > B2feCJEQMn3bmioA4KWXIO7qmYX/mW+SR79sEg921ajqSgYSgqCgnO84ZdkAsa6C > NgtiBYsY07sCalAZUbD6jALyxcrnp2XnwjfL3FwrXKzhMNBtyNgQC8xzWm1snFCg > 9MIKNLs4HlF2ovgSQZkl > =yxsH > -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/CANNetsMWR1_7OkfxO3SK8SxVNPdaydbStSVNgrea9oiHgbY5%2BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] 3.2 Install: Error unpacking qubes-template-fedora-23
I can confirm that error under certain circumstances. If I write the ISO (checked via Sha256+GPG) with Rufus from Windows 10, I get the exact same error under multiple computers with totally different hardware. If I write it on my USB drive with dd under Fedora 24, it works without any errors. Used the same hardware to write the same iso onto the same usb drive, just once with Win10 and once with Fedora. Maybe you try it this way aswell if you didnt already found another solution. -Fabian -- 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/1580b3f36d0.275d.db864a7b1d5e2becb017b42ae5cd9fc6%40posteo.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Dobrý den,
Dobrý den, Při vší úctě, jsem Barr.Garrick Moore, od Togo, západní Afrika. Jsem právník z povolání. Já jsem Vás kontaktovat o pozdních fondů Engr.Paulo uložených v jednom z našich bank zde předtím, než zemřel, takže Laskavě dostat zpět ke mně pro více informací přes můj soukromý e-mail garrickmoore6...@gmail.com S přátelským pozdravem, Barr. Garrick Moore. -- 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/CAPG1jBQLJUn9ASaTJUaRVDL-v9H1kupmJf3%2BgVdKoOjORhU8ig%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 28, 2016 at 12:56:28PM +0200, Zrubi wrote: > On 10/28/2016 11:44 AM, Marek Marczykowski-Górecki wrote: > > > Or maybe > > it's still at 3.1 there (and the updated one saved in .rpmnew file)? > > That was the case. > My templates are updated to fc24 now. > > A few notes about this: > > - skipping the template upgrade from 3.1 has no immediate visible > effect, easy to forget. This is somehow intended effect - we try to not break compatibility (that much) between 3.x releases. But indeed some warning would be nice. > - the /etc/yum.repos.d/qubes-r3.repo file hardcoded to Qubes versions, > and the upgrade not overwriting it if you made any change (enable more > repos for example) Ideally we'd have some variable for Qubes version there, but unfortunately there is only one $releasever and it's about Fedora release number... > - the short upgrade path (You discribed before) is working fine :) :) - -- 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 iQEcBAEBCAAGBQJYEzW1AAoJENuP0xzK19cs/1gH/3Pwm2xczqc199X1Wgtzja7B wQaXMO4XnGSl/hwcUEXrm1puZC4374aW95xWbkE9tbsQxP8BEbIOGNUBxLtqLfe0 TyDBdeF+lp6FBHsxvIEKmm8f6DBzvVNvfPJQ0OgMKQfazVe8Js5jVNjOMC8gkQuH tr4ctNzejltFYDBjsR/Q7z21agoJrtbZh+oAvYQc7aSSDooz6tbibrcq6mNIpy1U rJv+uZlRwIekmgLbZEmLzQ4kX1ZB6cdX+iNTY5OtBwpaDkQRO4h4jVhCFAW7Cmn2 MGSHMxUvJpXtCw6/mkBN2f4e2cV0DCJDt7dIJw1rLHJ0+TpdTfn7PJjA54YTPw4= =5P1Q -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/20161028112541.GL7073%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Display Calibration and Audio Equalizer for Dom0 ?
On 09/03/2016 12:49 AM, Connor Page wrote: > I have calibrated my yellow screen using argyllcms. > I don't attach usb devices to dom0 so installed it in sys-usb as well. > used > https://encrypted.pcode.nl/blog/2013/11/24/display-color-profiling-on-linux/ > as a rough guide. > to get the calibration done you just need to run dispcal and then transfer > the calibration file to dom0. > then test it with "dispwin xxx.cal" in dom0. if happy, create an autostart > item with that command (probably, > using the full path to the calibration file) and you're done. I just started to experiment with display color correction things. I wonder how it is workig in Qubes because as far as i know: - the display profile is used only the programs are aware of icc profiles. - the X server runs in dom0, the apps are in AppVMs - but no communication about display prifiles (colord) because of the qubes gui protocol. > I went further and created an icc profile for use in firefox and photo > software. If no colord is runnin in an appvm, how they apply your prifile then? You just manually configure all of the icc profile aware apps?? Can you please describe in more details what and how you achieved? Thanks. -- Zrubi -- 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/6fbdc9bc-dc48-8a25-ecd5-9686b62800ce%40zrubi.hu. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Re: How to view Youtube in Fullscreen ? (for dummies)
On 10/27/2016 01:31 AM, raahe...@gmail.com wrote: > On Wednesday, October 26, 2016 at 5:15:53 PM UTC-4, jamie wrote: >> does not matter if I use fedora, debian or whonix ... whenever I press >> fullscreen on any youtube video the brower freezes.. >> >> it also does not matter which browser I use firefox, chromium,... >> all of them freeze. I can confirm this issue. It's not that they freeze, they continue to run and you can see window updates when you resize the window, but it's simply that they stop updating after hitting that damn fullscreen button. This is a new bug and I recommend you file a ticket in https://github.com/QubesOS/qubes-issues/new . >> >> >> how to watch youtube videos 'for dummies' in fullscreen ? >> how to enable fullscreen mode 'for dummies' in my fedora appVM ? > hmm I've only had the issue on firefox, maybe related? > https://github.com/QubesOS/qubes-issues/issues/1502 > -- Rudd-O http://rudd-o.com/ -- 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/3e47b747-25e4-8254-f06a-f06abb947cac%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Crashplan?
On 06/26/2016 03:40 PM, Andrew David Wong wrote: > On 2016-06-26 04:27, Niels Kobschaetzki wrote: > > Hi, > > > does anyone have experiences with running Crashplan in Qubes? If > > yes, how did you install it? > > > Niels > > > I installed it in a StandaloneVM with the installer's default options. > > (As I'm guessing you've discovered, attempting to install it in an > AppVM with the default options doesn't allow it to persist across > reboots since it tries to install parts of itself to the read-only > root filesystem.) > There is a persist dirs option. Look for bind-dirs.sh in the qubes-core-agent-linux package. This should let certain directories persist for good in any AppVM (but, of course you don't want to do that for system dirs like /usr/bin and such). -- Rudd-O http://rudd-o.com/ -- 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/d2c28aca-8ac4-7954-07d2-6626ca344010%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Internal networking: How are IPs chosen, why class C subnet.
On 10/28/2016 08:51 AM, Robert Mittendorf wrote: > Hey, > > yesterday I noticed that even if VMs share a class C network, all > trafic is routed through the gateway and by default the gateway does > not allow a connection to other VMs in the same subnet. > This makes a lot of sense from a security perspective, but the shown > information is missleading. qubes-network-server does the right thing if you have a number of VMs with assigned static IPs. Traffic gets routed to the right VM. -- Rudd-O http://rudd-o.com/ -- 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/f2af19a4-7839-1a34-41e6-f57bf19b2cad%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
On 10/28/2016 09:40 AM, Marek Marczykowski-Górecki wrote: > > Actually yes, we may hook qubes-gui-agent.service into graphical.target > and call it "display manager", preventing others from running. This is > good idea, but something I'd like to avoid as a stable update - so, for > Qubes 4.0. Yes, this would be a good start. > >> I believe the correct thing to do is to create the necessary >> configuration for the default display manager to start qubes-guid with >> autologin. This will also give us a complete desktop session inside the >> VM, > This is exactly what we want to avoid. We don't want another window > manager there (which would be fighting with the one in dom0), as well as > a ton of other useless things like panels, clock icons etc. Excluding > this crap makes Qubes VMs lightweight enough to run 20+ of them at the > same machine. I was not suggesting you run a window manager. Just a qubes-guid session. No window manager whatsoever. Certainly not clocks, or panels, or any of that shit. -- Rudd-O http://rudd-o.com/ -- 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/68bd52bc-ad96-f342-0989-869fbc97fb6c%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: ANN: git-remote-qubes: Inter-VM Git for Qubes OS
On 10/28/2016 10:51 AM, cyrinux wrote: > Le jeudi 27 octobre 2016 13:47:14 UTC+2, Manuel Amador (Rudd-O) a écrit : >> It gives me great pleasure to announce the inter-VM Git bridge for Qubes >> OS, which allows you to git push and git pull from VMs stored in other >> repos, with no networking involved whatsoever, and observing full >> compliance with Qubes OS qrexec policy. >> >> This should usher in a new era of software development that allows >> people to segregate their secure Git repos from insecure build VMs and >> other engineering constructs I can't even think of (after doing >> low-level socket programming for a week, which has left my brain utterly >> fried). >> >> Find the software at https://github.com/Rudd-O/git-remote-qubes >> >> --- >> >> # Inter-VM Git for Qubes OS >> >> This is a very simple Git protocol bridge between Qubes OS VMs. With it, >> you can `git pull` and `git push` between VMs without having to grant >> any of the VMs any special policy privileges other than access to Git. >> >> ## Using the software >> >> These instructions assume you have installed the software. See the >> *Installing the software* heading below for more information. >> >> ### Creating a repository >> >> We'll assume for illustration purposes that you want to access a repository >> stored in `/home/user/xyz` on your VM `servervm`. >> >> Run the following commands on `servervm`: >> >> ``` >> cd /home/user >> mkdir -p xyz >> cd xyz >> git --bare init >> ``` >> >> That's it. Your new and empty repository is ready to use. >> >> ### Adding a remote to a local repository >> >> For illustration purposes, you'll be pushing and pulling `servervm`'s `xyz` >> repo on your vm `clientvm`. Run the following commands on `clientvm`: >> >> ``` >> cd /home/user >> git clone qubes://clientvm/home/user/xyz >> ``` >> >> You will get a permission dialog from dom0 asking for `ruddo.Git` access. >> Accept it. Note that accepting the permission dialog implicitly gives >> Git access to all Git repos stored in `servervm`, but only for that one >> execution (unless you say *Yes to all*, in which case the permission >> is remembered within the policy file that you installed earlier with the >> `dom0` package). >> >> This should have cloned `xyz` from `servervm` into your `/home/user/xyz` >> directory in `clientvm`. >> >> From this point on, you can push and pull in `clientvm` from >> `servervm:/home/user/xyz` to your heart's content. >> >> If, instead of cloning, you have an existing repo, you can add a new remote >> just as easily: >> >> ``` >> cd /home/user/existingxyz >> git remote add qubesremotevm qubes://servervm/home/user/xyz >> ``` >> >> That addition will enable to push and pull from the remote `qubesremotevm` >> which represents the repo `/home/user/xyz` in the remote VM `servervm`. >> >> ## Installing the software >> >> There are two components for this software: >> >> * Component 1 is the VM side of things, which implements the Git protocol >> across VMs. >> * Component 2 is the dom0 side of things, which is a simple text file >> declaring >> the initial Git access policy for your VMs. >> >> First, build the software, After cloning this repository on a suitable VM, >> run the command: >> >> ``` >> make rpm >> ``` >> >> This will generate two installable packages on the local directory: >> >> * `git-remote-qubes-.noarch.rpm`, which contains the Git >> protocol implementation. >> * `git-remote-qubes-dom0-.noarch.rpm`, which contains the >> default policy. >> >> Copy the `git-remote-qubes-.noarch.rpm` file to the template VM >> or standalone VM where you plan to pull or push to / from a Git repo >> stored in another Qubes VM. Install the RPM with >> `dnf install `. At this point, this VM, as well as >> any VMs using this as a template, have gained the ability to push and pull >> from Git repos stored in other VMs, as well as the ability to listen on >> push / pull requests from different VMs in the same system. >> >> Now copy the `git-remote-qubes-dom0-.noarch.rpm` file to >> your dom0. At this point, the default policy (`deny`) is active on >> your Qubes OS system, and you can begin pushing and pulling. >> >> Those clever among you will have discovered that there is a `Makefile` >> included, and that you can use the `Makefile` to install the software on >> other non-RPM templates. I welcome pull requests to add support for >> other distro packages and Qubes OS templates. >> >> ## Troubleshooting and debugging >> >> If you are experiencing problems communicating with a Git repo in a VM, >> export the variable `QUBES_DEBUG` on the side of your client (where your >> local Git repo is), and look at the debugging output that appears. >> >> As always, you can file new issues on the repo of this project for help >> with fixing bugs that the programs may have. Pull requests also welcome. >> >> -- >> Rudd-O >> http://rudd-o.com/ > I installed it yestarday, no problem,
Re: [qubes-users] Re: Introducing the qubes-announce read-only mailing list
On 10/28/2016 12:32 PM, Manuel Amador (Rudd-O) wrote: > Forgive me for asking this: > > Anyone else beginning to get annoyed with Drew's constant participation > that contributes nothing of value, and in fact often detracts from the > value of the mailing list? > > I don't want to be mean, but it's like we have our own Ken M in this > mailing list, and it is Drew. Yes, He is really annoying. I just ignoring all the posts from him (and maybe whole threads) for a while. Not easy for me - but nothing you can do about such issues. -- Zrubi -- 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/c072fd02-960d-878c-1e53-52de87525f34%40zrubi.hu. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: Request for test: Re: [qubes-users] Fedora 24?
On 10/28/2016 11:44 AM, Marek Marczykowski-Górecki wrote: > Or maybe > it's still at 3.1 there (and the updated one saved in .rpmnew file)? That was the case. My templates are updated to fc24 now. A few notes about this: - skipping the template upgrade from 3.1 has no immediate visible effect, easy to forget. - the /etc/yum.repos.d/qubes-r3.repo file hardcoded to Qubes versions, and the upgrade not overwriting it if you made any change (enable more repos for example) - the short upgrade path (You discribed before) is working fine :) Thanks for the fast response :) -- Zrubi -- 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/b9b075a2-c1dd-dbf5-aff3-eca047148770%40zrubi.hu. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Re: ANN: git-remote-qubes: Inter-VM Git for Qubes OS
Le jeudi 27 octobre 2016 13:47:14 UTC+2, Manuel Amador (Rudd-O) a écrit : > It gives me great pleasure to announce the inter-VM Git bridge for Qubes > OS, which allows you to git push and git pull from VMs stored in other > repos, with no networking involved whatsoever, and observing full > compliance with Qubes OS qrexec policy. > > This should usher in a new era of software development that allows > people to segregate their secure Git repos from insecure build VMs and > other engineering constructs I can't even think of (after doing > low-level socket programming for a week, which has left my brain utterly > fried). > > Find the software at https://github.com/Rudd-O/git-remote-qubes > > --- > > # Inter-VM Git for Qubes OS > > This is a very simple Git protocol bridge between Qubes OS VMs. With it, > you can `git pull` and `git push` between VMs without having to grant > any of the VMs any special policy privileges other than access to Git. > > ## Using the software > > These instructions assume you have installed the software. See the > *Installing the software* heading below for more information. > > ### Creating a repository > > We'll assume for illustration purposes that you want to access a repository > stored in `/home/user/xyz` on your VM `servervm`. > > Run the following commands on `servervm`: > > ``` > cd /home/user > mkdir -p xyz > cd xyz > git --bare init > ``` > > That's it. Your new and empty repository is ready to use. > > ### Adding a remote to a local repository > > For illustration purposes, you'll be pushing and pulling `servervm`'s `xyz` > repo on your vm `clientvm`. Run the following commands on `clientvm`: > > ``` > cd /home/user > git clone qubes://clientvm/home/user/xyz > ``` > > You will get a permission dialog from dom0 asking for `ruddo.Git` access. > Accept it. Note that accepting the permission dialog implicitly gives > Git access to all Git repos stored in `servervm`, but only for that one > execution (unless you say *Yes to all*, in which case the permission > is remembered within the policy file that you installed earlier with the > `dom0` package). > > This should have cloned `xyz` from `servervm` into your `/home/user/xyz` > directory in `clientvm`. > > From this point on, you can push and pull in `clientvm` from > `servervm:/home/user/xyz` to your heart's content. > > If, instead of cloning, you have an existing repo, you can add a new remote > just as easily: > > ``` > cd /home/user/existingxyz > git remote add qubesremotevm qubes://servervm/home/user/xyz > ``` > > That addition will enable to push and pull from the remote `qubesremotevm` > which represents the repo `/home/user/xyz` in the remote VM `servervm`. > > ## Installing the software > > There are two components for this software: > > * Component 1 is the VM side of things, which implements the Git protocol > across VMs. > * Component 2 is the dom0 side of things, which is a simple text file > declaring > the initial Git access policy for your VMs. > > First, build the software, After cloning this repository on a suitable VM, > run the command: > > ``` > make rpm > ``` > > This will generate two installable packages on the local directory: > > * `git-remote-qubes-.noarch.rpm`, which contains the Git > protocol implementation. > * `git-remote-qubes-dom0-.noarch.rpm`, which contains the > default policy. > > Copy the `git-remote-qubes-.noarch.rpm` file to the template VM > or standalone VM where you plan to pull or push to / from a Git repo > stored in another Qubes VM. Install the RPM with > `dnf install `. At this point, this VM, as well as > any VMs using this as a template, have gained the ability to push and pull > from Git repos stored in other VMs, as well as the ability to listen on > push / pull requests from different VMs in the same system. > > Now copy the `git-remote-qubes-dom0-.noarch.rpm` file to > your dom0. At this point, the default policy (`deny`) is active on > your Qubes OS system, and you can begin pushing and pulling. > > Those clever among you will have discovered that there is a `Makefile` > included, and that you can use the `Makefile` to install the software on > other non-RPM templates. I welcome pull requests to add support for > other distro packages and Qubes OS templates. > > ## Troubleshooting and debugging > > If you are experiencing problems communicating with a Git repo in a VM, > export the variable `QUBES_DEBUG` on the side of your client (where your > local Git repo is), and look at the debugging output that appears. > > As always, you can file new issues on the repo of this project for help > with fixing bugs that the programs may have. Pull requests also welcome. > > -- > Rudd-O > http://rudd-o.com/ I installed it yestarday, no problem, documentation is clear, well done yet :) -- You received this message because you are subscribed to the Google Groups "qubes-users" group.
Re: [qubes-users] Re: Introducing the qubes-announce read-only mailing list
On 10/28/2016 05:02 AM, Achim Patzner wrote: > Am 28.10.2016 um 02:00 schrieb Drew White: >> On Friday, 28 October 2016 10:57:03 UTC+11, Andrew David Wong wrote: >> We've just introduced a new mailing list: qubes-announce >>> So it's a forum, not a mailing list > > No, darling. It's a mailing liist. The contents are transferred to > registered users by mail and only those subscribed will receive it. The > contents are distributed by SMTP. The link he sent is an explanation > page on a web server. > > Don't pretend to be dumber than you are, it doesn't make you look better. > > > Achim > Forgive me for asking this: Anyone else beginning to get annoyed with Drew's constant participation that contributes nothing of value, and in fact often detracts from the value of the mailing list? I don't want to be mean, but it's like we have our own Ken M in this mailing list, and it is Drew. -- Rudd-O http://rudd-o.com/ -- 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/7bc77a5f-d86c-249f-6153-c7083568fce4%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Introducing the qubes-announce read-only mailing list
On Thursday, October 27, 2016 at 8:00:34 PM UTC-4, Drew White wrote: > > So it's a forum, not a mailing list its a mailing list that happens to have a forum interface. kinda like nntp but the other way around. -- 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/db60b315-5635-4682-a399-03da08cf9e60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 28, 2016 at 11:37:02AM +0200, Laszlo Zrubecz wrote: > On 10/28/2016 11:20 AM, Marek Marczykowski-Górecki wrote: > > > It looks so... See here: > > https://www.qubes-os.org/doc/upgrade-to-r3.2/#upgrade-all-template-and-standalone-vms > > It was not made a difference - only the package versions changed, the > error is the same. > > so I'm still stucked with broken dependencies :( Interesting. Check qubes repositories definitions. /etc/yum.repos.d/qubes-r3.repo should look like this: [qubes-vm-r3.2-current] name = Qubes OS Repository for VM (updates) baseurl = http://yum.qubes-os.org/r3.2/current/vm/fc$releasever gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3-primary skip_if_unavailable=False gpgcheck = 1 enabled=1 [qubes-vm-r3.2-current-testing] name = Qubes OS Repository for VM (updates-testing) baseurl = http://yum.qubes-os.org/r3.2/current-testing/vm/fc$releasever gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3-primary skip_if_unavailable=False gpgcheck = 1 enabled=0 [qubes-vm-r3.2-security-testing] name = Qubes OS Repository for VM (security-testing) baseurl = http://yum.qubes-os.org/r3.2/security-testing/vm/fc$releasever gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3-primary skip_if_unavailable=False gpgcheck = 1 enabled=0 [qubes-vm-r3.2-unstable] name = Qubes OS Repository for VM (unstable) baseurl = http://yum.qubes-os.org/r3.2/unstable/vm/fc$releasever gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3-unstable gpgcheck = 1 enabled=0 Especially "fc$releasever" part is important. Maybe you have hardcoded "23" there for some reason? Or have the repository disabled? Or maybe it's still at 3.1 there (and the updated one saved in .rpmnew file)? - -- 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 iQEcBAEBCAAGBQJYEx3pAAoJENuP0xzK19csMY4H/jVMeRDhv8BV7Z/Kmw59o94Y ZtaondXxCwQzeuqIXPp8UD0bxscBbduOadl+ARwNH3Xnvgsa6GG6xVrvjsOWLqP2 R3JUxEVLtHq76x68m9XuBIosXSTkBQTRbZ/wR8WxrdY9xGlzIM8hHJ2pZRrY2Usn QYkxIoH29ty8a0ac62i292/ITR/xgKj7jt1gt0d7olXagE+xlSwdTqV/Vd7qHWRA a/Tv4gMIcauNN9Y4cwXBrYIZv8HFLchId0L4jvgZ03X02h43HOVUJqSZ+lcNfS9I vNcfN/sBuaeiG3nKDiW3bZq5noRVENOcEszuJd36g27NLiBEkjPur+SIuZvTg6c= =DFlG -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/20161028094409.GI7073%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 28, 2016 at 09:28:31AM +, Manuel Amador (Rudd-O) wrote: > On 10/28/2016 01:56 AM, Marek Marczykowski-Górecki wrote: > > On Thu, Oct 27, 2016 at 03:31:46PM +0200, Marek Marczykowski-Górecki > > wrote: > > > On Thu, Oct 27, 2016 at 09:50:56AM +0200, Zrubi wrote: > > >> On 09/06/2016 01:24 AM, Marek Marczykowski-Górecki wrote: > > >> > > >>> I've just tried this and successfully upgraded Fedora 23 to Fedora 24 > > >>> template. > > >>> > > >>> TL;DR version: > > >>> 1. Clone fedora-23 to fedora-24-test. > > >>> 2. Open terminal in fedora-24-test. > > >>> 3. Run "dnf upgrade --releasever=24". > > >>> 4. Shutdown the template. > > >>> 5. Switch (some of?) VMs to this template. > > >>> > > >> > > >> Just tried to upgrade my templates and got this error: > > >> > > >> > > >> Error: Transaction check error: > > >> file /usr/lib64/libpython3.so from install of > > >> system-python-libs-3.5.1-17.fc24.x86_64 conflicts with file from > > package > > >> python3-libs-3.4.3-12.fc23.x86_64 > > >> > > >> > > >> Was not able to workaround it, because(?) those libs are used by dnf > > >> itself :o > > >> > > >> The official fedora upgrade way: > > >> https://fedoraproject.org/wiki/DNF_system_upgrade > > >> seems not compatible with Qubes > > >> > > >> > > >> any hints how to solve this? > > > > > I haven't tried recently, but it worked before. Maybe a workaround would > > > be to disable "updates" repository for the upgrade time? Just add > > > --disablerepo=updates. > > > > Or another idea: use `dnf distro-sync --releasever=24`, instead of `dnf > > upgrade`. Not sure if that helps. > > > > > I think it may be possible to use "official" upgrade method, by > > > switching to pvgrub first: > > > > > https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm > > > But in practice probably it will be more complex than just following > > > that instructions... Maybe worth a try? > > > > Actually, it looks like it almost works this way, even without switching > > to pvgrub. The only problem is that we put "3" on kernel cmdline, which > > forces systemd going into multi-user.target (instead of > > system-update.target). This can be worked around by putting > > "systemd.unit=system-update.target" on the template kernel command line > > ("kernelopts" property) before starting second phase of the upgrade. > > We should not be putting 3 in the kernel command line, and we should not > be modifying the default target in qubes-core-vm-systemd either. What > we should do is do the necessary work to get the default system > configuration to work when we boot a VM into graphical.target (the > default). That way we avoid these integration issues. Actually yes, we may hook qubes-gui-agent.service into graphical.target and call it "display manager", preventing others from running. This is good idea, but something I'd like to avoid as a stable update - so, for Qubes 4.0. > I believe the correct thing to do is to create the necessary > configuration for the default display manager to start qubes-guid with > autologin. This will also give us a complete desktop session inside the > VM, This is exactly what we want to avoid. We don't want another window manager there (which would be fighting with the one in dom0), as well as a ton of other useless things like panels, clock icons etc. Excluding this crap makes Qubes VMs lightweight enough to run 20+ of them at the same machine. > and XDG autostart as well, as opposed to just a tiny stub that > doesn't have e.g. password manager environment or GPG agent. > > This area is ripe for research, and it's time we matured in that > direction. Also noteworthy is that, with the move to Wayland, this sort > of work is very apropos. - -- 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 iQEcBAEBCAAGBQJYEx0UAAoJENuP0xzK19csoDkH/3rXbCEvgXE12IABaV18dldb PPEgp+6DrpEAuY56rhVQGHEo7QWUhSQzspotvs0UANirdVLiTFaIb3Q/Yv2uUPSZ RyHucDCu6bEcnBMDIDVX9jYvh3PZR8LdVMkKbQ1DdzMKDCCcjFU9bdwnUnVmdXVb hzy9W9BfWKIo8PzdJ/H9un6OqlGYR3RqtPOXD2hjO85yrmGjrC2MNi1OYh86s4EF o1DIwb7rDcMCA05b2RjiagucNprB64VGBo5RBh8ZW3cU1NMycViUG0yWEF2iqNGV AxfmrdWsyjSxC1d9Nhv45k5u2EruWKkCqjl9rxX6RLlzot+KgTU5h3e+te+l+lg= =w9P+ -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/20161028094037.GH7073%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
On 10/28/2016 11:20 AM, Marek Marczykowski-Górecki wrote: > It looks so... See here: > https://www.qubes-os.org/doc/upgrade-to-r3.2/#upgrade-all-template-and-standalone-vms It was not made a difference - only the package versions changed, the error is the same. so I'm still stucked with broken dependencies :( -- Laszlo Zrubecz -- 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/944e4b77-3f4f-64af-ba37-88d18caa04de%40zrubi.hu. For more options, visit https://groups.google.com/d/optout. [user@F24-Proxy ~]$ sudo dnf system-upgrade download --refresh --releasever=24 Error: package python3-dnf-plugins-qubes-hooks-3.2.11-1.fc23.x86_64 requires python(abi) = 3.4, but none of the providers can be installed. package qubes-db-3.2.1-1.fc23.x86_64 requires xen-libs >= 2001:4.6.1-20, but none of the providers can be installed. package qubes-gui-vm-3.2.6-1.fc23.x86_64 requires pulseaudio = 7.1, but none of the providers can be installed. package qubes-core-vm-3.2.11-1.fc23.x86_64 requires python3-dnf-plugins-qubes-hooks, but none of the providers can be installed. package qubes-core-vm-systemd-3.2.11-1.fc23.x86_64 requires qubes-core-vm, but none of the providers can be installed 0x8F0E7BC6.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: Request for test: Re: [qubes-users] Fedora 24?
On 10/28/2016 01:56 AM, Marek Marczykowski-Górecki wrote: > On Thu, Oct 27, 2016 at 03:31:46PM +0200, Marek Marczykowski-Górecki > wrote: > > On Thu, Oct 27, 2016 at 09:50:56AM +0200, Zrubi wrote: > >> On 09/06/2016 01:24 AM, Marek Marczykowski-Górecki wrote: > >> > >>> I've just tried this and successfully upgraded Fedora 23 to Fedora 24 > >>> template. > >>> > >>> TL;DR version: > >>> 1. Clone fedora-23 to fedora-24-test. > >>> 2. Open terminal in fedora-24-test. > >>> 3. Run "dnf upgrade --releasever=24". > >>> 4. Shutdown the template. > >>> 5. Switch (some of?) VMs to this template. > >>> > >> > >> Just tried to upgrade my templates and got this error: > >> > >> > >> Error: Transaction check error: > >> file /usr/lib64/libpython3.so from install of > >> system-python-libs-3.5.1-17.fc24.x86_64 conflicts with file from > package > >> python3-libs-3.4.3-12.fc23.x86_64 > >> > >> > >> Was not able to workaround it, because(?) those libs are used by dnf > >> itself :o > >> > >> The official fedora upgrade way: > >> https://fedoraproject.org/wiki/DNF_system_upgrade > >> seems not compatible with Qubes > >> > >> > >> any hints how to solve this? > > > I haven't tried recently, but it worked before. Maybe a workaround would > > be to disable "updates" repository for the upgrade time? Just add > > --disablerepo=updates. > > Or another idea: use `dnf distro-sync --releasever=24`, instead of `dnf > upgrade`. Not sure if that helps. > > > I think it may be possible to use "official" upgrade method, by > > switching to pvgrub first: > > > https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm > > But in practice probably it will be more complex than just following > > that instructions... Maybe worth a try? > > Actually, it looks like it almost works this way, even without switching > to pvgrub. The only problem is that we put "3" on kernel cmdline, which > forces systemd going into multi-user.target (instead of > system-update.target). This can be worked around by putting > "systemd.unit=system-update.target" on the template kernel command line > ("kernelopts" property) before starting second phase of the upgrade. We should not be putting 3 in the kernel command line, and we should not be modifying the default target in qubes-core-vm-systemd either. What we should do is do the necessary work to get the default system configuration to work when we boot a VM into graphical.target (the default). That way we avoid these integration issues. I believe the correct thing to do is to create the necessary configuration for the default display manager to start qubes-guid with autologin. This will also give us a complete desktop session inside the VM, and XDG autostart as well, as opposed to just a tiny stub that doesn't have e.g. password manager environment or GPG agent. This area is ripe for research, and it's time we matured in that direction. Also noteworthy is that, with the move to Wayland, this sort of work is very apropos. -- Rudd-O http://rudd-o.com/ -- 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/822d780c-e039-f80b-3808-c6c8e740ffa7%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Networking between two vms?
On 04/08/2016 02:17 PM, edev.u...@gmail.com wrote: > On Sunday, February 1, 2015 at 11:45:05 PM UTC-5, Marek Marczykowski-Górecki > wrote: > >> By default firewallvm blocks all the inter-vm traffic. But you can add a >> rule to allow that. Take a look here: >> https://wiki.qubes-os.org/wiki/QubesFirewall#EnablingnetworkingbetweentwoAppVMs > The above guide requires both VMs to be connected to the same firewall vm. > > I have a case when one vm is a proxyvm connected to a separate NIC via a > dedicated netvm and I want to connect the proxyvm to the default sys-firewall > vm. How can I enable networking between these two vms? > To enable transparent networking between VMs, you can also use: https://github.com/Rudd-O/qubes-network-server Just give your two VMs different IP addresses and they will work. Of course, the firewall rules still need to be set, if the VMs are attached to a ProxyVM. -- Rudd-O http://rudd-o.com/ -- 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/385f673c-f103-07e8-af90-3d70428d3645%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 28, 2016 at 10:51:43AM +0200, Zrubi wrote: > On 10/28/2016 10:46 AM, Marek Marczykowski-Górecki wrote: > > > Wait a sec, qubes-gui-vm-3.1.7 ? Is this Qubes 3.1? We don't have fc24 > > support there... > > Well no. It is Qubes 3.2 - but a restored template. > > Maybe I just messed up something related to 3.1 -> 3.2 upgrade? It looks so... See here: https://www.qubes-os.org/doc/upgrade-to-r3.2/#upgrade-all-template-and-standalone-vms - -- 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 iQEcBAEBCAAGBQJYExhCAAoJENuP0xzK19csgR4H/A2MIF9uxVpAq+WOf1ETGzAY u5fzU36/GtEpIUXfLelKGFyBujADToW0VHuhBFmoGJjiRRg6v9QFElOUkQojjfdd eRkVzQxNizKdYdCUErIJyEK0fWW6K60XYG2GcR5i5mqmojoOpa7XttBwNGggZcUU E/4Hw+WVC4VaiELbIfxvoWpaastgtbBM5PlAIv6OHb3P24osNNhxWoC81PT4d/aK 7pRTwkKv3T7TyoNbl1xbWipCD+ujakaXtWGyvAJtutORPAM2+/AJANdVEDEJx5ar zlWhvveUINIEM6/KdMCPOiRXDrQc8T3CJa//nAcz3zSUP7nZMa5abdL0fPfeJ4Q= =Lw7k -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/20161028092002.GG7073%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Windows HVM doesn't get updates
On 04/10/2016 11:34 PM, Salmiakki wrote: > Well, maybe. I haven't looked at traffic yet. Is there a simple way to > do that with qubes? sudo tcpdump -i eth0 -nn in the ProxyVM that your Windows VM is attached to. -- Rudd-O http://rudd-o.com/ -- 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/ef0825ab-29be-31a1-f382-538ac61a8d5a%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
On 10/28/2016 10:46 AM, Marek Marczykowski-Górecki wrote: > Wait a sec, qubes-gui-vm-3.1.7 ? Is this Qubes 3.1? We don't have fc24 > support there... Well no. It is Qubes 3.2 - but a restored template. Maybe I just messed up something related to 3.1 -> 3.2 upgrade? However to template is working fine. I'm using it for a while for production. -- Zrubi -- 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/6d28663d-3256-9940-ea6a-0ad700693a49%40zrubi.hu. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Internal networking: How are IPs chosen, why class C subnet.
Hey, yesterday I noticed that even if VMs share a class C network, all trafic is routed through the gateway and by default the gateway does not allow a connection to other VMs in the same subnet. This makes a lot of sense from a security perspective, but the shown information is missleading. With IP 10.137.x.y and class C subnet (255.255.255.0) one would expect to be able to communicate with IP 10.137.x.z directly. I guess this is just the preconfiguration of the templates and user-build template would be able to communicate directly when they are in the same network?! How are IPs chosen anyway? A class C-subnet "behind" every ProxyVM or NetVM? regards, Robert -- 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/c2fc5670-9d25-9f27-54fd-6171aa6a%40digitrace.de. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 28, 2016 at 10:32:12AM +0200, Zrubi wrote: > On 10/28/2016 10:06 AM, Zrubi wrote: > > On 10/27/2016 03:31 PM, Marek Marczykowski-Górecki wrote: > > > >> I haven't tried recently, but it worked before. Maybe a workaround would > >> be to disable "updates" repository for the upgrade time? Just add > >> --disablerepo=updates. > > > > I do not understand the reason - but it was worked this way - thanks. > > I just celebrated to early :( > > now it seems I'm running FC24 - but still have a lot of packages named: > *fc23* > including several qubes related. > > And if i try to update the system got the same dependency error as > before :( Also noticed that the update skipping several packages because > boken dependencies - see the attached file "b" > > distro-sync (and system-upgrade) also fails by broken dependencies - see > file "c" Wait a sec, qubes-gui-vm-3.1.7 ? Is this Qubes 3.1? We don't have fc24 support there... - -- 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 iQEcBAEBCAAGBQJYExBPAAoJENuP0xzK19csV+AH/ifcVnFxqZdeiYaY9n39YTJA 6vdpnV7r35lhriV4W0rb9eWceMkQLrRNGB7Omlo0cQBlCS4bFz+HiLvUEiPQBoO0 5vao4Id0OAsyviIVHijbK6leFrYrMoLqqo2JdT66ZBPAxwofVUx/zeecuBUOLF0U iNfjR5CPHmmGsko4AwQ5NqNUf0ZZeJ57aV/U5uHNs0Si9oph7qtPl2RABs46rJqb qeKsHC2SHlfI2AmYF6c3RS/3CgcZnUvnF+hXkN5UPZkdYiklizFjK86gRCv6jsId oFGxLac1CQEMQSicgfN74jb1d0pJe5bOwUo80ZDM5SPAe1dG55NW4sRMlcl0RU8= =MHGZ -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/20161028084607.GE7073%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] windows7 hangs on installation
How long did you wait? btw: "installed windows tools" is missleading. I guess you downloaded the QWT to dom0, as you did not even install windows before step 1. -- 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/82966e85-ad96-ce84-fa67-660ac12e93f4%40digitrace.de. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
On 10/28/2016 10:06 AM, Zrubi wrote: > On 10/27/2016 03:31 PM, Marek Marczykowski-Górecki wrote: > >> I haven't tried recently, but it worked before. Maybe a workaround would >> be to disable "updates" repository for the upgrade time? Just add >> --disablerepo=updates. > > I do not understand the reason - but it was worked this way - thanks. I just celebrated to early :( now it seems I'm running FC24 - but still have a lot of packages named: *fc23* including several qubes related. And if i try to update the system got the same dependency error as before :( Also noticed that the update skipping several packages because boken dependencies - see the attached file "b" distro-sync (and system-upgrade) also fails by broken dependencies - see file "c" -- Zrubi -- 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/35eaba28-7faf-d291-aa3f-d7b741a201a2%40zrubi.hu. For more options, visit https://groups.google.com/d/optout. Skipping packages with broken dependencies: dnfnoarch 1.1.10-1.fc24updates 276 k dnf-conf noarch 1.1.10-1.fc24updates 96 k dnf-plugin-system-upgrade noarch 0.7.1-2.fc24 fedora 49 k dnf-yumnoarch 1.1.10-1.fc24updates 79 k libcomps x86_64 0.1.7-4.fc24 fedora 75 k librepox86_64 1.7.18-2.fc24fedora 87 k pulseaudio x86_64 8.0-6.fc24 fedora 919 k pulseaudio-libsx86_64 8.0-6.fc24 fedora 586 k python3x86_64 3.5.1-17.fc24updates 57 k python3-dnfnoarch 1.1.10-1.fc24updates 452 k python3-dnf-plugin-system-upgrade noarch 0.7.1-2.fc24 fedora 31 k python3-iniparse noarch 0.4-19.fc24 fedora 46 k python3-libcomps x86_64 0.1.7-4.fc24 fedora 47 k python3-librepox86_64 1.7.18-2.fc24fedora 57 k python3-libs x86_64 3.5.1-17.fc24updates 1.3 M python3-pipnoarch 8.0.2-1.fc24 fedora 1.7 M python3-pygpgmex86_64 0.3-18.fc24 updates 90 k python3-setuptools noarch 20.1.1-1.fc24fedora 421 k python3-sixnoarch 1.10.0-2.fc24fedora 35 k python3-systemdx86_64 232-1.fc24 updates 70 k rpmx86_64 4.13.0-0.rc1.27.fc24 fedora 513 k rpm-build-libs x86_64 4.13.0-0.rc1.27.fc24 fedora 117 k rpm-libs
Re: [qubes-users] Net does not work
I have wired connection. DHCP connection with binding to the MAC-address. Problem solved actually. I disabled Whonix option when was installation of Qubes (i think it was cause) - and after that my default MAC in the Qubes was something like FE:FF:FF:FF:FF:FF. Thats why cloned MAC doesnt worked. After that i'm re-install Qubes (now i did not remove the Whonix) and default MAC after install become right and cloned MAC work! Changing of MAC i did in the icon, beside the clocks-icon (is it the Network Manager applet?). There was the one option with default MAC (FE:FF:FF:FF:FF:FF) Thanks for response! -- 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/55d8a559-78cc-4f49-9cac-715dced0e4b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for test: Re: [qubes-users] Fedora 24?
On 10/27/2016 03:31 PM, Marek Marczykowski-Górecki wrote: > I haven't tried recently, but it worked before. Maybe a workaround would > be to disable "updates" repository for the upgrade time? Just add > --disablerepo=updates. I do not understand the reason - but it was worked this way - thanks. -- Zrubi -- 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/7e387590-84b9-bcfd-45e2-b56a4f11a058%40zrubi.hu. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature