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 0/0, rev 2.00/5.02, addr 4> on usbus1 >>> >>> So should this just work out of the box or is there something I'm >>> missing? >> >> Hi Robert, >> I don't have any Yubikeys but have you tried checking the permissions of >> /dev/uhid0* and /dev/ugen1.4 (which will be a symlink to usb/1.4.0) ? >> You can chmod them for now and then if that works have a devd conf or devfs >> rule which sets the permissions appropriately when the device is connected. >> >> If permissions are the problem it would be nice to see if the error message >> can be improved too :) >> >> -- >> Daniel O'Connor > > I had done a manual chmod 777 /dev/usb/1.4.0 but had overlooked /dev/uhid0. > Once I did a chmod 777 on that it worked. Thank you. Any suggestions on the > best way to add a devd conf or devfs rule for this thing? Add this to /etc/devfs.conf.. [root=100] add path 'uhid*' group users mode 660 (Assuming your user is in the 'users' group - adjust to taste, devfs(8) has the details) And this to /etc/rc.conf.. devfs_system_ruleset="root" Then do.. sudo service devfs restart And unplug/replug the key. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
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 should this just work out of the box or is there something I'm > > missing? > > Hi Robert, > I don't have any Yubikeys but have you tried checking the permissions of > /dev/uhid0* and /dev/ugen1.4 (which will be a symlink to usb/1.4.0) ? > You can chmod them for now and then if that works have a devd conf or devfs > rule which sets the permissions appropriately when the device is connected. > > If permissions are the problem it would be nice to see if the error message > can be improved too :) > > -- > Daniel O'Connor I had done a manual chmod 777 /dev/usb/1.4.0 but had overlooked /dev/uhid0. Once I did a chmod 777 on that it worked. Thank you. Any suggestions on the best way to add a devd conf or devfs rule for this thing? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
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 out of the box or is there something I'm > missing? Hi Robert, I don't have any Yubikeys but have you tried checking the permissions of /dev/uhid0* and /dev/ugen1.4 (which will be a symlink to usb/1.4.0) ? You can chmod them for now and then if that works have a devd conf or devfs rule which sets the permissions appropriately when the device is connected. If permissions are the problem it would be nice to see if the error message can be improved too :) -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
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 "Register a U2F device" fails with:
Registration failed!
Make sure you have a U2F device connected, and try again.
Traceback (most recent call last):
File "/root/python-u2flib-server-demo/examples/yubiauth_server.py", line 161,
in __call__
raise Exception("FIDO Client error: %s" % error)
Exception: FIDO Client error: 4 (DEVICE INELIGIBLE)
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: on usbus1
So should this just work out of the box or is there something I'm
missing?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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 kernel. It is small, takes seconds to build and install. NOTE! You must have sources for 11.2-RELEASE on you system when you build it. The version of the kmod must match the version of virtualbox-ose exactly. If you install the package of virtualbox-ose and then build and install virtualbax-ose-kmod of the same version, you will be ready to go. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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 #11 from Dennis Clarke --- The build process for virtualbox-ose is fraught with problems. At least from 'ports' where multiple little bugs seem to exist. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
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 point me in the right direction to get this merged? and apologies if this this the wrong place to ask! Thanks Dave ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
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 11.2 OK 10.4to 11.1 10477 has incorrect hash 11.1p10 to 11.2 10477 has incorrect hash 11.1p10 to 11.1 10477 has incorrect hash # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. Fetching 2 patches.. done. Applying patches... done. Fetching 2 files... 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect hash. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
