{"id":122002,"date":"2025-02-19T02:22:05","date_gmt":"2025-02-19T00:22:05","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/opensuse-testiruet-podderzhku-povtoryaemyh-sborok"},"modified":"2025-02-19T02:22:05","modified_gmt":"2025-02-19T00:22:05","slug":"opensuse-testiruet-podderzhku-povtoryaemyh-sborok","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/opensuse-testiruet-podderzhku-povtoryaemyh-sborok","title":{"rendered":"openSUSE is testing support for reproducible builds","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The developers of the openSUSE distribution reported successes in the project to provide support for reproducible builds. As part of the project, a conceptual fork of the Reproducible-openSUSE (RBOS) distribution has been prepared, for which the capability to build 100% identical binary packages based on the proposed repository with 3300 source packages has been achieved. Approximately 40 patches (1, 2, 3) have been prepared during the project, which address issues with reproducible package rebuilding. About half of these patches have already been submitted to upstream projects. The Reproducible-openSUSE builds are currently intended only for testing and are not recommended for use in production systems, as no vulnerability mitigation updates are being released for them. <\/p>\n
The project allows users to create their own builds that bit-for-bit match the provided ready-to-load builds, to ensure that the binary files distributed in packages are built from the supplied source texts and contain no hidden changes. The capability to verify the identity of the binary build provides the opportunity not to rely solely on trust in the distribution's build infrastructure, where compiler or build toolchain compromise could lead to the insertion of hidden backdoors. <\/p>\n
When forming reproducible builds, nuances such as exact dependency matching, the use of an unaltered set and versions of build tools, identical options and default settings, maintaining the order of file builds (using the same sorting methods), and disabling the addition of volatile metadata by the compiler, such as random values, file path references, and build date and time data, are taken into account. Errors and race conditions in the toolchain also affect build reproducibility. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"