(Sorry, forgot to send earlier) Steve Litt writes:
Something that used to take no more than correctly configuring grub now requires execution of the volumes of information in these links, with much of that execution being trial and error because of different UEFI/secureboot implementations.
That sounds rather like booting itself, as well as reading data from drives and the network. Both were awfully simple until encryption and security and all that ruined it for us.
When I moved from DOS to linux I wrote a network storage driver for DOS (as a client) and linux (as server). The client side was just over 1500 bytes of assembly. No crypto of course. Today I'm sure I couldn't even parse the TLS handshake in that.
I also wrote a minixfs r/o driver in less than 640 bytes of assembly (the total project was 640 bytes, reading the file system was the biggest chunk of that). Again, no crypto. Today dealing with LUKS would need at least 6400 bytes of assembly.
Stuff is so simple if you can assume that noone will try to decrypt your packets, read your files or attack your system.
Arnt _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
