[qubes-users] Using virt-viewer for remote systems

2016-09-12 Thread Konstantin Ryabitsev
Greetings:

I need to be able to use virt-viewer to access remote systems (e.g. virt-viewer 
--connect qemu+ssh://some.host/system vm-name), and it would appear that it's 
impossible to install due to conflicts:

# dnf install virt-viewer
Error: package virt-viewer-2.0-2.fc23.x86_64 requires libvirt.so.0()(64bit), 
but none of the providers can be installed
(try to add '--allowerasing' to command line to replace conflicting packages)

If I do add --allowerasing it will want to remove qubes-gui-vm and 
xen-qubes-vm, which seems like it would do bad things.

Any suggestions how I could get virt-viewer installed without clobbering other 
stuff?

-K

-- 
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/58176a91-dcc0-4931-9a92-1c84e4e8ff65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] R3.2_rc3.iso Corrupt Download?

2016-09-16 Thread Konstantin Ryabitsev
On Fri, Sep 16, 2016 at 11:41:30AM +, amadaus wrote:
> I have downloaded Qubes R3.2-rc3 iso and in the course of verifying
> signatures received the following output:
> [user@rubbish ~]$ gpg -v --verify
> '/home/user/Downloads/Qubes-R3.2-rc3-x86_64.iso.asc'
> '/home/user/Downloads/Qubes-R3.2-rc3-x86_64.iso'
> gpg: armor header: Version: GnuPG v2
> gpg: Signature made Wed 31 Aug 2016 01:08:18 PM BST using RSA key ID
> 03FA5082
> gpg: using PGP trust model
> gpg: Good signature from "Qubes OS Release 3 Signing Key"
> gpg: binary signature, digest algorithm SHA256
> [user@rubbish ~]$ gpg --list-sig 03FA5082
> pub   4096R/03FA5082 2014-11-19
> uid  Qubes OS Release 3 Signing Key
> sig  36879494 2014-11-19  Qubes Master Signing Key
> sig 3E2986940 2016-01-04  [User ID not found]
> sig 303FA5082 2014-11-19  Qubes OS Release 3 Signing Key
> 
> As you can see signature E2986940 is unknown. I imported this key, it
> belongs to "Kabine Diane <kabi...@me.com>"
> This seems very suspicious. Should I delete the iso and try a fresh
> download?

Anyone can sign anyone's key and upload it to the keyservers. A presence
of an unknown signature on a key doesn't invalidate it in any way. As
long as there is a signature you do trust (DDFA1A3E36879494), the key is
valid.

Regards,
-- 
Konstantin Ryabitsev
Linux Foundation Collab Projects
Montréal, Québec

-- 
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/20160916121846.GA2126%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature


[qubes-users] Chrome update fixes "you're always logged out" bug

2016-12-02 Thread Konstantin Ryabitsev

Hi, all:

A chrome update came out today, and looks like it finally carries the 
fix for the annoying "you're always logged out of everything at the 
start of each session" bug:


https://bugs.chromium.org/p/chromium/issues/detail?id=631171

The version of chrome you need is 55.0.2883.75.

This should certainly make for a much more pleasant experience.

-K

--
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/20161203021653.GB2925%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature


[qubes-users] Yubikey with smartcard and HOTP together

2018-02-06 Thread Konstantin Ryabitsev
Hi, all:

This is a different and a more nuanced problem than recently discussed,
and I'm not sure if there's a solution, but I wanted to ask. :)

Yubikey-4 can act in multiple capacities:

- Smartcard
- U2F device
- HOTP

HOTP functionality is really just a keyboard and registers with Linux as
such (USB keyboard). With 3.2 I was attaching the USB controller
directly to the VM where I was doing the work that required the
smartcard/HOTP functionality and both worked just fine. With 4.0 I
created a separate sys-usb VM and it seems I can use only one or the
other, not both.

When I plug in the yubikey, it registers correctly and I get a pop-up
notification that it's available to be used. At that point, I am able to
use HOTP-press without needing to attach the device to my work vm
(because it's a "keyboard"). However, if I want to use the smartcard
functionality, I have to assign the device to the work VM -- and gnupg
interacts with it correctly. However, once I do that, I am no longer
able to use HOTP -- pressing the button does nothing.

Any ideas if this is fixable at all, or is it the downside of the way
USB devices are assigned with usb-proxy?

Best,
-- 
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation

-- 
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/0f889341-850c-23ba-8286-4b091bd2529b%40linuxfoundation.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature


[qubes-users] If you get "no authenticators available" with mutt

2018-02-09 Thread Konstantin Ryabitsev
If you are trying to use mutt with the default Fedora-26 template and 
can't figure out why authenticated smtp sending is giving you a "No 
Authenticators Available" error, you need to install cyrus-sasl-plain.


Drove me half-mad before I figured that out. Hopefully it saves you a 
bunch of clicks (and hair).


-K

--
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/20180209173217.GB1243%40work.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature