Розбіжності

Тут показані розбіжності між вибраною ревізією та поточною версією сторінки.

--- software:os:linux:additional_repos [2023/02/14 19:28]
charon [2. Download key in file from developer's location]
+++ software:os:linux:additional_repos [2023/02/14 19:58] (поточний)
charon [Add signing key for repository]
@@ Рядок 16: / Рядок 16: @@
 I think it means if you need to bother with key, then just put it to ///etc/apt/keyrings//
+===== Using new .sources =====
+.sources file instead of a .list file. This method is relatively new, and uses the deb822 multiline format that is less ambiguous compared to the deb . . . declaration, though is functionally identical. Create a new file:
+  Types: deb
+  Architectures: amd64 arm64
+  Signed-By: /usr/share/keyrings/nodesource.gpg
+  URIs: https://deb.nodesource.com/node_16.x
+  Suites: jammy
+  Components: main
 ===== How to get the key =====
 There are two ways, depending on what package developer implemented
 ==== 1. Download key from keyserver or keyserver pool ====
-First, download the key from keyserver to local user storage:
+  sudo gpg --homedir /tmp --no-default-keyring --keyring /etc/apt/keyrings/usefulpackage.gpg --keyserver \
-  gpg --keyserver keyserver.ubuntu.com --recv-keys 8ED17AF5D7E675EB3EE3BCE98AC3B29174885C03
+  keyserver.ubuntu.com --recv-keys E298A3A825C0D65DFD57CBB6517111119E084DAB9
-Another keyserver: //keys.openpgp.org//
-After that export key to file and put it to keyring directory:
-  gpg --export 8ED17AF5D7E675EB3EE3BCE98AC3B29174885C03 |sudo tee /etc/apt/keyrings/usefulpackage.gpg
-<WRAP center round important 60%>
-I didn't find out whether key should be ascii-armored or not. Most likely should be unarmored (binary).
-</WRAP>
 ==== 2. Download key in file from developer's location ====

Знання

Користувальницькькі налаштування

Налаштування сайту

Розбіжності

Налаштування сторінки