Es ist möglich, eine schwarze 1&1 FRITZ!Box (Business Server) vom "Branding" zu befreien, auch wenn sie einen neuen Bootloader besitzt (>1.3082), bei dem die FTP-Methode nicht mehr funktioniert. Wirklich notwendig ist das natürlich nicht, denn alle Funktionen sind auch mit der 1&1 Firmware vorhanden.
Dazu erstellt man ein sog. InMemory-Image, da die neueren FRITZ!OS keine unsignierten Firmwares mehr akzeptieren. Während der Gelegenheit bietet es sich an, eine eigene Signatur auf das modifizierte Image zu packen, denn dann lassen sich später eigene Firmwareimages ganz einfach über die Update-Funktion im FRITZ!OS auf die Box laden.
Am einfachsten gelingt das Vorhaben mit Freetz.
Freetz bietet einen "no freetz"-Modus, in dem keinerlei sonstige Änderungen an der Firmware durchgeführt werden, was sich in diesem Fall anbietet.
7/23/2018
GRUB Standalone with embedded config file and different keymap
It is possible to create a single GRUB EFI binary without any additional config files, modules, drivers, themes etc. on the boot partition. All those files will be put in a tar memdisk and then included into the binary itself, creating a "standalone" .efi file.
While that isn't really necessary for most users, it can be beneficial for full disk encryption scenarios.
GRUB is the only boot loader that can decrypt a LUKS blockdevice as of today.
However, in the standard configuration GRUB places its config files and drivers onto the boot partition. But on a fully encrypted disk, those files can't be read at boot.
Consequently no customization (e.g. changed colors, background, screen resolution) is available and one is greeted by an ugly password prompt before one can even chose what kernel or OS to boot.
Also, the decryption takes ages, even on a modern CPU. If you just want to boot a different OS on a dual boot machine this can be very tedious.
While that isn't really necessary for most users, it can be beneficial for full disk encryption scenarios.
GRUB is the only boot loader that can decrypt a LUKS blockdevice as of today.
However, in the standard configuration GRUB places its config files and drivers onto the boot partition. But on a fully encrypted disk, those files can't be read at boot.
Consequently no customization (e.g. changed colors, background, screen resolution) is available and one is greeted by an ugly password prompt before one can even chose what kernel or OS to boot.
Also, the decryption takes ages, even on a modern CPU. If you just want to boot a different OS on a dual boot machine this can be very tedious.
Subscribe to:
Posts (Atom)