Re: [qubes-users] AEM boot option causes hard reboot/partial shutdown (Lenovo T450s)
On 05/16/2016 11:44 PM, Andrew David Wong wrote: > I'm attempting to install Anti Evil Maid on a Lenovo T450s (Broadwell, > Wildcat Point-LP). > > A previous report from Alex Guzman indicated that AEM works on this > model. [1] However, I've followed the instructions [2] to the letter > and across dozens of variations over the course of days with no luck. > It's possible I'm missing something obvious, but here's what I've tried: > > * Use legacy boot option. > * Use UEFI boot option. > * Try all USB ports. > * Try different USB drives. > * Install to /boot partition on internal SSD. > * Enable/disable different BIOS USB options. > * Try different AEM text secrets (e.g., no symbols). > * Check that the correct SINIT module is in /boot. >Unless I'm mistaken, for the T450s, it should be: > > 5th_gen_i5_i7_SINIT_79.BIN > > In all cases, everything goes smoothly with the installation up to > step 5 (reboot and select the "AEM Qubes" GRUB option). I select that > option (or allow it to be auto-selected, or select the one in the > "advanced" submenu). It gets about 4 lines in (up to "loading initial > ramdisk," I think; a bit too fast to read), then the laptop appears to > do a hard reboot/partial shutdown. Instead of a normal reboot with the > BIOS and normal boot process, the screen is blank, but the system > retains power. (Power button is lit and keyboard backlight brightness > can be changed.) > > Does anyone have any ideas or tips about this one? Any help would be > greatly appreciated. > > > [1] https://groups.google.com/d/topic/qubes-users/jelz1pA8Ilk/discussion > [2] https://github.com/QubesOS/qubes-antievilmaid/blob/master/anti- > evil-maid/README > Andrew, did you ever get this resolved? I seem to have this exact same problem, but only after installing Qubes 3.2 (worked fine with 3.1) on my Thinkpad T430. -- 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/c90a4d4c-457f-0edf-daa8-a2af09412502%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] AEM with Linux 4.4 causes hard reboot (cont... Trying to resolve issue)
On 07/30/2016 02:52 PM, Marek Marczykowski-Górecki wrote: > On Sat, Jul 30, 2016 at 02:44:24PM -0700, tel wrote: > > Sorry for the delay, Chris. I was waiting for 3.2-rc2, which I just > installed. It seems to come with the latest AEM package, so I didn't > have to install that package myself. > > > I added the parameter to the tboot line. It didn't reboot, but it > hung before asking for the password with "Waiting for > /dev/disk/by-label/aem* to be connected..." > > > Not sure where to go from here. > > Do you use also USB VM? In that case, dom0 has no access to USB > controllers... > > But you can re-enable it just for boot time by editing /etc/default/grub > and removing the line with "hide_all_usb" (or just comment it out). Then > rerun `grub2-mkconfig -o /boot/grub2/grub.cfg`. > It will expose dom0 for all connected USB devices for a short time > during system startup. > > Yep. That's the ticket. I can confirm that Chris' method works, and I now have a working anti-evil-maid! Thanks Chris and Marek! -- 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/b4d04e38-489e-2b4c-f66d-b780ed1eae60%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Bitcoin Qubes tutorial
On 2016-06-28 12:01, Franz wrote:
Hello,
is there some form of tutorial for using Bitcoins with Qubes,
considering that I have no experience of bitcoins?
It seem I should have a VM for a hot wallet for making transactions
and another for a cold wallet to keep the bitcoins. But have no idea
if it is possible to move bitcoins between the two
Also imagine a good practice would be to make a backup of the VMs
containing the wallets using Qubes backup.
It would be also interesting to know which clients you consider safer
for buying and selling bitcoins.
Thanks
Best
Fran
Hi, Fran. I've done exactly this using the Electrum bitcoin wallet. I
have a dedicated hot ("watching") wallet in its own VM, and a cold
(offline) wallet in a separate VM that's never network-connected.
Although I'm hardly a bitcoin expert, I don't think it's a matter of
"transferring bitcoin from one wallet to another." Rather, I think the
cold wallet just holds the private keys used when authorizing bitcoin
transactions. For example, if I'm buying something with 1 bc, I generate
a pending transaction in the hot wallet, sign that transaction in the
cold wallet, transfer the signed transaction back to the hot wallet, and
then broadcast it from there. That way, only that 1 bc is ever
vulnerable in a network-connected VM.
If I'm misunderstanding this, or doing it wrong, I'd love to be educated
by a bitcoin guru!
Todd
--
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/59a6d11ff0484fc1ae7bda853f9dbada%40nowlas.org.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Can't open an attachment from thunderbird (3.2 rc-1)
There is a PDF in an email attachment I'd like to open in a dispVM from Thunderbird. When I choose that option, I get this error message: qopen-in-vm: Fatal error: send filename to dispVM (error type: Broken pipe) Shouldn't this be "qvm-open-in-vm..."? Or is there another issue I'm missing. FWIW, this is the first time I've tried this in 3.2rc-1. In 3.1, this procedure worked as expected. Todd -- 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/a2b628f2-0ab9-57ee-a224-81a15dfb1d69%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error
On 2017-03-17 11:55, jimmy.dack...@gmail.com wrote: I'm trying out the backup feature in Qubes but getting an error. I'm trying to save VMs totaling 22.4GB in size on a USB stick with 63GB free. At 19% progress is get: "[Dom0] Backup error! ERROR: Failed to write the backup, VM output: cat: write error: File too large." Is there a maximum file size for backups? A RAM limitation (I have 8GB RAM and when I do the backup about 6GB is free)? Something else I'm not thinking of? I am able to do a small backup, such as just Dom0 itself. Also a general question about backups: if I do a backup and then restore, will it add what I backed up to what is already on the system? Or completely overwrite everything? For example, if I have 10 VMs and backup 3, then restore the 3, will it just overwrite those three and leave the other 7 alone? Or will I only have those 3 and the other 7 are wiped out? Also, be sure you didn't make the mistake I made once. I (stupidly) mounted by backup USB stick in Dom0. Then, when backing up Dom0, it tried to back up all the data on the backup stick, which of course kept increasing in size as more stuff got backed up onto it. I've since learned to use a USBVM, and mount the stick in a dedicated BackupVM. -- 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/10747aff541781e0d2738fb6c6ca7f97%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Why should I clone a template?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The dogma, as I understand it, is that it's safer to clone a template, make changes to the clone, then base your AppVM's off of that cloned template. - From the Qubes website: "It is highly recommended to clone the original template, and make any changes in the clone instead of the original template. The following command clones the template. Replace your-new-clone with your desired name..." My question is, why? It seems to me that if you ever needed the original template back, you could just download it again from the repository. Am I missing something? Todd -- 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/712220ed-ca56-509a-ffe2-b5c47bdb14f3%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Why should I clone a template?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/20/2017 06:12 PM, Andrew David Wong wrote: > On 2017-05-20 19:43, Todd Lasman wrote: > > The dogma, as I understand it, is that it's safer to clone a template, > > make changes to the clone, then base your AppVM's off of that cloned > > template. > > > - From the Qubes website: > > "It is highly recommended to clone the original template, and make any > > changes in the clone instead of the original template. The following > > command clones the template. Replace your-new-clone with your desired > > name..." > > > My question is, why? It seems to me that if you ever needed the original > > template back, you could just download it again from the repository. Am > > I missing something? > > > Todd > > > The main reasons are that user customizations are not guaranteed to be > preserved in RPM-managed templates, and they're harder to back up and > restore. > > Hmm. Not sure I understand that logic. The cloned templates still need to be managed and backed up, so where's the advantage? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJZIQKOAAoJEOaMWwQFV9eFyLkP/R3z2y1BcWTz0JqRywG2Bpss blNct9980O5I2uMuRAn7wOplL06fIbOEtvarqbqby8WwvUVi4775/V7AF/zCCQ21 v9PIWJ1uqhhBoeO3aVVFk77CmMxS2M01rZShCjIjUCpsT/MiNCkJQNzDOdFYRJYQ iEJRXrA+qSJrfwPucQaeBjaXErQfuLASbCs+3l/EMtSrYerof4vD9vMjgbR4P4cm avJj9dpXmbiGWOtwz+Va9MGrvpNP4cYRoDbzDUSAWu4VceTQPHuloWq3xg9H94HF stzwYdRxonwj1sVgtsVkdoI/ljdoaDL+h0vr4HUZKnsdM2+nfJk+VQWsoiKUwR1B 4xWr0zSKlCWLFLSCqRMw4ZTTx0WIqrWNmMPmcQaezMOdl7jJaG7mt9KyOkx6Nut2 HuaReIeUbifP2o2X7Sz/52n3zp8+jmEJW2n/vdoa1R9OCjDxT/4c1rxd8mjU/IRs zZ9FcGgw4pQ8fqQGjY4ZAnLDlUmAvjuxq7qPMSrAmvpE7ho5wMyK/o9lP7S+C3Ny bGWdDqNPPU0VMGzGQlfBytjZdVzvn8QlZTLdvuPLQHUPpOaVKf3+TEV69KquJFcO 4BZEHh11onr8SC64D/xWMonmXbtPuYpYKkh6zG+6gAzxo5JenLWUHkHiiKFtqRVg wg/5IuEilrU/gIwpJuNU =ExCY -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/43dcf593-04c8-d211-8c52-5e821ee23f7c%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Why should I clone a template?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/20/2017 05:51 PM, Reg Tiangha wrote: > On 05/20/2017 06:43 PM, Todd Lasman wrote: >> The dogma, as I understand it, is that it's safer to clone a template, >> make changes to the clone, then base your AppVM's off of that cloned >> template. >> >> - From the Qubes website: >> "It is highly recommended to clone the original template, and make any >> changes in the clone instead of the original template. The following >> command clones the template. Replace your-new-clone with your desired >> name..." >> >> My question is, why? It seems to me that if you ever needed the >> original template back, you could just download it again from the >> repository. Am I missing something? >> >> Todd > > > Not really. It's more of a convenience thing and/or advice for those who > have limited bandwidth or data caps on their internet connection. If you > don't mind re-downloading the original template (which might be 1GB+) > plus maybe hundreds of MBs worth of updates afterwards, then it's up to > you. Otherwise, it's more bandwidth efficient to keep the stock > templates up-to-date and clone them if you need to make more specialized > templates later on. > > Ok. That makes sense to me. 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/6e76538d-10e6-7c48-50ee-a7983eb296c5%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Apps not starting on the first try
On Sat, May 06, 2017 at 10:41:04PM -0400, Chris Laprise wrote: > On 05/06/2017 12:30 PM, Todd Lasman wrote: > > > >-BEGIN PGP SIGNED MESSAGE- > >Hash: SHA256 > > > >This seems to be a new issue on a recent reboot. > > > >If I try to run a program from a VM that's not yet running, the VM > >starts as expected, but the program never runs. Even after the VM is up > >and running, I can't get any program to run in that VM. Even opening a > >window in dom0 and using the qvm-run command does nothing. > > > >However, if I kill the VM, the next time I try to run a program (which > >reopens the VM), it works perfectly. > > > >Any thoughts on troubleshooting this? > > > >Thanks. > > This is a long-term issue and the reports usually center around nautilus > (Files) because that it the most prone to the behavior. > > See https://github.com/QubesOS/qubes-issues/issues/2449 > > I believe its caused by gnome expecting some session-related daemon to be > already running when it tries to start a program. > > -- > > Chris Laprise, tas...@openmailbox.org > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/8edee868-fc2b-e0d6-3ec2-0ebf3b1ee684%40openmailbox.org. > For more options, visit https://groups.google.com/d/optout. Thanks. For some reason, I don't remember this happening in the past, but I could be wrong. I'll be patient. Todd -- 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/20170507154745.GA17456%40d1stkfactory. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
[qubes-users] Apps not starting on the first try
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This seems to be a new issue on a recent reboot. If I try to run a program from a VM that's not yet running, the VM starts as expected, but the program never runs. Even after the VM is up and running, I can't get any program to run in that VM. Even opening a window in dom0 and using the qvm-run command does nothing. However, if I kill the VM, the next time I try to run a program (which reopens the VM), it works perfectly. Any thoughts on troubleshooting this? Thanks. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJZDfovAAoJEOaMWwQFV9eFe68P/isxRedhykFef9rvRfpyPmWB jRRMZ7k00boATC2n25iW7OXS6hxNVjmOD6nOXp+alx1XJ4tMOf3y7Wu9vay91Uuv zFXPMUqHxw8jXGjXANI5+yUiJt9u82lQZbln+7k68j2sNYUaiAeBrA8J0a98LsMK qpHwxqCckEAKImyoCoN5PJLqKqnbb+36rzb7PgVjHnJI/bSclqdrSAidiKBXJxWV ie9KcMT97V7LN021n0KLxJTIIlAaiRDoXq/ZS2hRxqGSw3GA+kQUdEVn/zvpCA3o goX4b/TwzhezkpZW4O8i/jWS7PwVY28TkE5ezM87uu1oBEAIhLoLHgQJJW4/qEe3 Yl46xve1kl8PmEMrvpY26EsM1NaCKaKdoAgAxlRH6yG7j50P5Etlp0BJ9qH4EMu5 56hrDeiPZVQcOf97wbxBrubDvuVYethXG+bVpBp14W71dMC0ixXkBaDAylZUCt7M lZf7qCCX312e3z8eY5TRrTe1x+/5ibIUs6GMJhFHdhACDHh7fS5UoN8qXHli8rK1 79Vu5tIOAfjXThd1RuFnU94+e8BnY87CRvyAWKK3Ec9VUoD1nYz2IIAqizE4gqk8 dADdmNkX7bUWzy3uVgrCvrhT43wDC4eWQ4v6ShTtZSyBhZjKreMPocX4abKG8Mu1 jYFk4doS0YOLQNj/KXAU =FU+3 -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/fb931d51-9838-6a1d-0071-07f54397c7d0%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] split gpg: multiple authorization windows popping, autoaccept not working
On 05/08/18 10:12, Quentin wrote: > Trying to get split gpg to work with thunderbird. > > When I click on write in thunderbird it opens three authorization > windows. First time I give authorization to access my gpg qube, it asks > to give the permission for 5 minutes. After accepting that, there are > still authorization windows popping. > > > How to give the authorizations to access the gpg qube for 5 minutes? > >From the website, and new in Qubes 4.0: New qrexec policies in Qubes R4.0 by default require the user to enter the name of the domain containing GPG keys each time it is accessed. To improve usability for Thunderbird+Enigmail, in dom0 place the following line at the top of the file /etc/qubes-rpc/policy/qubes.Gpg: work-email work-gpg allow where work-email is the Thunderbird+Enigmail AppVM and work-gpg contains your GPG keys. -- 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/a11fee92-6e62-4bef-10b0-74d0f5a50da7%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/21/2017 05:42 PM, yreb...@riseup.net wrote: > hello, I went through the docs on creating a backup of the VMs, trouble > is > , I don't have the basic concept of which VMs to backup, e.g. Dom0 is > said to be 500Gb by itself, and the Deb 8 and Fed 25 are also hundreds > of Gbs, as is my non-network VM where I keep all my old photos , which > I did backup to somewhere, it's the only VM I've ever backed up. > > But, lets say I skip the large "old docs" file ; and wanted to migrate > my VMs to 4.0 , just which VMs would be translatable to 4.0 assuming > 4.0 is going to come out of the box with like Debian 9 and Fed 26? > > Am I/do people just back up AppVMs and mostly just for 3.2 ? or what am > I missing . I am a basic user as you can guess :) > My practice is to back up all my AppVM's and Dom0. The reason for the appVM's is that each one has specific docs along with specific customizations. I back up Dom0 because I store some scripts there. To my knowledge, backing up Dom0 only backs up the home directory, so I'd check the contents of your home directory in dom0 to see why you have 500Gb stuff stored there. I don't back up templates, as they are easily downloaded, and I don't back up trivial, easily creatable appVM's like my backupVM, which is essentially an empty placeholder for mounting external media. Hope this helps. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJaPpAvAAoJEOaMWwQFV9eFxrIQAJdhrgA5CfoMuVKisEQEfyuv v6c08hX9eVWo3Uz0mdXfzzGxGe5ixfxbLz4ZtGOwfKioljKJhkK7QCaBT7PCYTFG TrRdgp1lrxHcg0RTzdQLedRltMbYOlrStbGR+6YoZyhEkrIhGsG/hEEBCrdovavZ Xca2D3k8UHxJUxkGZ4SLJMjmkxGAIV+lsJnlWhPh1F0XsF/oZIJIye8n6A65HbMA 1sLeOslURUfo+nmg/mh9cFuwIMS+w7Xoy6qVxjd2SxygnqPkNHZsoiLU36kio5kf Ei9XfgYWlCNdIFBqnBWrSBeanepap3POCjv2uGcJ1AIY7KNu09SXxOdLSHOuVWvj nNKH7NmBwz7PILYBNYlf8uzipmEKGxX8IzNw0QVN5miGRi5RMbKTnxWt/3XocHiH Fw/NR5CEeCDmnsgM8AAyeTHlPh7k6W2QWSNnlA1Qx4hE12FZKJ6iJep3F+bFakE2 APBb7AAWU7+gYaeBCLsJ4g/vOxB/M32vHnM8kPDaa6WrC3g2cQpz1esJlvrXPOq0 c0KDxx66fp09K4ykuw3DvQH6yjDoPicYbnrvGI+8WzfdfvOgoeP2M3VajKM928/p MDK+Au7BO51qyCSmpeO5VZldLC8IxStWVtVEmQ41VYoyjOrrtx5OL4l8ub3QQbTg 71toB1pFBdieIUci2wvN =FIL2 -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/fc92f4b2-27dd-b41a-4c69-1451a4425fbc%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Constant pop-up from dom0 for qubes.gpg action
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/11/17 14:58, Sven Semmler wrote: > I just get started with R4 and restored my email vm. Everything works > > great, except that now everytime I am in the To: of Subject: line I get > a pop-up from dom0 asking: > > [dom0] Operation execution > > Do you want to allow the following operation? > Select the target domain and confirm with 'OK' > > Source: email > Operation: qubes.Gpg > Target: ... this is where I select 'vault' and click 'OK' > > After this, I get the prompt to allow GPG access that I am used to from > R3.2 (it's configured to allow for 500s). > > The problem is that the first / new prompt pops-up all the time and > makes entering To: and Subject: hell. > > I couldn't find any documentation. What can I do so I don't have to > select 'vault' all the time? > > All the steps of the original spit-gpg docu are followed. > > /Sven > > Did you ever get this fixed? I'm getting the same issue. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEElzlqqLTTc1W8vwlH5oxbBAVX14UFAlqI6rsACgkQ5oxbBAVX 14WOrA//VvrYJRZy2rXQc8HGbys23uy8/9giMiPRARdxjqSRTFmc9fTC0vH/rrCH 9SqOOSyroLlTi7+VMXgimTmfKpLkromcFJ2Zu2/xn5CQSD6BDKC7encSWnf15Hi6 CkiRaNJx+y4qdxPN/k9UbE+tJMrwly0ZHdfnKrREMX7OreSJdNCCCJJL2hDN4aXl 5zFYRk6qXSQzt6lmTxEB/DelkiKNRUj5XRjM9XXvV+6bEJhyBP0CNGkIqMTkE1Fx uihOZlEtophPnECkfWtc0vk/qOC58d5iF794m8N9REUX7hBGZ0Pg/siX8VWrFwfj 26ry32O9nLaR+WnTg9CGYufHVxgd64aClLkr34T5TZsxMp+k1cnOFXZmg4CZghUa fANLl254MXklYs6BXBnIqTT17PSOMtn32dzepHuY23Cg7xTkTAMZnVTqFQW0ATia 2F46mpIOJO3rJVYt5+h/Q/5fn35H18Ihsq5UUJdVOH9InaQEYHgu842Z8hq1gyi+ xLEw78p13WyjAs65DQvR/YSOMPU8OUK+hijc/BH7c6fjBzc0V34bOH+42SF8GHae BHJuQZ0v4LqJY8zWdRAi57skcvCmVeIf2iluJNzlKrK7WddQBtmeiZAyb2ce1MFX tAnK4un3cyiuF/vtOJy8h3eSP2XdASiNQyMrxGhJKmiYejMl83U= =Gqq1 -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/478ccd84-61f5-14ac-1c56-605c66d4a22a%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] DispVM starts and halts
On Sun, Oct 07, 2018 at 09:20:00AM +0300, Ivan Mitev wrote: > > > On 10/7/18 7:44 AM, Todd Lasman wrote: > >On 10/6/18 9:29 PM, Ivan Mitev wrote: > >> > >> > >>On 10/7/18 5:54 AM, Todd Lasman wrote: > >>>Help me troubleshoot this: > >>> > >>>When I launch a terminal from the menu using the fedora-28-dvm template, > >>>I get a message that disp407 is starting, disp407 has started, and > >>>disp407 has halted. No terminal comes up. > >>> > >>>However, if I launch the browser (Firefox), it works fine. > >>> > >>>If I run from dom0: > >>>$ qvm-run --dispvm=fedora-28-dvm --service qubes.StartApp+gnome-terminal > >>> > >>>I get exactly the same starting/started/halted sequence, and no error is > >>>reported. > >> > >>That's because gnome-terminal calls gnome-terminal-server and then > >>exits so the dispVM exits. See: > >> > >>https://github.com/QubesOS/qubes-issues/issues/2581#issuecomment-272664009 > >> > >> > >Thank you! This makes sense. I've taken the easier approach and just > >started using xterm, as the link suggests. > You may want to customize xterm to look like gnome-terminal (see the links > in a former ML post): > > https://groups.google.com/d/msg/qubes-users/rhp_jCrIO28/AcCk_G-CAwAJ > > Hope this helps ! > ivan > > -- > 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/cb2ef3a6-a298-3133-08e1-dc3b44e84f68%40maa.bz. > For more options, visit https://groups.google.com/d/optout. -- Even better - thanks 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/20181007185610.GA968%40d1stkfactory. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [qubes-users] DispVM starts and halts
On 10/6/18 9:29 PM, Ivan Mitev wrote: > > > On 10/7/18 5:54 AM, Todd Lasman wrote: >> Help me troubleshoot this: >> >> When I launch a terminal from the menu using the fedora-28-dvm template, >> I get a message that disp407 is starting, disp407 has started, and >> disp407 has halted. No terminal comes up. >> >> However, if I launch the browser (Firefox), it works fine. >> >> If I run from dom0: >> $ qvm-run --dispvm=fedora-28-dvm --service qubes.StartApp+gnome-terminal >> >> I get exactly the same starting/started/halted sequence, and no error is >> reported. > > That's because gnome-terminal calls gnome-terminal-server and then > exits so the dispVM exits. See: > > https://github.com/QubesOS/qubes-issues/issues/2581#issuecomment-272664009 > > Thank you! This makes sense. I've taken the easier approach and just started using xterm, as the link suggests. -- 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/aa750874-c472-ca5c-d25d-acb41f69d10a%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] DispVM starts and halts
Help me troubleshoot this: When I launch a terminal from the menu using the fedora-28-dvm template, I get a message that disp407 is starting, disp407 has started, and disp407 has halted. No terminal comes up. However, if I launch the browser (Firefox), it works fine. If I run from dom0: $ qvm-run --dispvm=fedora-28-dvm --service qubes.StartApp+gnome-terminal I get exactly the same starting/started/halted sequence, and no error is reported. -- 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/c185c87e-7c3f-4221-0802-90603331d311%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] i3 Tap to Click
I just can't get i3 to respect my synaptics touch to click! I've put this snippet in a variety of places (both in dom0 and the template), including: /etc/X11/xorg.conf.d/50-synaptics.conf /usr/share/X11/xorg.conf.d/50-synaptics.conf Section "InputClass" Identifier "touchpad catchall" Driver "synaptics" MatchIsTouchpad "on" Option "TapButton1" "1" EndSection Just can't get it to work. Any thoughts? I'm on Qubes 4.0, using a ThinkPad T430. Thanks. -- - Todd Lasman GPG: AE5D 3FBC 304F 1C8C 5266 2871 BA94 2436 95B3 58F4 -- 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/20181213163534.GA20708%40d1stkfactory. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [qubes-users] i3 Tap to Click
Works! Thanks! On 12/13/18 9:16 AM, Sven Semmler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 12/13/18 10:35 AM, Todd Lasman wrote: >> Just can't get it to work. Any thoughts? I'm on Qubes 4.0, using a >> ThinkPad T430. > I'm using Qubes R4 with I3 on a ThinkPad P51 and got it to work. > Attached is my /etc/X11/xorg.conf.d/99-synaptics-overrides.conf > (contains all variations I found, one of them makes it work ... didn't > spend time to figure out which). > > /Sven > > > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlwSlAUACgkQ2m4We49U > H7YY+hAAs0DDhEUieBm1frnaJncjksyQ5Unz1/AqFcQ7D46PwnNwSWE9ZvB0+P/E > yyiEA7ACfarbD7FQselzhVNyaWAgNS6NLZIfqP3+JBkQ6C9IM+TWt8JQmZRj1mSZ > O1zi+m/CrcoaiZvM7THv7Wo7qOIZCNY06dU4cOoml2FzcQbkMX1J9H5+4p/KSvh0 > B/ogCdTWcau3BoPp0+4f6MtvspsZcX1nQCA9gVPlWBQK94FfwRgXs5lMl2W09X7c > mIvot2i09nmN8dTJ+axQ4fRkq1KQuWJH8qlTgxnpyCkIUnX4X73lBrcfdjWaU4KW > Vw/68tbLzsNBvrc5+nkgRuHoa7F7k9olUnK5h3TSDzuD4Q8diCrxIEjWq/4wM4vu > U/Omly990L7/Ta9AJrmAAL38E+0gidmqEMxL4R3DeUFeDkVQZ6vU3oYuahRq5+hG > gtRSlPYYgQFPFBNxaRTzcVAkZP8Hds/oonLkIks4fROkmlBI7KHJG5jwHQ2hScN1 > GGbz0/Qy1ZOaVqsIwE0KQGfM/8CFyDbhra1CTGVsgu2waKm8dY5cfdE9RufneKQm > QhTZtyPcZvy2JmHplKLsE5hDin4E+jFvjlNzVz5RMfp36Zw5lWvteh1Nc5mEGUlI > VtMMevpgZt6/mNOclS4B3+/LOxpUmFYH02N4LbXxH3NaIuoYAOU= > =2xrT > -END PGP SIGNATURE- > -- *Todd E. Lasman, MD, FCCP* GPG: 0xBA94243695B358F4 <http://pgp.mit.edu/pks/lookup?op=get=0xBA94243695B358F4> -- 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/94043da0-c662-12a6-c5ba-10ac008d16f3%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] qvm-copy-to-vm question
I'm not sure if I'm doing this correctly. According to the usage, the syntax is: qvm-copy-to-vm destination_qube_name FILE When I do this, I get a dialog that asks me which qube I want to copy my file to. Why have this, if I already specified it in the command line? Is there a way to suppress the dialog? And if not, what's the purpose of having the destination_qube_name in the command line in the first place? I'm told that some use qvm-copy instead of qvm-copy-to-vm. Whenever I use the qvm-copy command (with the destination qube and the file to copy) I always get the error message "Can't stat destination_qube. File or directory doesn't exist (or something like that)" All I want to do is copy a file from one qube to the next without hassle. Suggestions? Thanks! Todd -- 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/20190213015855.GA2093%40d1stkfactory. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [qubes-users] qvm-copy-to-vm question
On 2/13/19 3:18 PM, 'awokd' via qubes-users wrote: Todd Lasman wrote on 2/13/19 1:58 AM: I'm not sure if I'm doing this correctly. According to the usage, the syntax is: qvm-copy-to-vm destination_qube_name FILE This is for copies from dom0 only. When I do this, I get a dialog that asks me which qube I want to copy my file to. Why have this, if I already specified it in the command line? Is there a way to suppress the dialog? And if not, what's the purpose of having the destination_qube_name in the command line in the first place? 3.2 used to permit the destination_qube_name in there, but 4.0+ doesn't. I'm told that some use qvm-copy instead of qvm-copy-to-vm. Whenever I use the qvm-copy command (with the destination qube and the file to copy) I always get the error message "Can't stat destination_qube. File or directory doesn't exist (or something like that)" All I want to do is copy a file from one qube to the next without hassle. Suggestions? From a terminal session inside the source qube, use "qvm-copy [filename]". It will then prompt for the destination qube. Ok. Thanks for the explanation. Still doesn't seem right to me, though. I think I should be able to do the whole copy/move with one command, rather than two. Todd -- 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/121c723b-f734-dd12-7073-f2cb6a86ca2f%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qvm-copy-to-vm question
On 2/14/19 7:12 AM, unman wrote: > On Wed, Feb 13, 2019 at 08:12:42PM -0800, Todd Lasman wrote: >> On 2/13/19 3:18 PM, 'awokd' via qubes-users wrote: >>> Todd Lasman wrote on 2/13/19 1:58 AM: >>>> I'm not sure if I'm doing this correctly. >>>> O >>>> qvm-copy-to-vm destination_qube_name FILE >>>> All I want to do is copy a file from one qube to the next without >>>> hassle. Suggestions? > You can suppress the prompt by setting rules in > /etc/qubes-rpc/policy/qubes.Filecopy > So if you have in that file: > qube1 qube2 allow > In qube1 you can use qvm-move-to-vm qube2 foo and no prompt will appear. > > The prompt appears because either you have not specified a target qube > or you have not given appropriate permissions. > > unman > I understand. Thanks all, for the explanation (security), and the potential for setting rules. Todd -- 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/c110ccec-7b7d-e5e9-adbe-238e231de2c2%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Anyone using protonmail-bridge
For anyone using protonmail-bridge with thunderbird: What kind of settings are you using to allow sending/receiving through the firewall? I've allowed protonmail.com and 127.0.0.1 (which is the address the bridge uses), but when the firewall is activated, I can't send or receive anything. Turning the firewall off allows normal operation. Thanks. Todd -- 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/df98d1e9-3170-22a1-4c0c-db01f433154d%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Re: Anyone using protonmail-bridge
On 2/14/19 11:55 AM, 22...@tutamail.com wrote: > Would appreciate any thoughts on your set-up but try the following: > > In the appvm that houses your thunderbird and protonmail bridge add > protonmails IP(= 185.70.40.151) in the firewall settings. I have managed to > get it working by further limiting it to port 443 only. > > As I understand the workings of protonmail bridge and Qubes, since the bridge > is in the same appvm as your thunderbird, 127.0.0.1 is all done within the > appvm so it never crosses the firefall. > > I am not sure of your setup but as I have used it as follows: > > Thunderbird/protonmail bridge Appvm (firewall limited to 185.70.40.151) -> > Firewall -> NetVM > > or > > Thunderbird/protonmail bridge Appvm (firewall limited to 185.70.40.151) -> > Whonix-GW -> Firewall -> NetVM > > I might submit a seperate question but how do you update the bridge in your > current Appvm? Protonmail just updated bridge, in the past I have rebuilt my > appvm but there must be an easier way to upgrade the bridge? > > I hope that helps... > Thanks for your help. I'll try this method for getting through the firewall. Regarding updating the bridge: my email VM is based on a fedora clone. In that clone, I've just installed the newest version (1.1.1) of the protonmail-bridge, which I had to download manually from the protonmail site. -- 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/e10bc00b-6bfb-e07c-cf70-96e8fd52c493%40nowlas.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Unable to update dom0
Any advice on this error I'm getting when trying to update dom0? https://mirror.linux.pizza/qubes-os.org/repo/yum/r4.0/current/dom0/fc25/rpm/xen-runtime-4.8.5-5.fc25.x86_64.rpm: [Error 14] HTTPS Error 416 - Requested Range not Satisfiable Trying other mirror. This error appears for all the mirrors for each xen-***.rpm file. I note that the files have downloaded normally, however, in /var/lib/qubes/dom0-updates/packages/ Thanks for any help! - Todd Lasman GPG: AE5D 3FBC 304F 1C8C 5266 2871 BA94 2436 95B3 58F4 -- 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/20190504175956.GA14067%40d1stkfactory. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
