Age | Commit message (Collapse) | Author |
|
This way rc.d and rcctl don't suffer from side effects in people's rc
files. If you somehow used those files to set environment variables,
you should have used login.conf as described in rc.d(8) instead.
ok ajacoutot@
|
|
|
|
it's only accessible to root:wheel.
ok deraadt@
|
|
|
|
|
|
|
|
ok claudio@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The freedb.org CD track database has been discontinued.
Retire cddb/888 from /etc/services. Nothing uses this any longer.
gnudb.org uses the "cddbp-alt" port of 8880, but we don't need a
services(5) entry for a single site.
ok deraadt@
|
|
ok deraadt@
|
|
Tested on a Cubieboard2.
OK patrick@
|
|
OK deraadt@, patrick@
|
|
store radius passwords and nothing requires it to be group readable.
ok yasuoka@
|
|
ok kn gsoares
|
|
from Matt Dunwoodie and Jason A. Donenfeld
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@
|
|
backslash at the end for line continuation
Breaking long lines into multiple ones must still be possible and does
require to treat the backslash as an escape character.
Breakage reported by Mark Patruck <mark at wrapped dot cx >, thanks!
---
distrib/miniroot/install.sub revision 1.1151
etc/netstart revision 1.203
date: 2020/05/21 11:54:41; author: kn; state: Exp; lines: +2 -2;
Do not treat backslashe as an escape character in hostname.if(5) lines
ifstart() should always pass such lines unaltered, especially if they
contain "nwid" or "description" lines with arbitrary strings.
<bsdlisten at gmail dot com> reported SSIDs such as "Mike's" during
installation end as broken; this was because the installer escaped
the single quote using backslashes which ended up being treated as
escape characters much later during hostname.if parsing in netstart(8).
Ok deraadt
|
|
Neither netstart's nor install.sub's (subtly different) implementations
remove trailing comments on lines not starting as a comment, e.g.,
lines like "up #not down" go through unaltered and without "#not down"
being removed.
Only lines *beginning* with the comment sign ("#") are stripped.
No functional change, just updating function descriptions.
|
|
ifstart() should always pass such lines unaltered, especially if they
contain "nwid" or "description" lines with arbitrary strings.
<bsdlisten at gmail dot com> reported SSIDs such as "Mike's" during
installation end as broken; this was because the installer escaped
the single quote using backslashes which ended up being treated as
escape characters much later during hostname.if parsing in netstart(8).
Ok deraadt
|
|
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
|
|
|
|
i noticed this is desirable while looking at an issue
reported by Doug Moss <dougmoss710 at yahoo dot com> on bugs@;
OK deraadt@ sthen@ tb@
|
|
|
|
|
|
No functional change.
|
|
|
|
ok deraadt
|
|
the user to 'rpki-client user' and the homedir to /nonexistent since it is
not required for operation of rpki-client.
OK deraadt@
|
|
no more need for separate v4/v6 groups. ok claudio@
|
|
ok jsg kettenis, testing by kmos also
|
|
|
|
root:_sndiod. Stop creating unused /dev/mixer* devices.
suggested by and ok deraadt
|
|
ok deraadt
|
|
In autonomous systems running bgpd(8) and rpki-client(8) on their edge
routers, it may be beneficial when out-of-the-box all routers don't all
do rpki fetches & bgp loads at the same time. It is expected behavior
for RPKI information to un-evenly percolate towards the BGP edge in a
staggered way.
The 'once an hour' pace may be a reasonable balance between the needs of
internet users, and what network operators tolerate in churn.
OK deraadt@
|
|
The random intervals used can be adjusted as needed. OK deraadt@
|
|
|
|
|
|
|
|
ok kettenis@ deraadt@
|
|
with /dev/console.
Feedback from and ok kettenis@
|
|
|