[qubes-users] Re: qvm-sync-appmenus problems
hmm well if in dom0 qvm-sync-appmenus syncs all the appvm's shortcuts based on that template, what command in which domain would sync the shortcut menu items for the Templates ? maybe 'refresh' button at the top of the Qube settings-> Applications? as I did try moving all but one item from the Right to the Left and 'refreshing' and noticed I get an icon for that one item, but if I move everything to the right there are many items with the application listing but no icon, I do get 4 'Warnings' when I do dom0: qvm-sync-appmenus Template , one says its missing an icon, another is missing a 'Name' key hmmm -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7d0d4ef1-6d7f-bce5-09c7-9893404c2dca%40riseup.net.
[qubes-users] Re: qvm-sync-appmenus problems
sorry seems 1st posting body was empty , I move all items to the left in the template qubes settings, then hit 'refresh applications' ; shutdown template Qube, however in the Q menu still seeing every application , frustrating , I can trash the Template, but that's not going to fix the fact that the shortcuts still exist for the deleted AppVM I imagine? On 7/1/20 4:13 PM, anon wrote: Hello, I added some non package software directly to /usr/share/applications/newsoftware.desktop following the template of another .desktop file --- [Desktop Entry] Name=newsoftware Comment= GenericName=web Exec=/home/user/qutebrowser/.venv/bin/python3 -m qutebrowser Icon= Terminal=false Type=Application Categories= X-KDE-StartupNotify=false qvm-sync-appmenus --- I moved the newsoftware into the AppVM, which I'm assuming is how the desktop shortcuts is starting successfully now. after doing qvm-sync-appmenus in dom0 Issue I'm having is 2 -fold ; 1) one AppVM was showing every single installed software reference, despite having cleared them to the left in qube settings, so I deleted it , however its still showing in the Q shortcuts, even after having removed the dir manually and re-running qvm-sync-appmenus. 2) the template is also now showing *Every installed app despite having cleared them to the left, though the other AppVMs that are based on it are behaving. how should I proceed to get things working normally again ? 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d68472af-76f4-d9ab-7b41-4a1056a1abba%40riseup.net.
[qubes-users] qvm-sync-appmenus problems
Hello, I added some non package software directly to /usr/share/applications/newsoftware.desktop following the template of another .desktop file --- [Desktop Entry] Name=newsoftware Comment= GenericName=web Exec=/home/user/qutebrowser/.venv/bin/python3 -m qutebrowser Icon= Terminal=false Type=Application Categories= X-KDE-StartupNotify=false qvm-sync-appmenus --- I moved the newsoftware into the AppVM, which I'm assuming is how the desktop shortcuts is starting successfully now. after doing qvm-sync-appmenus in dom0 Issue I'm having is 2 -fold ; 1) one AppVM was showing every single installed software reference, despite having cleared them to the left in qube settings, so I deleted it , however its still showing in the Q shortcuts, even after having removed the dir manually and re-running qvm-sync-appmenus. 2) the template is also now showing *Every installed app despite having cleared them to the left, though the other AppVMs that are based on it are behaving. how should I proceed to get things working normally again ? 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e45063f4-d85b-8270-3b57-b139e9fb12f0%40riseup.net.
[qubes-users] dom0 /qubes version how
I see there is a 4.0.3 in the website. I believe I am using 4.0.1 , dumb question but how do I confirm what version am I using? I just do the dom0 updates, so imagine things are fine, but shouldn't I be on 4.0.3 if that is what is offered on the website? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f6f0c783-7bc6-7f9b-dd19-8d44bf9ef6ba%40riseup.net.
[qubes-users] Installing qutebrowser with virtualenv?
hello, I'm trying to use qutebrowser by installing it in a debian-10 template as so: https://github.com/qutebrowser/qutebrowser/blob/master/doc/install.asciidoc#tox which works from the template, however, does not work on an AppVM based on it is there a way to make it work securely ? or maybe by design it shouldn't work? I changed this: Creating a wrapper script Running mkvenv.py does not install a system-wide qutebrowser script. You can launch qutebrowser by doing: .venv/bin/python3 -m qutebrowser You can create a simple wrapper script to start qutebrowser somewhere in your $PATH (e.g. /usr/local/bin/qutebrowser or ~/bin/qutebrowser): #!/bin/bash ~/path/to/qutebrowser/.venv/bin/python3 -m qutebrowser "$@" to: $ cat /rw/usrlocal/bin/qutebrowser #!/bin/bash /home/user/qutebrowser/.venv/bin/python3 -m qutebrowser "$@" I'm not high level qubes user, regards -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3d88b4a4-9a71-2e4d-51a7-f0522a826716%40riseup.net.
[qubes-users] Fedora 31 ?
thank you for your reply, not sure what I'm doing wrong if it is there? maybe I don't have the correct repos? where-ever it is that dom0 stores those? I've had successful dom0 updates over the last month, btw, from the widget @dom0 ~]$ sudo qubes-dom0-update qubes-template-fedora-31 Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Last metadata expiration check: 1 day, 9:07:55 ago on . No match for argument: qubes-template-fedora-31 Error: Unable to find a match: qubes-template-fedora-31 -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a2bc2162-60f0-09ea-aa48-1a2a0df5188c%40riseup.net.
[qubes-users] Fedora 31 ?
I'm not so sure its me. I've been around, think I know the basics am not seeing it @dom0 ~]$ rpm -qa |grep fedora qubes-template-fedora-30-4.0.1-201906241949.noarch -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/04e67576-bfdf-8a5a-5c9d-0497fe3c86b9%40riseup.net.
[qubes-users] dom0 journalctl errors in red
Hello ,
I see this all in red, I'm not sure what it's trying to tell me ?
increase dom0 memory allocation or ?
Xen free = 387860283 too small for satisfy assignments!
assigned_but_unused=379654787, domdict={'23': {'mem_used': 352968704,
'slow_memset_react': False, 'last_target': 1720813675, 'no_progress':
False, 'memory_current': 1682808832, 'memory_maximum': 4194304000,
'memory_actual': 1699652469, 'id': '23'}, '28': {'mem_used': 297312256,
'slow_memset_react': False, 'last_target': 1538314176, 'no_progress':
False, 'memory_current': 1503195136, 'memory_maximum': 4194304000,
'memory_actual': 1520039249, 'id': '28'}, '15': {'mem_used': None,
'slow_memset_react': False, 'last_target': 402653184, 'no_progress':
False, 'memory_current': 402694144, 'memory_maximum': 419430400,
'memory_actual': 402694144, 'id': '15'}, '18': {'mem_used': 1347514368,
'slow_memset_react': False, 'last_target': 2831155200, 'no_progress':
False, 'memory_current': 2814312448, 'memory_maximum': 2831155200,
'memory_actual': 2831155200, 'id': '18'}, '16': {'mem_used': None,
'slow_memset_react': False, 'last_target': 150994944, 'no_progress':
False, 'memory_current': 150994944, 'memory_maximum': 150994944,
'memory_actual': 150994944, 'id': '16'}, '22': {'mem_used': 759627776,
'slow_memset_react': False, 'last_target': 3054263423, 'no_progress':
False, 'memory_current': 2995167232, 'memory_maximum': 3355443200,
'memory_actual': 3012013357, 'id': '22'}, '0': {'mem_used': 1371455488,
'slow_memset_react': False, 'last_target': 4294967296, 'no_progress':
False, 'memory_current': 4211744768, 'memory_maximum': 4294967296,
'memory_actual': 4294967296, 'id': '0'}, '21': {'mem_used': 1347584000,
'slow_memset_react': False, 'last_target': 3670016000, 'no_progress':
False, 'memory_current': 3653173248, 'memory_maximum': 3670016000,
'memory_actual': 3670016000, 'id': '21'}, '25': {'mem_used': 1162686464,
'slow_memset_react': False, 'last_target': 4375907382, 'no_progress':
False, 'memory_current': 4295909376, 'memory_maximum': 4823449600,
'memory_actual': 4312755167, 'id': '25'}, '19': {'mem_used': 1225986048,
'slow_memset_react': False, 'last_target': 3512729600, 'no_progress':
False, 'memory_current': 3495886848, 'memory_maximum': 3512729600,
'memory_actual': 3512729600, 'id': '19'}, '24': {'mem_used': 313790464,
'slow_memset_react': False, 'last_target': 1572864000, 'no_progress':
False, 'memory_current': 1556021248, 'memory_maximum': 1572864000,
'memory_actual': 1572864000, 'id': '24'}, '20': {'mem_used': 1017421824,
'slow_memset_react': False, 'last_target': 3899579394, 'no_progress':
False, 'memory_current': 3913129984, 'memory_maximum': 4194304000,
'memory_actual': 3913129984, 'id': '20'}, '14': {'mem_used': None,
'slow_memset_react': False, 'last_target': 150994944, 'no_progress':
False, 'memory_current': 150994944, 'memory_maximum': 150994944,
'memory_actual': 150994944, 'id': '14'}, '17': {'mem_used': 339472384,
'slow_memset_react': False, 'last_target': 1676558755, 'no_progress':
False, 'memory_current': 1659715584, 'memory_maximum': 4194304000,
'memory_actual': 1676558755, 'id': '17'}, '13': {'mem_used': None,
'slow_memset_react': False, 'last_target': 297795584, 'no_progress':
False, 'memory_current': 297836544, 'memory_maximum': 314572800,
'memory_actual': 297836544, 'id': '13'}}
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/1593141b-2cae-f162-e834-ecf65e4574cf%40riseup.net.
[qubes-users] Yubikey for OTP password manager 2FA only ...with Q4.5 sys-usb please
Hello, using Q4.5 I have been reading the various yubikey howto problem-solving, but remain confused what to expect for my use of the Yubikey, which is, I believe OTP for 2FA for lastpass On my desktop I have Q3.2 and no sys-usb and I have NOT had to install any particular packages in dom0 or the Fed26 template etc. in Q4.5 I do note the widget to attach the Yubikey to the AppVM example: EmailVM , and I see it attached with lspci in the AppVM , using the widget, however it is nonfunctional. Typically, the Yubikey at times asks you to detach and reattach it, which probably in hindsight is not a good idea, as after doing that the widget will no longer allow any detaching. when I go into dom0 and do qvm-device attach email sys-usb:2-1.1 at current it is freezing and I can't Ctl+c out of the command I have 8gb Ram in an i7 thinkpad here, and for some reason I can't even get sys-usb to launch a Terminal, guess I'll be rebooting , maybe an SSD in the future is going to make Q4.5 usable ? (sorry added some commentary here) :O I believe at one point it told me the qubes usb proxy was not installed, then I went and tried to dnf install qubes proxy in the sys-usb and it said it *Was already installed. I find sys-usb the most difficult aspect of Qubes use, on Q3.2 after locking myself out I gave up on sys-usb ... and don't feel for my purposes a huge worry re: security ..can I do the same in Q4 or ... what do you suggest .. -- 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/51f6fd3d-aa10-9734-bde3-402a70dda983%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] [Q4-rc5] Blank screen on boot after installation on Lenovo
If it helps same problem here, after using the Thinkpad Troubleshooting docs link, went through the whole thing, then there is *No xen.cfg to change to BOOT only a efi.cfg (which I saw in another post in the usergroup someone also saw) ; I changed the efi.cfg references to BOOT and was able to install, but after install in EFI mode, I get display problems with the boot up penguins and loading then the blank screen. This is a T520 series... So, I went back to the legacy install and all is well for now -- 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/a8b21a6d-ea0d-1011-ec7c-c8a0b991390a%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Suggestions for running media server?
I'm looking for some suggestions for running a "maximally-secure" media server that will access an encrypted USB hard drive for it's storage. It can and probably should be read-only to the media-server software. A few possibilities I can think of listed from assumed lowest security to highest security: 1) run the media server in the sys-usb VM. 2) stop sys-usb VM and run another VM that doesn't start on boot but has access to all the USB devices and is run manually after boot 3) run another VM that only has one "locked down" dedicated USB device and remove that device from sys-usb VM permanently 4) run another VM that accesses the storage through sys-usb (I am unfamiliar with this, but assmue it's possible) The media-server software will by non-proprietary (DLNA compliant) and open. All thoughts are welcome, including those that say "don't do it." If there's something else I should be reading instead, please let me know. Thanks. -- 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/nqcr7n%24d6s%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: epoxy on ram to prevent cold boot attacks?
Marek Marczykowski-Górecki: > If you (or someone else) plug a malicious USB device that will exploit > some bug in one of million USB device drivers, it can do whatever it > want with the other USB devices on the same bus. And if that USB > controller live in dom0, it's game over even without injecting malicious > keystrokes. > PS/2 is much better, because you can't connect anything else than input > devices there, and attack surface is much smaller. After having read the entirety of the PC security paper Joanna wrote a while back, I was shocked to see how poor PC security really is. I found it one of the most profound papers I've ever read. As far as I'm concerned, it should be required reading for anyone capable of understanding even the basics. What you wrote reminds me of that feeling and how wide open and vulnerable things really are for those that know what they're doing. It's amazing to me things have been "allowed" to get this bad. All genuine efforts into making things better are very much appreciated and needed by all of us. Thank you. -- 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/nqcosk%24rm2%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: SOLVED - R3.1 - "Freezing?" sys-usb VM via mkfs.vat command
Marek Marczykowski-Górecki > It may still be out of memory problem, because sys-usb has statically > assigned 300MB, so even if you have no other VMs running, it will not > use free memory. This is mostly requirement to handle PCI devices, which > require continuous memory region. But you can increase this assignment > in sys-usb settings. Thank you. I see that sys-usb isn't participating in the memory sharing. I never noticed that before. I changed the min ram setting for sys-usb to 600MB and reran the command. It finished in about three seconds; so fast, I almost didn't believe it worked. So this seems to be the solution: increase memory to above 300MB (and 600MB is confirmed to work for this). I know very little about out-of-memory error handling, but it seems like Qubes could have a little bit more user-friendly information in instances like this; especially for someone like me. If there's something more I need to do, please let me know. Thank you for the help. -- 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/nq57ud%24nbh%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: R3.1 - "Freezing?" sys-usb VM via mkfs.vat command
Andrew David Wong: > If this is Qubes-related at all, it sounds like a hardware > compatibility issue, so qubes-users is the right place. Great thank you. > Do you have any other USB drives that you can try instead in order to > help determine whether the problem is the drive itself? I have USB sticks of the 8-16GB capacity type. This drive that I'm having issues with is a platter harddrive type. > Is it possible that the problem is trying to format with vfat instead > of a different filesystem? (How large is the drive?) Yes it is possible that the problem is vfat. Do you have any suggestions of pages for me to read in order to understand the types? Or alternative commands? I'm trying to have it be usable in Windows and Linux, though I probably will never connect it to Windows. The drive that I'm having problems with is 1.8TB. Thank you. -- 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/nq57lm%24vbk%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
