(base) root@open-web-ui:/etc/apt/sources.list.d# sudo mv /etc/apt/trusted.gpg.d/nginx.gpg /usr/share/keyrings/nginx-archive-keyring.gpg (base) root@open-web-ui:/etc/apt/sources.list.d# sudo chmod 644 /usr/share/keyrings/nginx-archive-keyring.gpg (base) root@open-web-ui:/etc/apt/sources.list.d# file /usr/share/keyrings/nginx-archive-keyring.gpg /usr/share/keyrings/nginx-archive-keyring.gpg: OpenPGP Public Key Version 4, Created Wed May 29 13:22:30 2024, RSA (Encrypt or Sign, 4096 bits); User ID; Signature; OpenPGP Certificate (base) root@open-web-ui:/etc/apt/sources.list.d# wget http://nginx.org/keys/nginx_signing.key --2025-03-06 07:32:10-- http://nginx.org/keys/nginx_signing.key Connecting to 10.32.99.43:3128... connected. Proxy request sent, awaiting response... sudo gpg --dearmor -o /usr/share/keyrings/nginx-archive-keyring.gpg nginx_signing.key200 OK Length: 11809 (12K) [application/octet-stream] Saving to: ‘nginx_signing.key’ nginx_signing.key 100%[===================================================================================================================>] 11.53K --.-KB/s in 0.002s 2025-03-06 07:32:11 (7.05 MB/s) - ‘nginx_signing.key’ saved [11809/11809] (base) root@open-web-ui:/etc/apt/sources.list.d# sudo gpg --dearmor -o /usr/share/keyrings/nginx-archive-keyring.gpg nginx_signing.key File '/usr/share/keyrings/nginx-archive-keyring.gpg' exists. Overwrite? (y/N) y (base) root@open-web-ui:/etc/apt/sources.list.d# sudo apt-get update Ign:1 https://deb.nodesource.com/node_20.x nodistro InRelease Get:2 http://nginx.org/packages/ubuntu jammy InRelease [3599 B] Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:4 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease Get:5 http://nginx.org/packages/ubuntu jammy/nginx amd64 Packages [27.3 kB] Hit:6 https://repo.zabbix.com/zabbix-tools/debian-ubuntu jammy InRelease Hit:7 https://repo.zabbix.com/zabbix/7.0/ubuntu jammy InRelease Hit:1 https:
时间: 2025-06-05 16:48:55 浏览: 25
### 如何正确安装和配置 Nginx GPG 密钥
为了确保 APT 包管理器能够验证来自 Nginx 官方仓库的软件包,在 Ubuntu 22.04 上需要按照特定流程来添加并配置 Nginx 的 GPG 密钥。
#### 添加 Nginx 官方 GPG 密钥
通过执行如下命令可安全地获取 Nginx 官方发布的 GPG 密钥:
```bash
wget https://nginx.org/keys/nginx_signing.key
sudo apt-key add nginx_signing.key
```
此操作会下载 Nginx 提供的安全签名密钥文件,并将其加入到系统的受信任密钥列表中[^1]。
#### 验证密钥是否成功添加
可以通过查询已知指纹确认新添加的密钥是否存在:
```bash
apt-key fingerprint ABF5BD827BD9BF62
```
这里 `ABF5BD827BD9BF62` 是 Nginx 官方提供的公钥 ID,用于匹配所添加的密钥。如果显示的信息中含有 "Nginx signing key" 则表示密钥已被正确导入[^3]。
#### 创建或编辑 sources.list.d 中的 Nginx 源条目
为了让 APT 认识到来自 Nginx 的更新渠道,需创建一个新的源列表文件指向稳定版发布地址:
```bash
echo "deb http://nginx.org/packages/mainline/ubuntu/ $(lsb_release -cs) nginx" | sudo tee /etc/apt/sources.list.d/nginx.list
echo "deb-src http://nginx.org/packages/mainline/ubuntu/ $(lsb_release -cs) nginx" | sudo tee -a /etc/apt/sources.list.d/nginx.list
```
上述命令中的 `$(lsb_release -cs)` 自动填充当前发行版本代号,适用于不同版本的 Ubuntu 系统环境设置。
完成以上步骤之后,记得运行 `sudo apt update` 来刷新本地缓存索引,使新的存储库生效。此时再尝试安装 Nginx 或者其他依赖项时,APT 就能自动利用刚才配置好的 GPG 密钥来进行校验工作了。
阅读全文
相关推荐

















