Leopold has quit [Remote host closed the connection]
apteryx has quit [Ping timeout: 246 seconds]
thopiekar has quit [Ping timeout: 244 seconds]
prabhakar has joined #u-boot
prabhakarlad has joined #u-boot
thopiekar has joined #u-boot
dossalab has joined #u-boot
apteryx has joined #u-boot
dossalab has quit [Ping timeout: 250 seconds]
sszy has joined #u-boot
dossalab has joined #u-boot
Adrian___ has quit [Read error: Connection reset by peer]
Adrian___ has joined #u-boot
<lvrp16>
i have discovered a phantom in my u-boot. splash_locations get updated automatically with the boot device without me setting splashdevpart. XD, traced it for 6 hours and cannot figure out how or what is changing the .devpart field. I only have 1 location with devpart "0:auto" but it magically changes to "1:auto" depending on the boot device. if I set devpart to "0:abcd", then the phantom disappears. some crazy stuff.
<lvrp16>
I'm starting to wonder if it's LTO doing it
camus has quit [Read error: Connection reset by peer]
camus has joined #u-boot
sng has joined #u-boot
naoki has quit [Quit: naoki]
sng has quit [Remote host closed the connection]
Leopold_ has quit [Ping timeout: 244 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
urja has quit [Ping timeout: 260 seconds]
Leopold has joined #u-boot
naoki has joined #u-boot
sng has joined #u-boot
sng has quit [Remote host closed the connection]
persmule_ has quit [Quit: Leaving]
persmule_ has joined #u-boot
persmule_ has quit [Remote host closed the connection]
persmule has joined #u-boot
dossalab has quit [Quit: dossalab]
sng has joined #u-boot
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 246 seconds]
sng has quit [Remote host closed the connection]
sng has joined #u-boot
Adrian___ has quit [Ping timeout: 252 seconds]
rainbyte has joined #u-boot
Zaid has joined #u-boot
mmu_man has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
naoki has quit [Quit: naoki]
FergusL has quit [Changing host]
FergusL has joined #u-boot
davlefou has quit [Ping timeout: 260 seconds]
thopiekar has quit [Ping timeout: 244 seconds]
thopiekar has joined #u-boot
<sfo[m]>
Is it possible to store the bootdev detected by bootflow scan -b in the u-boot env, so that it can be referenced from extlinux.conf later?
sng has quit [Read error: Connection reset by peer]
monstr has quit [Remote host closed the connection]
mmu_man has quit [Ping timeout: 240 seconds]
vagrantc has joined #u-boot
thopiekar has quit [Ping timeout: 245 seconds]
thopiekar has joined #u-boot
stefanro has quit [Quit: Leaving.]
dossalab has joined #u-boot
thopiekar has quit [Ping timeout: 244 seconds]
thopiekar has joined #u-boot
thopiekar has quit [Ping timeout: 250 seconds]
thopiekar has joined #u-boot
urja has joined #u-boot
LeSpocky has quit [Remote host closed the connection]
mmu_man has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
thopiekar has quit [Ping timeout: 244 seconds]
thopiekar has joined #u-boot
mmu_man has quit [Ping timeout: 246 seconds]
thopiekar has quit [Ping timeout: 246 seconds]
thopiekar_ has joined #u-boot
qqq has quit [Remote host closed the connection]
pivi has joined #u-boot
pivi has quit [Changing host]
pivi has joined #u-boot
goliath has quit [Quit: SIGSEGV]
pivi has quit [Quit: leaving]
pivi has joined #u-boot
thopiekar has joined #u-boot
thopiekar_ has quit [Ping timeout: 260 seconds]
goliath has joined #u-boot
thopiekar has quit [Ping timeout: 246 seconds]
thopiekar has joined #u-boot
ikarso has joined #u-boot
dossalab has quit [Quit: dossalab]
mmu_man has joined #u-boot
sng_ has quit [Remote host closed the connection]
sng has joined #u-boot
apteryx has left #u-boot [#u-boot]
dossalab has joined #u-boot
thopiekar has quit [Ping timeout: 250 seconds]
thopiekar has joined #u-boot
thopiekar has quit [Ping timeout: 245 seconds]
thopiekar has joined #u-boot
<CounterPillow>
What are my network boot options in u-boot if PXE's lack of authentication is too insecure for me? Do I have to hand-roll something myself that downloads kernel + initrd from a thing and checks a signature?
<Sout_>
tftp boot + imi on the fit image + kernel and initrid should do that?
<CounterPillow>
What's imi in this context?
<Sout_>
let me triple check, but i thought it was to verify the .fit images
<CounterPillow>
If it's something where I can throw a cryptographic key into u-boot's configuration and then check whatever I got over TFTP has a valid signature then that would be perfect
<Sout_>
er imi is just crc checks. But yeah from my understanding that is exactly what signatures in fit images do.
<CounterPillow>
Hmmm, this assumes that the user *only* wants to boot signed images regardless of where they're from, which is fine for most instances but I basically want to boot whatever locally but only boot signed stuff over the network
<CounterPillow>
I think I'll already need a custom bootflow, maybe I can somehow hack this in there
<CounterPillow>
Also this only seems to sign the kernel image, not initrd :(
<Sout_>
well it sign's the fit image which can be any set of images.