{"thread":{"id":"59846","subject":"git-send-email(1): Encrypted email","startedAt":"2023-06-08T19:45:24Z","lastAt":"2023-06-08T19:45:24Z","messageCount":1,"participants":["Alejandro Colomar"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"478178","messageId":"1309b98d-90a0-adce-7eec-8d035b727bf9@kernel.org","threadId":"59846","inReplyTo":null,"subject":"git-send-email(1): Encrypted email","fromName":"Alejandro Colomar","fromEmail":"alx@kernel.org","sentAt":"2023-06-08T19:45:15Z","receivedAt":"2023-06-08T19:45:24Z","isPatch":false,"sender":{"key":"alx@kernel.org","avatar":null},"body":"Hi!\n\nWhen there's a vulnerability, many projects require that patches (and\nrelated discussions) are encrypted with the GPG keys of the maintainers.\n\nIt would be nice to be able to send such patches with git-send-email(1),\nwhich would have to use the GPG keyring (git(1) already has code to use\nthe keyring, for example for git-commit(1) -S (--gpg-sign), so I guess\nit's not crazy to extend such use of the keyring to encrypt patches.\n\nWhat do you think about it?\n\nThanks,\nAlex\n\n-- \n<http://www.alejandro-colomar.es/>\nGPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5\n"}]}