{"id":123002,"date":"2025-03-26T04:22:53","date_gmt":"2025-03-26T02:22:53","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/razrabotchiki-grub2-rassmatrivayut-vozmozhnost-ispolzovaniya-yazyka-rust"},"modified":"2025-03-26T04:22:53","modified_gmt":"2025-03-26T02:22:53","slug":"razrabotchiki-grub2-rassmatrivayut-vozmozhnost-ispolzovaniya-yazyka-rust","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/razrabotchiki-grub2-rassmatrivayut-vozmozhnost-ispolzovaniya-yazyka-rust","title":{"rendered":"GRUB2 Developers Consider Using Rust Language","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Vladimir Serbinenko, one of the three maintainers of the GRUB2 bootloader, who has contributed over five thousand changes to the codebase, proposed the possibility of writing modules for GRUB2 using the Rust programming language. Vladimir presented the first results of experiments with adding Rust support to GRUB2 and creating the necessary bindings. Changes have also been prepared for GRUB to allow the use of shared libraries ('.so', ET_DYN) for modules instead of linking at the object file level ('.o', ET_REL). <\/p>\n
The initiative is currently positioned as a separate experiment that will not affect GRUB2 development. The optimal application of Rust in GRUB is mentioned as writing modules for new file systems. There is also the possibility of rewriting the code for disk partitions and GPT in Rust. <\/p>\n
It is expected that using Rust will help the project reduce the likelihood of certain types of errors, especially in module code that contains many large and complex parsing procedures. In February, an audit of the GRUB codebase revealed 72 security issues, 21 of which were deemed serious vulnerabilities capable of bypassing the UEFI Secure Boot verified boot mechanism. 20 out of 21 vulnerabilities were caused by memory handling errors that led to buffer overflows or dereferencing memory after it was freed. <\/p>\n
Additionally, it is worth noting the release of GNU Boot 0.1 RC6, which includes the aforementioned vulnerability fixes (in GRUB2, the fixes continue to be distributed as patches without forming a separate release). The GNU Boot project develops a replacement for proprietary UEFI and BIOS firmware based on CoreBoot but applying stricter requirements for including binary components. GNU Boot is presented as 'coreboot-libre', i.e., as a version of CoreBoot free of blobs and non-free components, similar to how the Linux-libre project develops a cleaned version of the Linux kernel. Similar projects like Libreboot and Canoeboot are also being developed separately. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"