Age | Commit message (Collapse) | Author |
|
MDFSOPT and add a missing prototype.
|
|
entry point.
ok mlarkin@, deraadt@
|
|
inspect the memory layout that the firmware has created. It is
especially useful for UEFI debugging.
OK deraadt@ kettenis@
|
|
it larger than RC4STATE. A long discussion ensued. In conclusion all
entropy inputs are either satisfactory enough, or just as shitty at 512.
|
|
section, which has grown a fair bit with the introduction of retguard.
Mortimer discovered the repeated 512-byte sequence as retguard keys, and
this resolves the issue. (Chacha does not fit on the media, so 1.5K early
drop RC4 is hopefully sufficient in our KARL link universe)
Version crank the bootblocks. sysupgrade -s will install new bootblocks.
ok djm mortimer
|
|
ok djm mortimer
|
|
so the file cannot be re-executed upon the next boot. This provides a
stronger one-shot-upgrade model than the upgrade script's rm /bsd.upgrade.
Now various forms of upgrade failure will reboot into /bsd, which is probably
more recoverable. Performing fchmod -x depends on (1) use of MI boot.c
(not alpha/macppc/sparc64/sgi/octeon) and (2) "can write blocks" functionality
in the IO layer. Most architectures have this support now.
Two diagnostics "fchmod a-x %s: failed" and "/bsd.upgrade is not u+x" will
remain in the tree while refinements happen for some of the laggard
architectures.
based upon a discussion florian
tested in snapshots for more than a week without any complaints
|
|
|
|
memcpy() correct behaviour. This also brings the bcopy() macro into line.
|
|
details from the ELF header instead of faking it.
Proposal from mlarkin, tested on most architectures already
|
|
half or more would be wasted. Causes more effective re-use of blocks.
ok jsing@
|
|
Historically, the softraid crypto support in the boot loaders has only
given one attempt to provide the correct passphrase. There were a
few reasons for this, including the fact that pkcs5_pbkdf2() allows an
empty passphrase and that returning EPERM allowed for another attempt.
With the event of KARL and the need for bsd.booted with hibernate resumption,
this becomes much more of an issue - if you get the passphrase wrong you
fail to resume. There are also other situations like using /etc/boot.conf
to switch serial console, but an incorrect passphrase results in the config
not being read. Also, bcrypt_pbkdf() does not permit empty passphrases.
This reworks the softraid crypto support in the boot loaders so that it
loops requesting a valid passphrase until one is provided, or an empty
passphrase is entered (at which point it will abort).
ok mortimer@ tb@
|
|
Use zero-padding to get double-digit HH:MM:SS and space-padding for
the DOM.
ok visa@
|
|
endianness for convenience reasons. Especially in code pathes like TFTP
where the source port is read from the received UDP packet and used as
destination port in a new UDP packet this can be very harmful. Luckily
this issue has had no effect on our architectures since they never use
any of the code paths that could be harmful.
ok visa@
|
|
in bootloader printfs.
Feedback from and ok gerhard@
|
|
Inputs and ok jsing@.
|
|
needed
problem noted by naddy@
|
|
not memcpy().
'oh oh' deraadt@
|
|
|
|
implementation that it depends on currently isn't.
ok mikeb tom
|
|
|
|
ok tom@
|
|
|
|
OK krw@
|
|
Based on a diff from djm@
|
|
avoid masking the errno from a failed read().
ok guenther@ tom@
|
|
elf(5)
feedback from guenther@
ok guenther@ kettenis@
|
|
ok deraadt@ millert@
|
|
which holds the CTF data.
ok mpi@
|
|
and softraid crypto key handling code.
|
|
loader to support softraid crypto volumes using bcrypt pbkdf.
|
|
|
|
|
|
|
|
|
|
ok deraadt@
|
|
ok beck@ deraadt@
|
|
and convert all gets() users.
ok deraadt@
|
|
ok tedu@
|
|
ok guenther@
|
|
|
|
ok millert@ jasper@
|
|
ok deraadt yuo
|
|
to the cast to unsigned, it fails the error test and returns a bogus partial
read to the caller, which is painful to debug.
|
|
|
|
kernels and we no longer have any.
|
|
change type of len to size_t to match strlen(3) result. Drop unneeded
casts.
u_int64_t is overkill because the actual size is still limited to SYMLINK_MAX
but it is probably better to match the filesystem types.
ok miod@, guenther@
|
|
ok guenther@, henning@
|
|
caller's responsibility to do so.
|
|
of the kernel, and extend the array filled by loadfile to report the location
of the randomness area.
This doesn't introduce any change for bootblocks (save for a slightly larger
stack usage due to the larger array), for the new {LOAD,COUNT}_RANDOM bits
are included in the {LOAD,COUNT}_ALL masks everything uses or computes from.
|