On Sun, 18 Feb 2018 22:04:52 +0100
Nicolas Dandrimont wrote:
> Recent versions of Firefox (Firefox Quantum, i.e. 57+) support u2f if
> you turn the right knob on in about:config. More details:
> https://www.yubico.com/2017/11/how-to-navigate-fido-u2f-in-firefox-quantum/
It's nice suggestion, tha
On Wed, Feb 21, 2018 at 10:24:52AM +0100, Philipp Kern wrote:
> FWIW a future version of the proprietary google-chrome-* will pick up
> libu2f-udev as a recommends as well - probably with M66 somewhen in late
> April, early May. It now landed on Chromium master. If you think it needs to
> be pushed
On 2018-02-18 13:49, Bastian Blank wrote:
On Sun, Feb 18, 2018 at 10:08:39AM +0900, Hideki Yamane wrote:
On Sat, 17 Feb 2018 19:32:09 +0100
Bastian Blank wrote:
> And chromium does not recommends that at all.
Really? What's wrong with it, I'm curious.
Well, if you need something, in this case
On Sun, Feb 18, 2018 at 8:49 PM, Bastian Blank wrote:
> Well, if you need something, in this case some udev rules to actually
> be able to access the hardware, then you should recommend it. And as
> chromium does not pull in the library, then somehow it needs to get the
> udev rules.
Alternately
* Hideki Yamane [2018-02-18 10:08:39 +0900]:
> Hi,
>
> On Sat, 17 Feb 2018 13:10:50 -0500
> Robert Edmonds wrote:
> > I ran into the same problem. It looks like it was due to #889665 being
> > fixed and not having the libu2f-udev package installed.
>
> This fixes the problem, thanks Robert!
>
On Sun, Feb 18, 2018 at 10:08:39AM +0900, Hideki Yamane wrote:
> On Sat, 17 Feb 2018 19:32:09 +0100
> Bastian Blank wrote:
> > And chromium does not recommends that at all.
> Really? What's wrong with it, I'm curious.
Well, if you need something, in this case some udev rules to actually
be able
Hi,
On Sat, 17 Feb 2018 13:10:50 -0500
Robert Edmonds wrote:
> I ran into the same problem. It looks like it was due to #889665 being
> fixed and not having the libu2f-udev package installed.
This fixes the problem, thanks Robert!
On Sat, 17 Feb 2018 19:32:09 +0100
Bastian Blank wrote:
> And
On Sat, Feb 17, 2018 at 01:10:50PM -0500, Robert Edmonds wrote:
> I ran into the same problem. It looks like it was due to #889665 being
> fixed and not having the libu2f-udev package installed.
And chromium does not recommends that at all.
Bastian
--
The heart is not a logical organ.
Hideki Yamane wrote:
> Hi,
>
> Today, I've tried to login salsa.debian.org, 2FA doesn't work well
> (and on github, too). It works several days ago.
>
> The message on salsa is
> >>There was a problem communicating with your device. (error code: 1)
>
> On my desktop (sid)
> - chrome / chrom
Hi,
Today, I've tried to login salsa.debian.org, 2FA doesn't work well
(and on github, too). It works several days ago.
The message on salsa is
>>There was a problem communicating with your device. (error code: 1)
On my desktop (sid)
- chrome / chromium / chrome-unstable doesn't work
- wit
10 matches
Mail list logo