Re: Yubico Security Keys

> On 5 Sep 2018, at 12:43, Robert Ames wrote: >>> On 5 Sep 2018, at 08:33, Robert Ames wrote: >>> FreeBSD sees the device: >>> >>> Sep 4 17:25:13 freebsd kernel: ugen1.4: at >>> usbus1 >>> Sep 4 17:25:13 freebsd kernel: uhid0 on uhub4 >>> Sep 4 17:25:13 freebsd kernel: uhid0: >> class

RE: Yubico Security Keys

> > On 5 Sep 2018, at 08:33, Robert Ames wrote: > > FreeBSD sees the device: > > > > Sep 4 17:25:13 freebsd kernel: ugen1.4: at > > usbus1 > > Sep 4 17:25:13 freebsd kernel: uhid0 on uhub4 > > Sep 4 17:25:13 freebsd kernel: uhid0: > class 0/0, rev 2.00/5.02, addr 4> on usbus1 > > > > So

Re: Yubico Security Keys

> On 5 Sep 2018, at 08:33, Robert Ames wrote: > FreeBSD sees the device: > > Sep 4 17:25:13 freebsd kernel: ugen1.4: at > usbus1 > Sep 4 17:25:13 freebsd kernel: uhid0 on uhub4 > Sep 4 17:25:13 freebsd kernel: uhid0: 0/0, rev 2.00/5.02, addr 4> on usbus1 > > So should this just work

Yubico Security Keys

I just upgraded to 11.2-RELEASE with Firefox 60.0.1_1,1 from packages. It's my understanding Yubico Security Keys should be supported (I have one of the blue ones).  In Firefox I did about:config and set security.webauth.u2f to true.  When I go to https://demo.yubico.com/u2f to test it, the

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 --- Comment #12 from rkober...@gmail.com --- (In reply to Kubilay Kocak from comment #10) No, virtualbox-ose is not the problem and there is no reason to build it. It is virtualbox-ose-kmod that requires a build against an 11.2-RELEASE

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 Dennis Clarke changed: What|Removed |Added CC||dcla...@blastwave.org --- Comment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210726

Hi All I was hoping someone could have a look at this long standing bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210726 It's ephemeral port clash when you have multiple jails with the same IP address, I've tested with 11.1 and 11.2 and the patch does fix the issue Could someone please

Re: bad hash in repo

Hello I have exactly the same problem : 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect hash. I ve updated several 10.4 to 11.1 without problem near march/april. In august, the same update failed on another 10.4 Today, here is the situation : 10.4to