Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..
|
|
|
|
|
|
the sme.
|
|
|
|
|
|
|
|
having two mysterious names, let's settle on one.
|
|
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.
|
|
tightly-built ramdisk kernels, set the option in per-arch Makefile.inc
based upon SMALL_KERNEL
|
|
|
|
|
|
|
|
|
|
ok kevlo@
|
|
random cookies to protect access to function return instructions, with the
effect that the integrity of the return address is protected, and function
return instructions are harder to use in ROP gadgets.
On function entry the return address is combined with a per-function random
cookie and stored in the stack frame. The integrity of this value is verified
before function return, and if this check fails, the program aborts. In this way
RETGUARD is an improved stack protector, since the cookies are per-function. The
verification routine is constructed such that the binary space immediately
before each ret instruction is padded with int03 instructions, which makes these
return instructions difficult to use in ROP gadgets. In the kernel, this has the
effect of removing approximately 50% of total ROP gadgets, and 15% of unique
ROP gadgets compared to the 6.3 release kernel. Function epilogues are
essentially gadget free, leaving only the polymorphic gadgets that result from
jumping into the instruction stream partway through other instructions. Work to
remove these gadgets will continue through other mechanisms.
Remaining work includes adding this mechanism to assembly routines, which must
be done by hand. Many thanks to all those who helped test and provide feedback,
especially deaadt, tb, espie and naddy.
ok deraadt@
|
|
DESTDIR rather than reaching around in src. ok deraadt
|
|
Some resizing scenarios can be done from within single user mode, but
resizing the root partition required you to bring your own growfs(8)
binary into the ramdisk environment. This commit adds growfs(8) to the
ramdisks (the ones that don't have space constraints) to simplify such
operations.
OK deraadt@
|
|
broke amd64/ramdisk_cd as it no longer fit; spotted by jsg@
ok deraadt@ mpi@
|
|
according to the same logic for all architectures but sgi.
Consolidate setting them in one place in install.sub and incorporate
the sgi specific MDSETS and MDSANESETS.
Introduce MDSANESETS complementing MDSETS which makes the construction
of DEFAULTSETS, THESETS and SANESETS clearer in install.sub.
While here, adjust the comment about how MDSETS used now.
OK deraadt@
|
|
clang optimizes better for size with -Oz so use that as a default to avoid
overflowing the ramdisk floppies. gcc now accepts -Oz as an alias for -Os.
ok kettenis@
|
|
|
|
Size problem noted by me, correct fix from deraadt@
|
|
Prepare the install*.fs files for this growth.
|
|
tracked that permission. Make the copy in $RELEASEDIR a+r
|
|
|
|
can perform https fetches. While non-critical for sets (which are verified
using signify), it is an uplift for communication towards the ftp.openbsd.org
cgi which provides mirror proposals, entropy seeds, and current time.
[The install script changes are not included in this commit]
ok beck jsing rpe
|
|
will follow with some safety distance when I figured out all MD quirks.
makefs allows to build the ramdisk image as an unprivileged user. The
next step in the quest to reduce root during builds.
ok deraadt
|
|
ok deraadt
|
|
ok deraadt
|
|
into the picture.
ok natano
|
|
as required.
much help from natano and tb.
|
|
The instbin stuff looks good to deraadt@
|
|
Saves precious 896 bytes as a side effect.
OK deraadt
|
|
/tmp with proper permissions so that unprivileged programs can not
tamper with them.
positive feedback from deraadt
OK halex
|
|
/tmp with proper permissions so that unprivileged programs can not
tamper with them.
positive feedback from deraadt
OK halex
|
|
OK halex, tb, deraadt
|
|
The current code is too strict and checks for an OpenBSD area inside an
MBR or GPT and if it fails to find one reports that there's no valid MBR
or GPT (which is misleading because the MBR/GPT is valid).
Instead, do two checks (similar to i386): first see if there's an MBR or GPT
present on the disk and if there is then check for the OpenBSD area.
OK krw@, halex@.
|
|
- merge upgrade.sh into install.sub as do_upgrade()
- delete install.sh and upgrade.sh
- make install.sub executable
- turn install and upgrade into symbolic links to install.sub
- add autoinstall symbolic link to install.sub
- change dot.profile to use these symlinks
- introduce a -m option to set MODE in install.sub
- alternativly set MODE and AUTO depending on PROGNAME
- execute the do_{install,upgrade) functions depending on $MODE
OK halex@, krw@
'go for it' deraadt@
|
|
verbiage explaining what disklabels are.
If you don't know, you should be using (A)uto!
ok rpe@ halex@
|
|
OK halex@ krw@
|
|
- prevent autoinstall loop
OK krw@
|
|
partition-table of a certain type and optionally if it has a partition
of a certain type.
Use disk_has() in the install.md script to replace all the various
"fdisk <disk> | grep <pattern>" commands greatly simplifying things.
positive feedback from sthen@
"time to get it really tested" deraadt@
OK krw@
|
|
'O*|o*' as a valid response. Ignore it as we do other invalid input.
armv7 is special case to be handled separately.
Noticed by kettenis@.
ok deraadt@ rpe@
|
|
result may not be bootable if GPT is used on a machine that did not
boot via EFI. But allow the user to proceed if the user insists.
Sometimes you just want to create an EFI bootable image on a non-EFI
machine.
Enforce the presence of both an OpenBSD partition and an EFI Sys
partition if GPT partitioning is used.
Prompted by complaints and observations from kettenis@.
Verbiage tweak from doug@. Tested & ok rpe@.
|
|
OK jmc@ krw@
|
|
'reinit;update;write;quit'. They've done the same thing for some
time now.
Tweaks & test from rpe@.
ok rpe@ deraadt@
|