{"id":74341,"date":"2020-03-16T20:42:18","date_gmt":"2020-03-16T17:42:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/proekt-redox-os-predstavil-paketnyj-menedzher-pkgar-napisannyj-na-yazyke-rust"},"modified":"2020-03-16T20:42:18","modified_gmt":"2020-03-16T17:42:18","slug":"proekt-redox-os-predstavil-paketnyj-menedzher-pkgar-napisannyj-na-yazyke-rust","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/proekt-redox-os-predstavil-paketnyj-menedzher-pkgar-napisannyj-na-yazyke-rust","title":{"rendered":"The Redox OS project has introduced the pkgar package manager, written in Rust.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Developers of the operating system Redox<\/a><\/noindex>, written<\/a><\/noindex> using the Rust language and microkernel concepts. have introduced<\/a><\/noindex> new package manager pkgar<\/a><\/noindex>. Within the project, a new format for packages is being developed, including a library for package management functions and a command-line toolkit for creating and extracting cryptographically verified collections of files. The pkgar code is written in Rust and is distributed<\/a><\/noindex> is licensed under the MIT License.<\/p>\n

The pkgar format does not claim universality and is optimized for the specifics of the Redox OS operating system. The package manager supports verification of the source via digital signatures and integrity checks. Checksums are calculated using the hash function blake3<\/a><\/noindex>The functionality related to verification of pkgar can be accessed without actually saving the package archive, manipulating only the header part. Specifically, the package is composed of a header file (.pkgar_head) and a data file (.pkgar_data). A correctly signed complete aggregate package (.pkgar) can be obtained by simply appending the header file to the data file (cat example.pkgar_head example.pkgar_data > example.pkgar). <\/p>\n

The header file contains separate checksums for the header and structures with parameters from the data file, as well as a digital signature for package verification. The data file includes a sequential listing of all files and directories supplied in the package. Before each data element, there is a structure with metadata, which includes the checksum for the actual data, size, access permissions, the relative path of the installed file, and the offset of the next data element's parameters. If individual files have not changed during the update and the checksum matches, they are skipped and not downloaded.<\/p>\n

You can check the integrity of the source by obtaining only the header file, and verify the correctness of the chosen data file by downloading only the structure with the parameters of this file and ensuring they match the checksum certified in the header file. The actual data can be verified after it is downloaded, using the checksum from the parameters structure preceding the data.<\/p>\n

Packages are initially designed for repeatable assembly, meaning that creating a package for a specific directory always results in the formation of an identical package. After installation, only metadata is retained in the system, which is sufficient to reconstruct the package from the installed data (the package contents, checksums, paths, and access rights are included in the metadata).<\/p>\n

Key goals of pkgar:<\/p>\n