On Thu, Sep 06, 2018 at 01:48:10PM +0200, Niclas Zeising wrote:
> > Yes, that works (using /etc/devfs.rules). Thanks. I also got it to work
> > using /etc/devd.conf
> >
> > # Yubico Security Key
> > attach 100 {
> > match "vendor" "0x1050";
> > match "product" "0x0120";
> >
On Wed, Sep 05, 2018 at 01:00:20PM +0930, O'Connor, Daniel wrote:
> > 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: ug
> > 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
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
In 10.2-RELEASE running "calendar -a" as root fails when user calendar files
have a #include line. This worked in 10.0-RELEASE (and before). From my
limited testing I think it's looking for the included files relative to root's
home directory and not the user's home directory. The svn
Trying to get caught up on some of the recent Errata Notices and I'm
having problems with FreeBSD-EN-15:06.file on 9.3-RELEASE.
# cd /usr/src
# patch /tmp/file-9.3.patch
After successfully applying hundreds of patches, it eventually
fails with
Hmm... The next patch looks like a unified diff
From: M.Hirsch [EMAIL PROTECTED]
I had the same problem with 6.1. But only on some occasions, not always
(iirc).
The installations I made over the last weeks had all very different
environments and deployment methods.
I can't tell anymore when it happens and when not because I simply added
I have an ancient machine that used to run 5.4-RELEASE. I installed
6.1-RELEASE and since the install the kernel has trouble finding
the root filesystem when it boots and prompts me for it each time. After
I type in the root filesystem specification at the mountroot prompt
it boots up and runs
