[qubes-users] dispvms saving its sessions?
I just saw that in the directory containing my default dvm (/var/lib/qubes/appvms/whonix-ws-ws-dvm/) contains alot of files named like this: disp1.conf disp2.conf disp3.conf And it keeps going on for a while, but I cannot seem to discover where they are coming from, since creating new and restarting the dvms does not solve it. Is this normal behavior, or is this some weird configuration issue? -- 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/c2bab838-2692-4a83-94a9-663c0d9dc685%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Local network access when using ProxyVM as VPN gateway using iptables and CLI scripts?
On 11/16/2017 08:11 AM, Chris Laprise wrote: > On 11/15/2017 10:17 PM, Michael Siepmann wrote: >> >> I've followed the instructions to "Set up a ProxyVM as a VPN gateway >> using iptables and CLI scripts" at https://www.qubes-os.org/doc/vpn/ >> and it's working well so far but I need to be able to access my local >> network 192.168.x.x. That worked when I was connecting to the VPN >> with Network Manager in my NetVM. Is there a way to configure that >> when using a ProxyVM as a VPN gateway? I'm guessing I need to do >> something in /rw/config/qubes-firewall-user-script in my VPN ProxyVM >> to configure iptables to allow bypassing the VPN for 192.168.x.x but >> I'm not sure how to do that. Any help will be greatly appreciated! >> > > Hi Michael, > > You're not the first to ask about LAN access via a VPN VM. Various > posters in qubes-users have found ways around the anti-leak > configuration to access particular nets directly. > > What I usually advise is to think of VPN proxy, sys-firewall or any > other proxyVM as Qubes network primitives: Let the VPN VM do its thing > in guarding against non-tunnel access, and use sys-firewall or > specific proxyVM to access the LAN. This implies that any given appVM > can have access to only one type of network (or, only one type at a > time). This IMHO is the best way. > > OTOH, yes you can make the compromise in the VPN VM and allow > non-tunnel traffic. In the firewall script, you can start by > commenting-out these two lines: > > iptables -I FORWARD -o eth0 -j DROP > iptables -I FORWARD -i eth0 -j DROP > > This removes almost all leak protection, but should suffice for > initial testing. You may also have to add a route pointing to your > local net (see Linux "ip route" documentation) because the VPN may > have added its route as a default. If you wish to eventually reinstate > the above anti-leak rules you can try adding exceptions after those > two (so they will be listed _first_ in the FORWARD chain), for instance: > > iptables -I FORWARD -o eth0 -d 192.168.0.0/16 -j ACCEPT > iptables -I FORWARD -i eth0 -s 192.168.0.0/16 -j ACCEPT > > A word of caution: Once you start modifying rules like this its easy > to make mistakes that compromise security, even if you generally know > what you're doing. That's one reason to use the Qubes-oriented net > security model I mentioned initially. Another reason is, of course, > that even creating correct exceptions to tunnel enforcement opens you > up to certain kinds of threats. If your use case does not call for an > appVM accessing both VPN and LAN at the same time then there should be > no reason to make the compromise. > Hi Chris, Thank you! I will try this and report back. My main use case here is automatically doing an encrypted backup (with Borg Backup) of my files once an hour to a NAS device, which in turn automatically copies the backups to cloud storage at night, when I don't have competing needs for the upload bandwidth. Another use case is file sync, e.g. with SyncThing (which can work over the Internet, but much slower of course). However, I can certainly see the security advantages of only letting an appVM have access to one type of network, or only one type at a time. -- 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/e80071ff-f740-4de7-25a1-89ddf0798647%40TechDesignPsych.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] HCL - Razer Blade Stealth (Late 2016 Model)
How did you install in UEFI mode? Mine will show a terminal with some text for less than 1 second and turn back to the installation menu. Secure boot is disabled. The far I get is the first menu that appears -- 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/ba2a8b81-2a58-4b22-aa44-ad4ae478adab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How To Fix Libvirt Internal Error
Should I update libvirt, install new drivers, or reinstall the hypervisor? -- 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/59d96b89-dcb5-4719-a762-4297ab0cc70a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How To Fix Libvirt Internal Error
Whenever I try to attach an ISO to a VM, I receive an error: “internal error: libxenlight failed to create new domain”. I have tried running different commands on Qubes. Disabling AppArmor doesn’t work, and starting xendriverdomain.service doesn’t work, because it’s not even installed. Some suggest getting xen-hvm-stubdom-linux (or they call it vmm-xen-stubdom-linux), but I don’t even know how to get it. I’ve tried downgrading libvirt, but all my packages are already at the lowest possible level. -- 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/b085d7b8-f994-41ad-a281-32a4b21362d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes RC2 updated, and no vms starting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Nov 16, 2017 at 04:07:29PM -0800, linuxcomputer...@gmail.com wrote: > I did sudo lvs and saw this: > vm-debian-8-private-snap > vm-debian-8-private-tmp > What should i do? Same with fedora VM Did your system crashed during debian-8 shutdown? Anyway try this: sudo lvrename qubes_dom0 vm-debian-8-private-tmp vm-debian-8-private Try similar thing with fedora-25-root (look for fedora-25-root-tmp). Then, lets try to find the root cause. Search sudo journalctl -u qubesd for things about fedora-25-root (and debian-8-private). - -- 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 iQEcBAEBCAAGBQJaDiprAAoJENuP0xzK19csJe4H/3hYpwiwwMfGLxff0lzYDgLy u0GbVS20SP0iqwOCBVzUcymjEiUKIHcxJc0JLqf+/7JrUe+I7jXyNRA9bvNvvhmb c8xIMA5MqiLhA/+yE0T07E+UIxEzsWmKFdhJD1hTKd0B/Fn0Zep199U+2QDU6gPU eNzKoqiY90aFZikmAHDqNXg6wlGUEkVShOTTXOWfVJlff4dQZ3tVphV1hQhD6JfX 2o6u8rLs7d34IyzYBE9y0jEsPTG1SA+BLaDRm7OZftMhycO4h0+ZKa6J/cMBtN1z KvK7aeHWcsf9N43YqmTwhKoemtw5MCtS+T23u3UFrcj6mjEPKIKwxfbeqSZwokk= =CCWB -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/20171117001640.GB2450%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes RC2 updated, and no vms starting
I did sudo lvs and saw this: vm-debian-8-private-snap vm-debian-8-private-tmp What should i do? Same with fedora VM -- 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/8f1fa655-c300-41c7-b32e-66b543c32df4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes RC2 updated, and no vms starting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Nov 16, 2017 at 01:58:46PM -0800, linuxcomputer...@gmail.com wrote: > I have already changed templates two debian and i get this: > RESULT: volume qubes_dom0/vm-debian-8-private missing > What should i do? I need to fix this asap Check `sudo lvs` to see what volumes are there. Do you see vm-debian-8-private (or this with some suffix)? - -- 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 iQEcBAEBCAAGBQJaDid7AAoJENuP0xzK19csEZQH/3uKL8C2/52EXY4kiAjTcrw3 6RxbTTbN4+cjQsDSz4fwycJolp2pdAtwUWFlQsSVsdTxLYB+KUbl1vdD/VVOWmqZ OvBpmbNc9gsgHCuqOtTaCHxP6z+MFZ6tp83CZBWuoBy97HEv/NsoNmDjMTk0S8Ym Li9zt5MgOPw5zLgQMF0BGp4l5MYwz2tLyuDT5ltUYtJIn8KSBGAvtuhi9vYSK36t G4EZO37kOvt8hokuYLT2N/pdYNksTxIkG1fKdj6wl2D0JR5kBrbvJQw1pZEiFPBw cyZHt2KVC+nHnIl3Eatw+RZSaRrgK+rqOOYXlG9t2jRiaI71mzJZK9s1c2Y12Ak= =QvVu -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/20171117000408.GA2450%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes RC2 updated, and no vms starting
I have already changed templates two debian and i get this: RESULT: volume qubes_dom0/vm-debian-8-private missing What should i do? I need to fix this asap -- 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/8e05cc3e-d884-4316-b10c-b2df0d6cf40e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes RC2 updated, and no vms starting
I have already tried changing templates two debian, still not starting and giving those errors. -- 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/4efffe3c-e785-40fe-a810-e1a4772137b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] When transferring file between Qubes, MD5 changes.
vegetarianst...@gmail.com: > I am transferring a windows ISO file between qubes.. however, the file's MD5 > sum changes every time I complete the transfer. > > Why might this be so? > Shouldn't be happening. I suspect faulty checksum tools in Windows. Use one of the following options: 1. (cmd.exe) CertUtil -hashfile SHA256 2. (PowerShell 4 or higher) Get-FileHash -Algorithm SHA256 Compare with `sha256sum` in Linux. -- 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/6feedb94-cd4f-445b-40aa-0903fe3b%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Ubuntu Template
On Thu, Nov 16, 2017 at 10:42:08AM +0100, rysiek wrote: > Hye, > > Dnia Tuesday, November 14, 2017 1:55:06 AM CET Unman pisze: > > I've just put in a couple of PRs to allow building for Xenial in 4.0. > > Are these the ones you're talking about? > https://github.com/QubesOS/qubes-gui-agent-linux/pull/23 > https://github.com/QubesOS/qubes-core-agent-linux/commit/ > 54867b6eabed3a6dca0e932ff77f67aedfe43e03 > > The latter is merged, I believe, and the former I applied manually. However, > while building, now I get: > > mkdir: cannot create directory ‘chroot-qubuntu’: File exists > mount: mount point chroot-qubuntu/tmp/qubes-deb does not exist > /home/qubes/qubes-builder/qubes-src/builder-debian/Makefile.qubuntu:275: > recipe for target 'update-repo-prepare' failed > make[1]: *** [update-repo-prepare] Error 32 > Makefile:297: recipe for target 'template-local-xenial' failed > make: *** [template-local-xenial] Error 1 > > Not sure where to dig now. > > More debug info below. The error message is self explanatory. Delete chroot-qubuntu and try to build 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/20171116195424.e3odvc5e5ved7kek%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] When transferring file between Qubes, MD5 changes.
On Wed, Nov 15, 2017 at 11:35:33PM -0800, vegetarianst...@gmail.com wrote: > I am transferring a windows ISO file between qubes.. however, the file's MD5 > sum changes every time I complete the transfer. > > Why might this be so? > Please identify the Qubes version, and which Templates you are using. On 3.2 with Debian templates (various) I have never seen this, and I religiously check iso images before using. I don't have a Windows iso to test with, but I cant imagine that makes any difference. Just in case though, can you test with some other iso image? Are the file sizes identical? unman -- 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/20171116195026.l454255hyb3aclcd%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: "Qubes" BOOT option DISAPPEARD in my Bios (thus I can't boot Qubes!), HOW TO BRING IT BACK?
It is strange that the boot section has been corrupted. After a quick search on google, I found this: https://www.qubes-os.org/doc/uefi-troubleshooting/ Maybe it can be helpful. Regards, L. G. -- 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/8d259cad-4352-49b1-bc65-d47ecfec41be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 backup of template VM fails - device out of space
I have a template VM im trying to back up which is rather larger, 185gb or so. Am attempting to backup to an external usb-connected sata drive with about half a terabyte of space on it. Less than 10% into the backup a failure message appears informing me that "device is out of space" where in reality the device has only had a small portion of it's 500GiB used. actual file size of backup after failure is only around 100MiB -- 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/95f0c6ff-179a-46bd-a981-74b2d181642d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] qubes 3.2 backup fails: device out of space
I have a template VM im trying to back up which is rather larger, 185gb or so. Am attempting to backup to an external usb-connected sata drive with about half a terabyte of space on it. Less than 10% into the backup a failure message appears informing me that "device is out of space" where in reality the device has only had a small portion of it's 500GiB used. actual file size of backup is only around 100MiB -- 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/06a5574d-80ba-4704-a441-b0df7c5c92c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Local network access when using ProxyVM as VPN gateway using iptables and CLI scripts?
On 11/15/2017 10:17 PM, Michael Siepmann wrote: I've followed the instructions to "Set up a ProxyVM as a VPN gateway using iptables and CLI scripts" at https://www.qubes-os.org/doc/vpn/ and it's working well so far but I need to be able to access my local network 192.168.x.x. That worked when I was connecting to the VPN with Network Manager in my NetVM. Is there a way to configure that when using a ProxyVM as a VPN gateway? I'm guessing I need to do something in /rw/config/qubes-firewall-user-script in my VPN ProxyVM to configure iptables to allow bypassing the VPN for 192.168.x.x but I'm not sure how to do that. Any help will be greatly appreciated! Hi Michael, You're not the first to ask about LAN access via a VPN VM. Various posters in qubes-users have found ways around the anti-leak configuration to access particular nets directly. What I usually advise is to think of VPN proxy, sys-firewall or any other proxyVM as Qubes network primitives: Let the VPN VM do its thing in guarding against non-tunnel access, and use sys-firewall or specific proxyVM to access the LAN. This implies that any given appVM can have access to only one type of network (or, only one type at a time). This IMHO is the best way. OTOH, yes you can make the compromise in the VPN VM and allow non-tunnel traffic. In the firewall script, you can start by commenting-out these two lines: iptables -I FORWARD -o eth0 -j DROP iptables -I FORWARD -i eth0 -j DROP This removes almost all leak protection, but should suffice for initial testing. You may also have to add a route pointing to your local net (see Linux "ip route" documentation) because the VPN may have added its route as a default. If you wish to eventually reinstate the above anti-leak rules you can try adding exceptions after those two (so they will be listed _first_ in the FORWARD chain), for instance: iptables -I FORWARD -o eth0 -d 192.168.0.0/16 -j ACCEPT iptables -I FORWARD -i eth0 -s 192.168.0.0/16 -j ACCEPT A word of caution: Once you start modifying rules like this its easy to make mistakes that compromise security, even if you generally know what you're doing. That's one reason to use the Qubes-oriented net security model I mentioned initially. Another reason is, of course, that even creating correct exceptions to tunnel enforcement opens you up to certain kinds of threats. If your use case does not call for an appVM accessing both VPN and LAN at the same time then there should be no reason to make the compromise. -- Chris Laprise, tas...@posteo.net https://github.com/tasket 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/e66f84c8-15f3-2965-ccb3-65b8d5742c4f%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Can't login to VM after upgrade to fedora 26
Hi, qubes-gui-vm needs to be rebuilt against the newer version of pulseaudio. This should be fixed as of commit 4cf2d11 in qubes-gui-agent-linux, but it looks like it still needs to be built and pushed to the repositories. Fixing this is important because --allowerasing is needed for some updates from Fedora 25 to Fedora 26 because of this upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1467060. Best, Daniel -- 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/2c624deb-e849-42ef-99c3-33139f42cf86%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] When transferring file between Qubes, MD5 changes.
Dnia Thursday, November 16, 2017 9:16:49 AM CET Chris Laprise pisze: > On 11/16/2017 02:35 AM, vegetarianst...@gmail.com wrote: > > I am transferring a windows ISO file between qubes.. however, the file's > > MD5 sum changes every time I complete the transfer. > > > > Why might this be so? > > It might be a bug? > > What version of Qubes? And what OS are the source & destination VMs? Is > the same mdsum program being using on both ends? Also, what if you transfer the file with the changed md5 back into the original VM? Does the md5 sum change back to what it was, or to something different yet? -- Pozdrawiam, Michał "rysiek" Woźniak Zmieniam klucz GPG :: http://rys.io/pl/147 GPG Key Transition :: http://rys.io/en/147 -- 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/1817646.1gal37gNey%40lapuntu. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part.
Re: [qubes-users] When transferring file between Qubes, MD5 changes.
On 11/16/2017 02:35 AM, vegetarianst...@gmail.com wrote: I am transferring a windows ISO file between qubes.. however, the file's MD5 sum changes every time I complete the transfer. Why might this be so? It might be a bug? What version of Qubes? And what OS are the source & destination VMs? Is the same mdsum program being using on both ends? -- Chris Laprise, tas...@posteo.net https://github.com/tasket 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/ec439c10-f808-23e5-c6ab-1759c692df42%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Ubuntu Template
Hye, Dnia Tuesday, November 14, 2017 1:55:06 AM CET Unman pisze: > I've just put in a couple of PRs to allow building for Xenial in 4.0. Are these the ones you're talking about? https://github.com/QubesOS/qubes-gui-agent-linux/pull/23 https://github.com/QubesOS/qubes-core-agent-linux/commit/ 54867b6eabed3a6dca0e932ff77f67aedfe43e03 The latter is merged, I believe, and the former I applied manually. However, while building, now I get: mkdir: cannot create directory ‘chroot-qubuntu’: File exists mount: mount point chroot-qubuntu/tmp/qubes-deb does not exist /home/qubes/qubes-builder/qubes-src/builder-debian/Makefile.qubuntu:275: recipe for target 'update-repo-prepare' failed make[1]: *** [update-repo-prepare] Error 32 Makefile:297: recipe for target 'template-local-xenial' failed make: *** [template-local-xenial] Error 1 Not sure where to dig now. More debug info below. -> Building meta-packages (debian) for xenial vm (logfile: build-logs/meta- packages-vm-xenial.log) ╔══ DEBUG ══ ║ Repo Variables ╠─── ║ SRC_DIR: qubes-src ║ CHROOT_DIR: /home/qubes/qubes-builder/chroot-xenial ║ CHROOT_REPO_DIR: chroot-qubuntu ║ CHROOT_DEBIAN_DIR: /home/qubes/qubes-builder/chroot-xenial// ║ BUILDER_REPO_DIR:/home/qubes/qubes-builder/qubes-packages-mirror-repo/ xenial ╠─── ║ Chroot Variables ╠─── ║ DIST_BUILD_DIR: /home/user ║ DIST_SRC: ║ DIST_SRC_DEBIAN_DIR: / ╠─── ║ Build Variables ╠─── ║ DEBIAN_PARSER: /home/qubes/qubes-builder/qubes-src/builder-debian// scripts/debian-parser ║ DEBIAN_PLUGIN_DIR: /home/qubes/qubes-builder/qubes-src/builder-debian/ ║ OUTPUT_DIR: pkgs/xenial ║ PACKAGE_LIST: ║ DISTRIBUTION:qubuntu ║ DIST:xenial ║ DEBIANVERSION: xenial ║ UPDATE_REPO: /home/qubes/qubes-builder/qubes-src/linux-template- builder/pkgs-for-template/xenial ║ REPO_SUFFIX: ║ DISTRIBUTION_CAP:Qubuntu ║ REPO_PROXY: ║ APT_GET_OPTIONS: ║ CHROOT_ENV: BACKEND_VMM=xen ╚═══ ╔══ DEBUG ══ ║ Repo Variables ╠─── ║ SRC_DIR: qubes-src ║ CHROOT_DIR: /home/qubes/qubes-builder/chroot-xenial ║ CHROOT_REPO_DIR: chroot-qubuntu ║ CHROOT_DEBIAN_DIR: /home/qubes/qubes-builder/chroot-xenial//debian-vm/ debian ║ BUILDER_REPO_DIR:/home/qubes/qubes-builder/qubes-packages-mirror-repo/ xenial ╠─── ║ Chroot Variables ╠─── ║ DIST_BUILD_DIR: /home/user ║ DIST_SRC: ║ DIST_SRC_DEBIAN_DIR: /debian-vm/debian ╠─── ║ Build Variables ╠─── ║ DEBIAN_PARSER: /home/qubes/qubes-builder/qubes-src/builder-debian// scripts/debian-parser ║ DEBIAN_PLUGIN_DIR: /home/qubes/qubes-builder/qubes-src/builder-debian/ ║ OUTPUT_DIR: pkgs/xenial ║ PACKAGE_LIST:debian-vm/debian ║ DISTRIBUTION:qubuntu ║ DIST:xenial ║ DEBIANVERSION: xenial ║ UPDATE_REPO: /home/qubes/qubes-builder/qubes-src/linux-template- builder/pkgs-for-template/xenial ║ REPO_SUFFIX: ║ DISTRIBUTION_CAP:Qubuntu ║ REPO_PROXY: ║ APT_GET_OPTIONS: ║ CHROOT_ENV: BACKEND_VMM=xen ╚═══ mkdir: cannot create directory ‘chroot-qubuntu’: File exists mount: mount point chroot-qubuntu/tmp/qubes-deb does not exist /home/qubes/qubes-builder/qubes-src/builder-debian/Makefile.qubuntu:275: recipe for target 'update-repo-prepare' failed make[1]: *** [update-repo-prepare] Error 32 Makefile:297: recipe for target 'template-local-xenial' failed make: *** [template-local-xenial] Error 1 -- Pozdrawiam, Michał "rysiek" Woźniak Zmieniam klucz GPG :: http://rys.io/pl/147 GPG Key Transition :: http://rys.io/en/147 -- 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
Re: [qubes-users] Baffled About Passphrases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/16/2017 08:01 AM, Ron Allen Smith wrote: > Hi, > > I'm new to Qubes/Linux and would like to know how to > change/add/remove passphrases applied to the USB I installed Qubes > 3.2 on. I looked around at Qubes FAQs and elsewhere, which was > helpful, but not giving a step-by-step of what to do. > > [user@untrusted ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE > MOUNTPOINT xvdc 202:32 1 11.5G 0 disk ├─xvdc2202:34 > 1 10.5G 0 part │ └─dmroot 253:00 10G 0 dm / └─xvdc1 > 202:33 11G 0 part [SWAP] xvda 202:01 10G 1 > disk └─dmroot 253:00 10G 0 dm / xvdd 202:48 1 > 500M 1 disk /usr/lib/modules/4.9.56-21.pvops.qubes.x86_64 xvdb > 202:16 12G 0 disk /rw > > Although I selected default encryption during the Qubes install, I > can't determine whether or not enryption is actually set. > > I also looked at 'man cryptsetup', but unsure of how to use it, or > even if I should use it. > > Can anyone set me on the right path? > https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption#Cryptset up_actions_specific_for_LUKS https://unix.stackexchange.com/questions/252672/how-do-i-change-a-luks-p assword - -- Zrubi -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJaDViJAAoJEBozWgtUjzdkjEgP/0YJaJx02wCw58jXYDOFf3xY sa3VASFf9lNtWz3B9JSK8hM+mn4aIh402zS2oGu+OQLaE9oG4H+c2e2oNDwHihyu +nBGflOj0uPK4iWHrvKHiGm5p+etlrZMu7HJElMHLL5VE7LnHFsASwSfCDYAFKXL 6+pZXTIwXGF5RPiI0YZWdXf1+j1YA+i5VFaUWDaUXwLqcjgdCzrHyzI6T1oJXiGK fUzA6y1ynJ03GDb7Ik3XunS8rwzaIgjwke0LlNsST75CYhErGJt5Xw0tqNhVKK6A xdB920aFFA00G1yE5IbdNSkGSQiE9BqaAk3HGmMlNkD06i6dyczXoSFJ+7tS32dT SeoxfEGDK35k75lyTbY3md+NBM+xwdoYDvT1Hk9uOIAIMrckUJ2WVf7uqHSteCTR 2zdvQK55PDhR0cdx/YdXsHU+cYAHg4gV+fGV1PUAjuAfjjqcXRmrpjghlgffVvNF D3GHBkPWYNWtNqNXTVGNZBPLrxRyVeBFdjPUANefQd4PaOB+027a5TflBhtkRipU PnugdE14uU5/XDGbth2YIZtkfPPVOcjuoMUGzKBUo4Ak3Dbt7RQCEgySzGemJmYp 8PyM40qLTu+YcBoDtnmb1cmtv4gA2fjK1+fYlKqMBBBIQx0r6xrRYiyHZN/D4x3N tQHRthMFEhBep7ff2vpD =f8MO -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/4fde44df-7c27-2099-516a-edde9e6c697d%40zrubi.hu. For more options, visit https://groups.google.com/d/optout.
