From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jens Schmidt Newsgroups: gmane.emacs.devel Subject: epa.texi: Emacs and GnuPG pinentry Date: Wed, 5 Jul 2023 00:13:27 +0200 Message-ID: <4c2b40c1-2bd6-47cb-6d66-9addd90d7518@vodafonemail.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20603"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 05 00:14:50 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qGoIL-0005Bu-H6 for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Jul 2023 00:14:49 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qGoHJ-0005oi-D1; Tue, 04 Jul 2023 18:13:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qGoHH-0005oV-Tv for emacs-devel@gnu.org; Tue, 04 Jul 2023 18:13:43 -0400 Original-Received: from mr4.vodafonemail.de ([145.253.228.164]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qGoHF-0000sJ-8H for emacs-devel@gnu.org; Tue, 04 Jul 2023 18:13:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vodafonemail.de; s=vfde-mb-mr2-21dec; t=1688508815; bh=F6m1q8C5gDlUf1wcfV5nJF4Ga6YJ57y16AxAn2VJQwg=; h=Message-ID:Date:User-Agent:Content-Language:From:To:Subject: Content-Type:From; b=nxt4mZk9PsQlMT2UW4vsRxbLUffprKMX1T16NadxP/LWFmjBSdxyr2ZlDQI7jK+FX 2E9Ol+y7jZsLl+SxT7rq5AmRuTNBIOsKDkU1nx4LmHGmld88csJKnrV6jiFVQ4K95S WXviNqniImQMx3uk/FOJ+BrHJUeZXls3tkJs5/28= Original-Received: from smtp.vodafone.de (unknown [10.0.0.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mr4.vodafonemail.de (Postfix) with ESMTPS id 4QwcWM0GgJz1yHB for ; Tue, 4 Jul 2023 22:13:35 +0000 (UTC) Original-Received: from [192.168.178.41] (port-92-194-153-144.dynamic.as20676.net [92.194.153.144]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp.vodafone.de (Postfix) with ESMTPSA id 4QwcWG5gsyzMm7H for ; Tue, 4 Jul 2023 22:13:27 +0000 (UTC) Content-Language: de-DE-frami, en-US X-purgate-type: clean X-purgate: clean X-purgate-size: 1063 X-purgate-ID: 155817::1688508810-8F7F8023-59839B1C/0/0 Received-SPF: pass client-ip=145.253.228.164; envelope-from=jschmidt4gnu@vodafonemail.de; helo=mr4.vodafonemail.de X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307443 Archived-At: Hi. I currently try to extend epa.texi based on my own experience with GnuPG and Emacs setup. (Bug#64154 tracks that, but it does not contain anything overly interesting so far.) What puzzled me during my first-time setup were the different modes of Emacs as GnuPG Pinentry. Basically you can have for GnuPG >= 2.1: 1. Use Emacs only for GnuPG requests that are triggered by Emacs itself (aka loopback pinentry), 2. use Emacs for *all* GnuPG requests (also non-Emacs ones), or 3. use Emacs for all GnuPG requests with some other non-Emacs Pinentry as fallback. The latter two alternatives require pinentry.el, which was present in Emacs core only in versions [25, ..., 27] (see https://lists.gnu.org/archive/html/emacs-devel/2018-01/msg00233.html). Plus they are not supported on Debian. While some users may consider alternatives 2. and 3. desirable I'm not sure whether I should describe their setup in detail in epa.texi. I could just mention them and that "they are not recommended for use". Or whatever. WDYT?