22:13 cpm 

www/chromium: update to 64.0.3282.186

Changelog:
https://chromium.googlesource.com/chromium/src/+log/63.0.3239.132..64.0.3282.186?pretty=fuller&n=10000

MFH:		2018Q1
Security:	https://vuxml.freebsd.org/freebsd/8e986b2b-1baa-11e8-a944-54ee754af08e.html
Security:	https://vuxml.freebsd.org/freebsd/abfc932e-1ba8-11e8-a944-54ee754af08e.html

 

18:51 rene 

www/chromium: update to 63.0.3239.132

Submitted by:	cpm
Obtained from:	https://github.com/cpu82/freebsd-chromium
MFH:		2018Q1
Security:	https://vuxml.freebsd.org/freebsd/e264e74e-ffe0-11e7-8b91-e8e0b747a45a.html
Security:	https://vuxml.freebsd.org/freebsd/1d951e85-ffdb-11e7-8b91-e8e0b747a45a.html
Security:	https://vuxml.freebsd.org/freebsd/82894193-ffd4-11e7-8b91-e8e0b747a45a.html
Security:	https://vuxml.freebsd.org/freebsd/f8e72cd4-c66a-11e7-bb17-e8e0b747a45a.html
Security:	https://vuxml.freebsd.org/freebsd/3cd46257-bbc5-11e7-a3bc-e8e0b747a45a.html
Security:	https://vuxml.freebsd.org/freebsd/a692bffe-b6ad-11e7-a1c2-e8e0b747a45a.html

 

05:44 gonzo 

www/chromium: add support for USB U2F devices

Implement enough of chrome.hid API to make U2F security keys work.

Due to FreeBSD's HID API limitations it's not possible to consistently
report vedor id or product id values for HID devices so if javascript
library relies on this information to detect supported keys it won't
work, only report descriptor based detection works.

Also by default uhid(4) devices accessible only to root user, current
solution is to change /dev/uhidX node permission using devd. For example
create /usr/local/etc/devd/yubi.conf with following content and
restart devd:

attach 20 {
  match "vendor" "0x1050";
  action "/bin/chmod 766 /dev/$device-name";
};

Work on u2f-devd port is in progress (see PR). When done it will take
care of maintaining devd rulesets for U2F devices.

PR:		196754
Approved by:	cpm