WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sbin/shutdown?h=jd%2Fqueueboosts 2018-08-03T17:09:22Z 2018-08-03T17:09:22Z deraadt deraadt@openbsd.org 2018-08-03T17:09:22Z urn:sha1:a5617f5ed0f796652921ad76efd0c748acc68995 powerdown, halt, or singleuser. Before pledge, unveil access to /dev/console, /etc/rc for singleuser entry, execute of /usr/bin/wall to alert users, and creation of the fastboot and nologin files. Also conditionally allow execute of halt, reboot, or the shell depending on mode. Believe all scenarios were tested -- please exercise this one a bit. 2018-04-07T19:08:13Z cheloha cheloha@openbsd.org 2018-04-07T19:08:13Z urn:sha1:7e3375798827d30b1158682b38fb3a1d5d115420 Admins don't necessarily reside in the same timezone as the machine. If an admin mistakenly schedules downtime for a machine at the wrong time this could be quite bad. Users, too, don't necessarily reside in the same timezone as the machine. Saying the box is going down at "15:40" is potentially ambiguous. So, display the local timezone in all logs, broadcasts, printouts, messages, etc. Give the admin a chance to correct the mistake; give the user a better idea of when the box is actually going down. This also updates the process' understanding of the present time before printing estimates. The system's wall clock could have changed after the shutdown was scheduled, making subsequent broadcasts potentially misleading for users. ok deraadt@ 2018-03-19T14:51:45Z cheloha cheloha@openbsd.org 2018-03-19T14:51:45Z urn:sha1:44680ff5ad48b4c8f46d19d94ffb444febcaf341 strtonum(3) accepts a single leading '+', so if we increment timearg we allow input with two leading pluses. If we don't increment, we still have a valid input for strtonum(3). While here, use errstr to say what was wrong with timearg. Don't increase the range for offsets yet: it exposes segfaults elsewhere in the program that need to be addressed. ok millert@ tb@ 2018-03-02T02:30:15Z cheloha cheloha@openbsd.org 2018-03-02T02:30:15Z urn:sha1:c766b91388db3d3a7648de82edbc79d7190daff8 If we insert our offset into tlist[] and then process tlist[] like an array we can eliminate many of the special cases and duplicate calls in loop(). While we're at it, change struct interval and timewarn() to use time_t to eliminate the need for some of the casting and add explicit long-long suffixes to the constants in tlist[] to head off overflow if the code wanders off. With type-related input from tb@ and a style tweak from anton@. ok tb@ 2018-02-24T20:00:07Z cheloha cheloha@openbsd.org 2018-02-24T20:00:07Z urn:sha1:fde1d200342a9eb4e2358c62c38e0daa9ac08c6e We can limit the time we wait on wall(1) without the complexity inherent to setjmp. Actually wait (instead of waitpid) to pick up any straggler wall processes from prior timewarn() calls. With a tweak from millert@ to ensure we don't accidentally close stdin before we exec wall. ok millert@ tb@ 2018-02-04T04:28:41Z cheloha cheloha@openbsd.org 2018-02-04T04:28:41Z urn:sha1:59eaf1c4c3f9b3d6e867df2198fd5cee9ef784b7 ok jca@ tb@ 2017-04-03T20:59:19Z fcambus fcambus@openbsd.org 2017-04-03T20:59:19Z urn:sha1:a2f556876585311b939162e57b5b0292e4e9283e OK deraadt@, millert@ 2016-09-01T09:50:38Z deraadt deraadt@openbsd.org 2016-09-01T09:50:38Z urn:sha1:a91c3ab5a063c974ed730684747a15474fb56789 localtime() since it tends to work better than ctime() when some filesystems are absent. ok guenther 2015-11-16T18:35:31Z deraadt deraadt@openbsd.org 2015-11-16T18:35:31Z urn:sha1:8aa0c8fbc0befba1ef2fb9f8d715fe89333de4f2 it sounds like a lot, but this will eventually run the /etc/rc scripts to shutdown, then run reboot or halt. After looking at getpw*, drop pledge "getpw". Later drop to just "stdio exec"... This depends on new pledge semantics for revoke(2). with help from jca ok guenther millert semarie tedu jca 2015-04-23T02:13:18Z deraadt deraadt@openbsd.org 2015-04-23T02:13:18Z urn:sha1:089371e786f28b49f75dd06329d8b4cdbaf5e2fa