Authentication-Results: mail-b.sr.ht; dkim=pass header.d=moritz-poldrack.de header.i=@moritz-poldrack.de Received: from mail.moritz-poldrack.de (mail.moritz-poldrack.de [207.180.217.31]) by mail-b.sr.ht (Postfix) with ESMTPS id 37CF911EF44 for <~sircmpwn/aerc@lists.sr.ht>; Thu, 29 Apr 2021 07:49:46 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 3280A10803E2; Thu, 29 Apr 2021 09:49:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=moritz-poldrack.de; s=dkim; t=1619682584; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to; bh=RUpWilHpKyvRv9TKBQmDV/mZS9Wtrd96D1B9nQV7bo0=; b=f9Ud/Rftgwt+zkmEQwBSa0v8EuiZvmi/tPP7eIBtrenriUP/a5FJNI2guaztq0Pyms1bmc JoeUv0YhCnwKni8yfWhuOtm1g0NUTInW4h1GPUIrMD4swTJmeKdORODrk1a2xGwkwbyOy8 4VbxngdheQ/hJz8KcOdp+UpEPBJbLAHX3Zf2BAE1aviZ2rJOG3IBKBQMiHiM6xDJFdeOAc EommIgw3/IzdrTHQpP1cnnQkd+haJoAoyt7o0lOsDS8MXAq1wa6Pf1VVKU303ubAiZ+MIc yqe87Yk2Hp9jweK8xkMbwKMOADP0jnJ5EJ92o6lxK07w5GtXPrmWVwEvBd7qlA== Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 From: "Moritz Poldrack" To: <~sircmpwn/aerc@lists.sr.ht> Cc: =?utf-8?q?Chris_H=C3=B6ppner?= Subject: Re: Initial PGP support added Date: Thu, 29 Apr 2021 09:34:00 +0200 Message-Id: In-Reply-To: <3EBEA82C-66AF-4E61-AAB2-4E118A2080AE@mkaito.net> X-Last-TLS-Session-Version: TLSv1.3 Wouldn't it be better then to use GPG if available and fall back to the internal tooling if it is not? Or at least making the use of shell GPG optional. I think I am not the only one uncomfortable with just straight up exporting my secret keys. > It should just werk. This is a great tenet for working, but I think having the freedom to configure this would allow for a more fine-grained control for advanced users. Like, using the mutt defaults [1] which are pretty decent IMHO. [1]:https://gitlab.com/muttmua/mutt/-/blob/master/contrib/gpg.rc