Re: Kernel dump and secure boot with KARL

[Janne Johansson]

Den tis 5 okt. 2021 kl 06:35 skrev Arka Sharma :
> Also suppose we have a crash and dump is generated, how does KARL impact
> gdb when the core file is opened ?

It would not affect this at all.

It is exactly as hard or as easy to debug a core file from something
compiled with
cc -o bsd obj1.o obj2.o obj3.o
as with something compiled with
cc -o bsd obj2.o obj3.o obj1.o

The relinking is done so that exploit code that knows how to find an
address inside obj1 will not be able to jump into obj2 by taking the
obj1 address and adding 83743 bytes to it and expect to land at a
certain place in obj2. In the first case it would work, in the second
it would not.

-- 
May the most significant bit of your life be positive.

Kernel dump and secure boot with KARL

[Arka Sharma]

Hi All,

I am very much new to OpenBSD. I have come across KARL, and I wonder since
a new kernel image is created on every boot, how does it impact secure
boot.How the new binary is signed ? Is the kernel image signed on every
boot ?
Also suppose we have a crash and dump is generated, how does KARL impact
gdb when the core file is opened ?

Regards,
Arka

Re: Raspberry Pi 4 Model B

[Sandeep Gupta]

Some progress. Thank you. Still stuck though. Post network
configuration,  The boot installer asks for
HTTP Server? (hostname or 'done').  hostname.
Server Directory? [pub/OpenBSD/7.0/arm64].

It fails at this step:

Unable to connect using https. Use http instead.
Looked at found no OpenBSD/arm64 7.0 sets.

I tried with pub/OpenBSD/snapshots/arm64. That didn't work either.



On Thu, Sep 30, 2021 at 11:48 AM Stuart Henderson  wrote:
>
> Change the server directory to /pub/OpenBSD/snapshots/arm64. We're in the 
> awkward time where the version number is just 7.0 so the installer thinks it 
> is a released version, but the release hasn't been made yet, and there is no 
> mechanism for the installer to fetch that information online, so you have to 
> do it manually.
>
> --
>   Sent from a phone, apologies for poor formatting.
>
>
> On 30 September 2021 03:18:36 Sandeep Gupta  wrote:
>>
>> This is my second attempt to install openBSD on RPI4. I write out the UEFI 
>> to sdcard and miniroot.img to usb-ssd drive which takes some 16MB of space. 
>> The rest I create a new fat32 partition. This works -- the boot loader kicks 
>> off the openBSD installer.
>> The installer after asking for disk partitions, reaches till installing 
>> sets.However,
>> it doesn't give me option to install bsd or bsd.rd (see attached pic below).
>>
>> Not sure if I am messing up the disk  partition where openbsd should be 
>> installed. I tried both sd1 and sd1a. But both end up having the same issue.
>>
>> -S
>>
>> On Wednesday, September 29, 2021, Stuart Henderson 
>>  wrote:
>> >
>> > On 2021-09-28, Peter J. Philipp  wrote:
>> > > On Tue, Sep 28, 2021 at 10:04:25AM -0700, Joseph Olatt wrote:
>> > >> I tried the following snapshot:
>> > >>
>> > >>   https://cdn.openbsd.org/pub/OpenBSD/snapshots/arm64/miniroot70.img
>> > >>
>> > >>   Build date: 27-Sep-2021 20:10
>> > >>   Size: 45088768
>> > >>
>> > >> Didn't have much luck. The install process rebooted after the following
>> > >> error:
>> > >>
>> > >>   bwfm0: failed loadfirmware of file 
>> > >> brcmfmac43455-sdio.raspberrypi,4-model-b.bin
>> > >>   panic: do_el0_error
>> > >
>> > > What happens when you boot with -c and 'disable bwfm' then exit?  Is 
>> > > that not
>> > > an option anymore?
>> >
>> > I am pretty sure the do_el0_error is unrelated to the loadfirmware() 
>> > failing
>> > (which is just because the firmware for the device isn't installed yet).
>> >
>> >
>
>