Date: Wed, 5 Sep 2018 10:41:04 +0930 From: "O'Connor, Daniel" <darius@dons.net.au> To: Robert Ames <robertames@hotmail.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: Yubico Security Keys Message-ID: <1AEEDB86-DF6B-433B-A413-452F105D9A53@dons.net.au> In-Reply-To: <SN6PR08MB50700E8EAFDEDA7646671E6EC9030@SN6PR08MB5070.namprd08.prod.outlook.com> References: <SN6PR08MB50700E8EAFDEDA7646671E6EC9030@SN6PR08MB5070.namprd08.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 5 Sep 2018, at 08:33, Robert Ames <robertames@hotmail.com> wrote: > FreeBSD sees the device: >=20 > Sep 4 17:25:13 freebsd kernel: ugen1.4: <Yubico Security Key by = Yubico> at usbus1 > Sep 4 17:25:13 freebsd kernel: uhid0 on uhub4 > Sep 4 17:25:13 freebsd kernel: uhid0: <Yubico Security Key by Yubico, = class 0/0, rev 2.00/5.02, addr 4> on usbus1 >=20 > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1AEEDB86-DF6B-433B-A413-452F105D9A53>