[qubes-users] Re: Qubes 3.1 Installer Hangs on Creating default DisposableVM
Oops, subject should read 3.2 not 3.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/4c98413f-0a80-41a9-a7d6-b712a1f40779%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] проблемы с установкой usb wi-fi адаптера rtl8188eus
проблемы с установкой usb wi-fi адаптера rtl8188eus. как это вообще сделать? sys-net на qubes os просто не видит вайфай адщаптер. как исправить эту проблему? -- 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/68eabd77-4783-41a6-9b4b-aba8cd7252bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] how to integrate 3-year old backed up VM's into new system?
Marek Marczykowski-Górecki: > On Tue, Oct 18, 2016 at 12:05:33PM +, Emil Cronjäger wrote: > > >> Marek Marczykowski-Górecki: >>> On Mon, Oct 17, 2016 at 11:08:35PM +, Emil Cronjäger wrote: >>> >>> Marek Marczykowski-Górecki: > On Mon, Oct 17, 2016 at 07:50:26PM +, Emil Cronjäger wrote: > Take a look at those instructions (in order): > https://www.qubes-os.org/doc/upgrade-to-r3.0/ >>> That got me a shell in one of the two VM's - thanx! There were some problems with the ip-commands though, but I managed to get the data out, and put it into a fresh VM. >>> The other VM (also standalone), however, wont help me with a shell: >>> connected to domain [domain-name] error: operation failed: PTY device is not yet assigned >>> I am not sure or how to determine it, but it *might* be a debian-based VM, if that is to any help. >>> >>> Standalone (PV) VM, right? Or maybe some HVM? > >> yes, standalone VM, no HVM. > It is not crucial for me to get the VM up and running, but I need to get data out of it somehow. >>> >>> If you just want the data, create new VM, start it, and then attach the >>> old VM private.img and/or root.img to the new one as additional device: >>> >>> qvm-block --attach-file new-vm /var/lib/qubes/appvms/old-vm/private.img > > Correction: prefix file path with "dom0:". But if you didn't get any > error, it should be fine too... > >> The command goes through without any errors, but the device doesnt show >> up in new-vm. No changes in lsblk before/after. >> I tried the --frontend=xvdi, also goes through with no problem, but >> still no new device for me in new-vm. Does it hide somewhere special? > > No, it should be there as /dev/xvdi... Anything in `dmesg` output in > new-vm? > It worked with the "dom0:" option, the device got mounted as /dev/xvdi and all good. I mistakenly used prefix "old-vm:", thats why it did't work. Thanks a lot, all solved. -- 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/3977c91d-84b4-5632-58cc-f8f78a34cdf0%40riseup.net. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] SMB mount point location
On Saturday, October 15, 2016 at 10:30:06 PM UTC-4, Manuel Amador (Rudd-O) wrote: > On 10/13/2016 02:25 PM, John Maher wrote: > > On Wednesday, October 12, 2016 at 12:06:15 PM UTC-4, Manuel Amador (Rudd-O) > > wrote: > >> On 10/12/2016 12:55 PM, John Maher wrote: > >>> Hello, > >>> > >>> I'm trying to access file on the command line through an SMB mount point > >>> that is created in the GUI. I'm using a debian-8 AppVM and connecting to > >>> an SMB share in a Files window, but I cannot find a mount point for the > >>> share. I would expect it to be in /run/users/1000/.gvfs, but there's > >>> nothing there. > >>> > >>> Can anyone point out where I would find that mount point? > >> By default, GVFS won't actually mount it — it just appears in the Files > >> window. I believe the first time you attempt to activate (open) a file > >> on the share, GVFS does the mount. It used to be different, I know, I > >> just hit this issue myself a few days ago. > >> > >> This is more a GNOME upstream thing. > >> > >> Do your files show on the file manager? > >> > >> > >> -- > >> Rudd-O > >> http://rudd-o.com/ > > The real issue is that I'm trying to access a KeePassX database that > > resides on a smb share, and the Database > Open dialog box does not present > > mounted smb shares or bookmarks to the shares. Any thoughts on this? > > You need an actual mount for that to work, and the dialog box will not > trigger the mount operation. You have two choices: > > 1) Open your KeepAssX database in a StandaloneVM which you have > configured to mount the SMB drive. > 2) In the template, create and enable an /etc/systemd/system mount unit > for the SMB drive, that is only active if a file in > /var/run/qubes-service/ exists (check the various > qubes-*.service files in /usr/lib/systemd/system for examples on how the > ConditionPathExists thing works), then set up the qubes-service > on the VM in question. That way, when you boot the VM in > question, and only that VM in question, the mount appears immediately. > > I would also use automount units if I were you, just to make sure that > your VM where you run KeepAssX boots fast and does not wait to mount the > remote device. > > Here is a crude example of such a thing: > > [user@tpl ~]$ mkdir /mnt/keepassxmount > [user@tpl ~]$ cat > /etc/systemd/system/mnt-keepassxmount.mount > [Unit] > Description=Mount /mnt/keepassxmount > ConditionPathExists=/var/run/qubes-service/mnt-keepassxmount > Before=remote-fs.target > After=remote-fs-pre.target mnt-keepassxmount.path > > [Mount] > What=//smbserverip/keepassxmount > Where=/mnt/keepassxmount > Type=cifs > Options=_netdev,cache=strict,forceuid,forcegid,noperm,noserverino,nomapposix,nomapchars,uid=user,gid=user,forceuid,forcegid > > [Install] > WantedBy=remote-fs.target > [user@tpl ~]$ systemctl enable mnt-keepassxmount.mount > > At this point you add the Qubes service mnt-keepassxmount in your VM's > configuration. > > Option 3: use some file sync service to keep that KeepAssX file > synchronized to local disk on that VM. > > > -- > Rudd-O > http://rudd-o.com/ Manuel, this is awesome! Thank you for the extensive explanation. Regarding option 3, are you referring to a Qubes service or some other type of utility? Being new to Qubes, your mentioning of services above is my introduction to Qubes services. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2c228b10-2abd-4d2e-876d-77802b22614c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Anonymize MAC address
On 10/18/2016 04:26 AM, pl1...@sigaint.org wrote: On 10/16/2016 02:02 PM, pl1...@sigaint.org wrote: On 10/15/2016 08:59 AM, pl1...@sigaint.org wrote: Anyone? Instructions for MAC anonymization have just been updated: https://www.qubes-os.org/doc/anonymizing-your-mac-address/ Chris Ok, is recommend to use debian as sys-net My question is about already used mac-spoof in sys-net, please can you try to give me an answer if it is possible? pL11 Maybe someone involved in the macchanger instructions can chime in with advice. My personal recommendation would be to use Network Manager, as the Macchanger script is prone to breakage and lists these limitations: * This does not randomize your MAC Address on sleep and wake state (only on restarting the |sys-net| VM) * The |sys-net| networking VM takes longer for device drivers to start up than usual, this delayed startup may cause the first attempt of |sys-whonix| to connect to Tor to fail I started about 2 years ago trying to get Macchanger to work consistently. None of the different approaches really did the job. It should be handled by the system's network configuration daemon, which is Network Manager. Chris Hi Yes, each time that I want to randomize mac address I have to shutdown the sys-net, activate macspoof-wlp0s1 and restart the pc. Does the mac address spoof with debian 9 work perfectly? Can I remove mac changer from fedore, then the drivers start immediately? It has worked perfectly for me so far. The only problem was a slight incompatibility NM 1.4.x has with old connection settings from versions 1.2.x and earlier. If you use the old connection data it will only randomize in scan mode, not for connections. That was easily solved by creating a new sys-net after the upgrade. You can remove the macchanger scripts according to the uninstall directions in the doc, though starting with a fresh template would accomplish the same thing. Chris -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/53f09693-ca9b-87db-f3b7-e2f3f63ad2cb%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Lenovo E460 (i5-6200U)
Hi, The E460 hardware specification: 14" i5-6200U Intel IGP 8 GB RAM 1 TB HDD Anti-glare screen No OS 1.8 kg I initially tried Qubes 3.2, but, it simply kept rebooting after printing "dom0: detected vCPUS ...". So, I proceeded to install 3.1. I booted with secure boot off, EFI disabled and in legacy mode. VT-d is enabled in BIOS. I set Dvorak keyboard as default. Keyboard, touchpad and trackpoint work fine by default. Display is good, and connecting to an external display works. I have not tested the camera. Suspend to resume works partially. Sometimes, unlocking does not allow me to log into X server, and I get a blank screen. I have to login to console instead. Audio has been tested. Attaching USB devices also works. Wireless works fine. Regards, SK -- Shakthi Kannan http://www.shakthimaan.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/CABG-yt3Wn5GsiTai9-JeeJ3g6Dyi7V%3DmBib38Ebz-qnfBNgmmQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20EUA00P00-20161009-095148.yml Description: application/yaml
Re: [qubes-users] how to integrate 3-year old backed up VM's into new system?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, Oct 18, 2016 at 12:05:33PM +, Emil Cronjäger wrote: > > > Marek Marczykowski-Górecki: > > On Mon, Oct 17, 2016 at 11:08:35PM +, Emil Cronjäger wrote: > > > > > >> Marek Marczykowski-Górecki: > >>> On Mon, Oct 17, 2016 at 07:50:26PM +, Emil Cronjäger wrote: > >>> Take a look at those instructions (in order): > >>> https://www.qubes-os.org/doc/upgrade-to-r3.0/ > > > >> That got me a shell in one of the two VM's - thanx! There were some > >> problems with the ip-commands though, but I managed to get the data out, > >> and put it into a fresh VM. > > > >> The other VM (also standalone), however, wont help me with a shell: > > > >>connected to domain [domain-name] > >>error: operation failed: PTY device is not yet assigned > > > >> I am not sure or how to determine it, but it *might* be a debian-based > >> VM, if that is to any help. > > > > Standalone (PV) VM, right? Or maybe some HVM? > > yes, standalone VM, no HVM. > > >> It is not crucial for me to get the VM up and running, but I need to get > >> data out of it somehow. > > > > If you just want the data, create new VM, start it, and then attach the > > old VM private.img and/or root.img to the new one as additional device: > > > > qvm-block --attach-file new-vm /var/lib/qubes/appvms/old-vm/private.img Correction: prefix file path with "dom0:". But if you didn't get any error, it should be fine too... > The command goes through without any errors, but the device doesnt show > up in new-vm. No changes in lsblk before/after. > I tried the --frontend=xvdi, also goes through with no problem, but > still no new device for me in new-vm. Does it hide somewhere special? No, it should be there as /dev/xvdi... Anything in `dmesg` output in new-vm? - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYBhqoAAoJENuP0xzK19csXTkH/RvFHSeBlkCDI9U+4oyCUB7W Pb2BeeodM2JUSTitFSHfhv6hioW0wVAfEFGMUHEWwS5I48w183j50EEmPZ1Jl+/L llVa87oCTEkKhgDttgpWCW7p4EbUIS3bltm7vYF5FWv1BuvvPXdSuB666oLbpXaJ evUYVnFbh+b1SEV5PTcfHRfXRfm3/fbFjda77xH99U640GkdmIHLIkVMBfSBullv AGOPxdGvhJCNCmyJC01DcP2nKeDKi3z/+lnYDFb6AU97R3xRsK47hgZJ6PXB0llN 8j2muAth4mrgaYA0QZbFl4DRzF4mjVnYnDpXFL81aRe6vvGLtA1kl7gW9Lyr/Kw= =o89T -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/20161018125050.GQ15776%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] how to integrate 3-year old backed up VM's into new system?
Marek Marczykowski-Górecki: > On Mon, Oct 17, 2016 at 11:08:35PM +, Emil Cronjäger wrote: > > >> Marek Marczykowski-Górecki: >>> On Mon, Oct 17, 2016 at 07:50:26PM +, Emil Cronjäger wrote: >>> Take a look at those instructions (in order): >>> https://www.qubes-os.org/doc/upgrade-to-r3.0/ > >> That got me a shell in one of the two VM's - thanx! There were some >> problems with the ip-commands though, but I managed to get the data out, >> and put it into a fresh VM. > >> The other VM (also standalone), however, wont help me with a shell: > >> connected to domain [domain-name] >> error: operation failed: PTY device is not yet assigned > >> I am not sure or how to determine it, but it *might* be a debian-based >> VM, if that is to any help. > > Standalone (PV) VM, right? Or maybe some HVM? yes, standalone VM, no HVM. >> It is not crucial for me to get the VM up and running, but I need to get >> data out of it somehow. > > If you just want the data, create new VM, start it, and then attach the > old VM private.img and/or root.img to the new one as additional device: > > qvm-block --attach-file new-vm /var/lib/qubes/appvms/old-vm/private.img The command goes through without any errors, but the device doesnt show up in new-vm. No changes in lsblk before/after. I tried the --frontend=xvdi, also goes through with no problem, but still no new device for me in new-vm. Does it hide somewhere special? -- 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/3feb4473-aae0-f734-82d5-0baf4af76129%40riseup.net. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
