So I found a bug, it's probably easy to fix but I've about burned out my
brain making TLS work in EFI mode.
assert(((&cert->extensions.subject_alt_name.names))->prev != NULL) failed
at net/tls.c line 2449
assert(((&cert->extensions.subject_alt_name.names))->next != NULL) failed
at net/tls.c line 2
FWIW this is on IBM hardware, and it has gone 5 times in a row managing to
print '2984' as the last sample out the serial port before rebooting. I
reduced to 2048 and it said tests passed at the end, though then it seems
to pause and just say '2056 tests passed' and then the iPXE banner with
feat
On 01/11/13 17:49, Jarrod Johnson wrote:
So my console logging catches 2984 samples and the system then reboots
abruptly. I can send a file with 2984 samples explicitly enumerated,
but not sure if there was more to it that I was missing. It suddenly
reboots the system without further output aft
So my console logging catches 2984 samples and the system then reboots
abruptly. I can send a file with 2984 samples explicitly enumerated, but
not sure if there was more to it that I was missing. It suddenly reboots
the system without further output after 2984 samples (wel, I guess 0-2984).
On
On 31/10/13 22:28, Jarrod Johnson wrote:
Seeking comments on:
https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/89e0b3c8bab8685c7b81dbffdcca05360de8547f
It seems to pass the checks that DRBG throws at it for now.
Looks sensible to me. The only part concerning me is:
/* TODO: actually me
5 matches
Mail list logo
