[qubes-users] Re: How to deal with Yubikey ?

2018-01-31 Thread ThierryIT
There is no sys-usb and I do not have installed qubes-usb-proxy 

Le mercredi 31 janvier 2018 16:10:08 UTC+2, ThierryIT a écrit :
> Hi,
> 
> I have moved from R3.2 to 4.0R3.
> And I am still dealing with the same problem, and I don't know if for 4.0R3 
> the documentation provided is still updated.
> All my Keys are detected by dom0:
> 
> Device dom0:4-2 - Neowave_Keydo-AES_0989876... is available
> Device dom0:sdd - Keydo-AES () available
> Device dom0:sdf - Keydo-AES ()( is available
> Device dom0:sdf1 - Keydo-AES (PUBLIC) is available
> 
> This key has two fuction as auth key (github ...) and an public and an  
> encrypted folder
> 
> I am using it to log to Github and to my Registar under Windows.
> 
> So for a Qubes 4.0R3 how to do ?
> 
> Thx
> 
> Le jeudi 25 janvier 2018 13:37:56 UTC+2, rob_66 a écrit :
> > On Mon, 22 Jan 2018 22:47:55 -0800 (PST)
> > ThierryIT  wrote:
> >  
> > > I have today to deal with two problems:
> > > 
> > > 1) I am using Yubikey to be authentified on some web site like
> > > Github ... 2) I am using Yubikey to stock my PGP keys and to use them
> > > with mainly my emails (Thinderbird+Enigmail)
> > > 
> > > What to do under Qubes to make this possible ?
> > > I have already sys-usb running. 
> > 
> > Hi.
> > 
> > I studied and followed
> > https://mig5.net/content/yubikey-2fa-qubes-redux-adding-backup-key as
> > well as https://mig5.net/content/yubikey-challenge-response-mode-qubes
> > and it works perfectly fine on Qubes 3.2, Fedora 26. And my skills
> > are mediocre. 
> > 
> > (Sending *63* bits, »variable«, you'll recognize later.)
> > 
> > However, Qubes' own tutorial can, of course, work flawlessly with your
> > set-up:
> > 
> > https://www.qubes-os.org/doc/yubi-key/
> > 
> > If you like to dig in deeper, see the discussions on Github: 
> > 
> > https://www.qubes-os.org/doc/yubi-key/
> > 
> > Best regards,
> > r.

-- 
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/2c4d60cc-a503-4ed9-9987-b5e93bfcf8b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How to deal with Yubikey ?

2018-01-31 Thread ThierryIT
Hi,

I have moved from R3.2 to 4.0R3.
And I am still dealing with the same problem, and I don't know if for 4.0R3 the 
documentation provided is still updated.
All my Keys are detected by dom0:

Device dom0:4-2 - Neowave_Keydo-AES_0989876... is available
Device dom0:sdd - Keydo-AES () available
Device dom0:sdf - Keydo-AES ()( is available
Device dom0:sdf1 - Keydo-AES (PUBLIC) is available

This key has two fuction as auth key (github ...) and an public and an  
encrypted folder

I am using it to log to Github and to my Registar under Windows.

So for a Qubes 4.0R3 how to do ?

Thx

Le jeudi 25 janvier 2018 13:37:56 UTC+2, rob_66 a écrit :
> On Mon, 22 Jan 2018 22:47:55 -0800 (PST)
> ThierryIT  wrote:
>  
> > I have today to deal with two problems:
> > 
> > 1) I am using Yubikey to be authentified on some web site like
> > Github ... 2) I am using Yubikey to stock my PGP keys and to use them
> > with mainly my emails (Thinderbird+Enigmail)
> > 
> > What to do under Qubes to make this possible ?
> > I have already sys-usb running. 
> 
> Hi.
> 
> I studied and followed
> https://mig5.net/content/yubikey-2fa-qubes-redux-adding-backup-key as
> well as https://mig5.net/content/yubikey-challenge-response-mode-qubes
> and it works perfectly fine on Qubes 3.2, Fedora 26. And my skills
> are mediocre. 
> 
> (Sending *63* bits, »variable«, you'll recognize later.)
> 
> However, Qubes' own tutorial can, of course, work flawlessly with your
> set-up:
> 
> https://www.qubes-os.org/doc/yubi-key/
> 
> If you like to dig in deeper, see the discussions on Github: 
> 
> https://www.qubes-os.org/doc/yubi-key/
> 
> Best regards,
> r.

-- 
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/4f9b9c15-76d1-4e2e-97b8-0f1c28ff6a6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How to deal with Yubikey ?

2018-01-25 Thread rob_66
On Mon, 22 Jan 2018 22:47:55 -0800 (PST)
ThierryIT  wrote:
 
> I have today to deal with two problems:
> 
> 1) I am using Yubikey to be authentified on some web site like
> Github ... 2) I am using Yubikey to stock my PGP keys and to use them
> with mainly my emails (Thinderbird+Enigmail)
> 
> What to do under Qubes to make this possible ?
> I have already sys-usb running. 

Hi.

I studied and followed
https://mig5.net/content/yubikey-2fa-qubes-redux-adding-backup-key as
well as https://mig5.net/content/yubikey-challenge-response-mode-qubes
and it works perfectly fine on Qubes 3.2, Fedora 26. And my skills
are mediocre. 

(Sending *63* bits, »variable«, you'll recognize later.)

However, Qubes' own tutorial can, of course, work flawlessly with your
set-up:

https://www.qubes-os.org/doc/yubi-key/

If you like to dig in deeper, see the discussions on Github: 

https://www.qubes-os.org/doc/yubi-key/

Best regards,
r.


-- 
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/20180125113702.770c2005.robotico%40posteo.es.
For more options, visit https://groups.google.com/d/optout.