{"id":120769,"date":"2024-11-29T09:45:59","date_gmt":"2024-11-29T07:45:59","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-paketnom-menedzhere-apt-2-9-15-prekrashheno-ispolzovanie-apt-key"},"modified":"2024-11-29T09:45:59","modified_gmt":"2024-11-29T07:45:59","slug":"v-paketnom-menedzhere-apt-2-9-15-prekrashheno-ispolzovanie-apt-key","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-paketnom-menedzhere-apt-2-9-15-prekrashheno-ispolzovanie-apt-key","title":{"rendered":"The use of apt-key has been discontinued in the APT package manager 2.9.15.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of the APT 2.9.15 package management tool (Advanced Package Tool) has been published. The 2.9.x branch is experimental and is used to develop the functionality of the future stable version APT 3.0, which will be integrated into Debian Testing after stabilization and will be included in the next major release of Debian, as well as added to the Ubuntu package repository. <\/p>\n
The key change in the new version is the final discontinuation of the apt-key utility for managing keys used to verify digital signatures of packages. The apt-key utility was deprecated several years ago due to the shift away from the old model of package integrity verification, which used a shared keyring (\/etc\/apt\/trusted.gpg) and lacked repository-specific key bindings. This meant that a key added for a third-party repository would work for verifying packages in all repositories. The new method of managing keys replaces apt-key and requires separate key storage for each repository (\/etc\/apt\/trusted.gpg.d\/ or \/etc\/apt\/keyrings\/). <\/p>\n
Other changes: <\/p>\n
\n
A path to call gpg has been added for the Rust-written utility gpg-sq, which takes the same arguments as the gpg utility but simulates its operation through Sequoia, an OpenPGP implementation in Rust. The invocation of gpg-sq takes priority over gpg, so to use gpg-sq instead of gpg, simply install the corresponding package.\n
Key types are mapped to file extensions: the extension \".asc\" is associated with ASCII-armored keys, \".gpg\" is always linked to binary keys, and all other file extensions will trigger the error \"The key(s) in the keyring ... are ignored as the file has an unsupported filetype.\" For example, when using a key file \"\/etc\/apt\/keyrings\/winehq-archive.key\", it must be renamed to \"\/etc\/apt\/keyrings\/winehq-archive.gpg\" and the path in the file should be corrected in \"\/etc\/apt\/sources.list.d\/\".\n
Many functions have been modified to use the class \"std::string\" instead of \"const char *\" (the std::string_view class defined in the C++17 standard, which works more efficiently with strings by leveraging references to existing data and avoiding unnecessary data copying until it's utilized in the code).\n
Support for standalone verification of keyrings and performing the dearmor operation (converting ASCII-armored keys to binary format) has been implemented without calling apt-key.\n