| Age | Commit message (Collapse) | Author |
|---|
|
|
|
will find them, and devname() in various programs won't return "??"
ok kettenis
|
|
|
|
it's only accessible to root:wheel.
ok deraadt@
|
|
|
|
eight to sixteen. It's quite easy to be able to create that many LDOMs on
the newer machines.
Help making the change in the right place from Miod and otto@
ok kn@ "looks fine" deraadt@
|
|
We used to have different numbers of blowfish rounds between the
default and daemon classes in login.conf. On Jun 26, 2016, tedu
committed "upgrade selected login.conf to use auto rounds for bcrypt"
for amd64, sparc64, i386, and maccpc.
Since the class daemon inherits from the default class, the
:localcipher=blowfish,a:\
is a duplicate.
ok millert@ deraadt@ sthen@
|
|
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn
|
|
|
|
ok deraadt
|
|
|
|
|
|
|
|
with help from claudio@
|
|
|
|
|
|
|
|
While FIDO/U2F keys were already supported by the generic uhid(4)
driver, this driver adds the first step to tighten the security of
FIDO/U2F access. Specifically, users don't need read/write access to
all USB/HID devices anymore and the driver also improves integration
with pledge(2) and unveil(2): It is pledge-friendly because it doesn't
require any ioctls to discover the device and unveil-friendly because
it uses a single /dev/fido/* directory for its device nodes.
It also allows to support FIDO/U2F in firefox without further
weakening the "sandbox" of the browser. Firefox does not have a
proper privsep design and many operations, such as U2F access, are
handled directly by the main process. This means that the browser's
"fat" main process needs direct read/write access to all USB HID
devices, at least on other operating systems. With fido(4) we can
support security keys in Firefox under OpenBSD without such a
compromise.
With this change, libfido2 stops using the ioctl to query the device
vendor/product and just assumes "OpenBSD" "fido(4)" instead. The
ioctl is still supported but there was no benefit in obtaining the
vendor product or name; it also allows to use libfido2 under pledge.
With feedback from deraadt@ and many others
OK kettenis@ djm@ and jmc@ for the manpage bits
|
|
|
|
responsive during packages compilation, especially on slower machines.
feedback welcome from people building ports
discussed with deraadt@
|
|
|
|
|
|
some cases also the serial console) such that X can use it as its VT
when running without root privileges.
ok jsg@, matthieu@
|
|
ok semarie@
|
|
|
|
|
|
|
|
on ttyC0. While here add drm0 to loongson and add the complete set of
wscons and drm devices to arm64.
ok kettenis@
|
|
|
|
ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
raising openfiles-cur above the implicit -max value (1024 on at least the
common arch) results in the setting not being applied at all.
Earlier version OK tom@ danj@ ajacoutot@ benno@ krw@ beck@, suggestion about
openfiles= from millert@ - changes in this version are to use 1024 for -max
rather than 512 to avoid changing the existing hard limit, and just use
openfiles= for bgpd/unbound where max and cur are the same value.
|
|
|
|
matter much -- and "uucp" is just stupid in 2016.
ok rpe
|
|
|
|
|
|
|
|
While here, also remove two forgotten descriptions for long obsolete
devices.
|
|
|
|
ok deraadt@ yasuoka@ reyk@
|
|
already does this, so we don't want to go backwards on password changes.
ok krw
|
|
|
|
|
|
unused for now, but I plan to convert all programs in base to use it in
a future diff. /dev/bpf0 is for compatibility with existing binaries
and is to be removed after a transition period.
ok rpe krw, for the installer part
"Let's see it hit the tree." deraadt
|
|
|
