Searched refs:PGP (Results 1 – 16 of 16) sorted by relevance
/linux-6.12.1/Documentation/translations/zh_CN/process/ |
D | maintainer-pgp-guide.rst | 14 内核维护者 PGP 指南 25 PGP 在 Linux 内核开发中的作用 28 PGP 有助于确保 Linux 内核开发社区产出代码的完整性,并在较小程度上,通过 29 PGP 签名的电子邮件交换,在开发者之间建立可信的交流渠道。 36 git 仓库和 tarball 都带有创建官方内核版本的内核开发者的 PGP 签名。这 40 - git 仓库在所有标签上提供 PGP 签名 41 - tarball 为所有下载提供独立的 PGP 签名 52 来创建安全的工作环境并保护用于建立 Linux 内核本身完整性的 PGP 密钥。 54 PGP 工具 93 保护你的 PGP 密钥 [all …]
|
D | embargoed-hardware-issues.rst | 33 邮件列表是加密的,发送到列表的电子邮件可以通过PGP或S/MIME加密,并且必须使用报告 34 者的PGP密钥或S/MIME证书签名。该列表的PGP密钥和S/MIME证书可从 203 列表的PGP密钥或列表的/MIME证书进行加密。邮件列表软件对电子邮件进行解密,并 204 使用订阅者的PGP密钥或S/MIME证书为每个订阅者分别对其进行重新加密。有关邮件列表 221 的PGP密钥或S/MIME证书签名。如果使用PGP密钥,则必须从公钥服务器获得该密钥, 222 并且理想情况下该密钥连接到Linux内核的PGP信任网。另请参见: 226 的电子邮件,该邮件列表使用列表的PGP密钥或列表的/MIME证书签名。订阅者的电子邮件 227 客户端可以从签名中提取PGP密钥或S/MIME证书,以便订阅者可以向列表发送加密电子
|
D | email-clients.rst | 60 不要在使用PGP/GPG签名的邮件中包含补丁。这样会使得很多脚本不能读取和适用于你的
|
/linux-6.12.1/Documentation/translations/zh_TW/process/ |
D | embargoed-hardware-issues.rst | 36 郵件列表是加密的,發送到列表的電子郵件可以通過PGP或S/MIME加密,並且必須使用報告 37 者的PGP密鑰或S/MIME證書籤名。該列表的PGP密鑰和S/MIME證書可從 206 列表的PGP密鑰或列表的/MIME證書進行加密。郵件列表軟件對電子郵件進行解密,並 207 使用訂閱者的PGP密鑰或S/MIME證書爲每個訂閱者分別對其進行重新加密。有關郵件列表 224 的PGP密鑰或S/MIME證書籤名。如果使用PGP密鑰,則必須從公鑰服務器獲得該密鑰, 225 並且理想情況下該密鑰連接到Linux內核的PGP信任網。另請參見: 229 的電子郵件,該郵件列表使用列表的PGP密鑰或列表的/MIME證書籤名。訂閱者的電子郵件 230 客戶端可以從簽名中提取PGP密鑰或S/MIME證書,以便訂閱者可以向列表發送加密電子
|
D | email-clients.rst | 61 不要在使用PGP/GPG簽名的郵件中包含補丁。這樣會使得很多腳本不能讀取和適用於你的
|
/linux-6.12.1/Documentation/process/ |
D | maintainer-pgp-guide.rst | 4 Kernel Maintainer PGP guide 17 The role of PGP in Linux Kernel development 20 PGP helps ensure the integrity of the code that is produced by the Linux 22 communication channels between developers via PGP-signed email exchange. 29 Both git repositories and tarballs carry PGP signatures of the kernel 35 - git repositories provide PGP signatures on all tags 36 - tarballs provide detached PGP signatures with all downloads 55 a secure working environment and safeguard the PGP keys used to 60 PGP tools 108 Protect your PGP key [all …]
|
D | embargoed-hardware-issues.rst | 38 The list is encrypted and email to the list can be sent by either PGP or 39 S/MIME encrypted and must be signed with the reporter's PGP key or S/MIME 40 certificate. The list's PGP key and S/MIME certificate are available from 43 - PGP: https://www.kernel.org/static/files/hardware-security.asc 324 list's PGP key or with the list's S/MIME certificate. The mailing list 326 subscriber with the subscriber's PGP key or S/MIME certificate. Details 347 by email. The email must be signed with the subscriber's PGP key or S/MIME 348 certificate. If a PGP key is used, it must be available from a public key 349 server and is ideally connected to the Linux kernel's PGP web of trust. See 354 email from the mailing-list which is signed either with the list's PGP key [all …]
|
D | email-clients.rst | 56 Don't use PGP/GPG signatures in mail that contains patches.
|
/linux-6.12.1/Documentation/translations/it_IT/process/ |
D | maintainer-pgp-guide.rst | 9 La guida a PGP per manutentori del kernel 23 Il ruolo di PGP nello sviluppo del kernel Linux 26 PGP aiuta ad assicurare l'integrità del codice prodotto dalla comunità 28 affidabili tra sviluppatori attraverso lo scambio di email firmate con PGP. 36 Sia i repositori git che gli archivi tar portano le firme PGP degli 42 - i repositori git forniscono firme PGP per ogni tag 63 salvaguardare le chiavi PGP usate nello stabilire l'integrità del kernel Linux 68 Strumenti PGP 118 Proteggere la vostra chiave PGP primaria 121 Questa guida parte dal presupposto che abbiate già una chiave PGP che usate [all …]
|
D | email-clients.rst | 65 Non usate firme PGP/GPG nei messaggi che contengono delle patch. Questo
|
/linux-6.12.1/Documentation/translations/sp_SP/process/ |
D | embargoed-hardware-issues.rst | 46 enviado por PGP o S/MIME encriptado y debe estar firmado con la llave de 47 PGP del reportero o el certificado de S/MIME. La llave de PGP y el 51 - PGP: https://www.kernel.org/static/files/hardware-security.asc 304 lista se encripta con la llave PGP de la lista o con el certificado S/MIME 307 PGP del suscriptor o el certificado S/MIME. Los detalles sobre el software 330 con la llave PGP del suscriptor o el certificado S/MIME. Si se usa una 331 llave PGP, debe estar disponible desde un servidor de llave publica y esta 332 idealmente conectada a la red de confianza PGP del kernel de Linux. Véase 338 PGP de la lista o el certificado S/MIME de la lista. El cliente de correo 339 electrónico del suscriptor puede extraer la llave PGP o el certificado
|
D | email-clients.rst | 68 No utilice firmas PGP/GPG en el correo que contiene parches.
|
/linux-6.12.1/drivers/gpu/drm/radeon/ |
D | sumod.h | 337 # define PGP(x) ((x) << 8) macro
|
D | sumo_dpm.c | 173 WREG32_P(CG_PWR_GATING_CNTL, PGP(p) | PGU(u), in sumo_gfx_powergating_initialize() 179 WREG32_P(CG_CG_VOLTAGE_CNTL, PGP(p) | PGU(u), in sumo_gfx_powergating_initialize()
|
/linux-6.12.1/Documentation/crypto/ |
D | asymmetric-keys.rst | 107 instance, PGP generates key identifiers by hashing the key data plus some 108 PGP-specific metadata, whereas X.509 has arbitrary certificate identifiers.
|
/linux-6.12.1/ |
D | CREDITS | 5 (W), PGP key ID and fingerprint (P), description (D), and
|