From owner-freebsd-ports@freebsd.org Sat Nov 5 10:49:06 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3128FC30E31 for ; Sat, 5 Nov 2016 10:49:06 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B798D876 for ; Sat, 5 Nov 2016 10:49:05 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id f82so34434346wmf.1 for ; Sat, 05 Nov 2016 03:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=P3nxwnuRj3WINF+e3vQa2ruaNVLz2o57txFtgUwVqe4=; b=0yaBHt5mHb/LBnYvQDuDPk8mHETfmdTJURMQ3mJnCpFO+OfKWikXm/4ld5SqELRYBO C8p1YGMyFhIy/9kvYR1TPkZEDReqTjKIOqM33YY3/XTVhNTiNg78DKe9dlDUaD2pkdyJ dy53lALleQhE8TXdOgbw/KWHl4LAHuySlZHuIl09N+ynDeSngtlAVMXrENTBmdgH+iiB BKrBZoKVQar9q/0wLunUVFTP2xD8HS8bB19X//3YnTwMu3CSynPgDjpQ9sN4Bbx2g9Px fMBI2aqj1X+jvousbu9M+/Yj3iakS5wKp6/YcBGAFGQaqW8nD7uaHwVVo44aK5W+Rvio l0EQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=P3nxwnuRj3WINF+e3vQa2ruaNVLz2o57txFtgUwVqe4=; b=Cz7x4JkxUDJEzdGAgsLlEGcHVsww28qkvraGcOV8JbNaDa1Od6MxWQG6MLG5rBAnOF DvGTnecdGZLrJG7vX1S+SFVDPwVteXY1VsChx9I8A5x2aHrx+3xusYRj/wgstEBpGe0f D8t8O46VTBww/DnmK5Zu0XQDJ8oxbz1Ilbdf5VOlbDf/EFveljxRgM01KMzjtaH9nFQU siddb6ssKEoCyOdohdq7U+bYvH9hzdmLHdFARcuhsdyGRjYlNf0W1JWwvvE2SzqggySg 8/7mvS/1JcqfSG63zeQm/zFkbjhRAW0/3NPgafRqDQxbZnEPQY/w6QyS1VC2DT0uVpYh a3xg== X-Gm-Message-State: ABUngvfFqjpP1y1y2Oq+c8/7sj0EcX3NUEGSh4kgCcKAvShe0y0MtHFHIYcofIX1hep+Bg== X-Received: by 10.28.213.74 with SMTP id m71mr1347789wmg.39.1478342944117; Sat, 05 Nov 2016 03:49:04 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id b184sm1596001wma.0.2016.11.05.03.49.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Nov 2016 03:49:03 -0700 (PDT) Sender: Baptiste Daroussin Date: Sat, 5 Nov 2016 11:49:03 +0100 From: Baptiste Daroussin To: freebsd-ports@freebsd.org, dereks@lifeofadishwasher.com Subject: Re: mail/{neo,}mutt: why not packaged with gpgme? Message-ID: <20161105104902.z7p3cx2apahbopxm@ivaldir.etoilebsd.net> References: <20161102204551.jkismaljloqwlokp@box-hlm-03.niklaas.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zxuizdoh2sruf3su" Content-Disposition: inline In-Reply-To: <20161102204551.jkismaljloqwlokp@box-hlm-03.niklaas.eu> User-Agent: NeoMutt/20161028 (1.7.1) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2016 10:49:06 -0000 --zxuizdoh2sruf3su Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 02, 2016 at 09:45:51PM +0100, Niklaas Baudet von Gersdorff wrot= e: > Hello, >=20 > While talking about an issue I have with mail/{neo,}mutt and > security/gnupg on #gnupg on freenode I was advised to use > security/gpgme with mutt. I haven't been using gpgme for a while, > mainly because the packaged versions of both mail/{neo,}mutt have > it disabled and I was too lazy to compile it on my own. Since > I got that advice, I've started wondering: >=20 > Why is gpgme disabled by default? >=20 > As was argued (and as I experienced myself) setting up mutt to > work with gpgme is much easier than without. Especially gnupg2 > made it difficult to configure mutt without gpgme. So why not > enabling gpgme in the packaged versions? >=20 > I decided not to create a PR about this request. If that's wrong, > tell me and I'll create one. For neomutt I haven't added gpgme as the default gpg setup works pretty fine with gnupg2 and the gpg.rc I can be convinced that making gpgme the default= is a good idea, though I have never used gpgme Best regards, Bapt --zxuizdoh2sruf3su Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYHbkEAAoJEGOJi9zxtz5aziUQALP9yiLySpLowO2hAQQmVFEu 3jRzsVvvoS6gpN36CcPDDu3XqXs2j9IAFqlp16G1e5qJ/B2gdZDJ05d6dxswqs8f qAD6k0Mv3Nfe9m+vc04Tqg2YVeeznfjNEOWu573lVmh/JTKKx9qWmLNV7nnjr5Xk tbyWhjY0gWDCJwCp3kYvco70x58TU8Zphfk5b+wtaX/05yrFxCcHqQJM2ou7Navq iwRz5Cu7UNCFsLH/8W0TiuN21/BbsBBX6WE5uCApXTIblnjZDWCEIN8BJj8YOfoj E7aCyIZIR8Urz8fMRyR0mUoSukCFXnVFqeKYtnTFrnUhsNppXTpFL5bEp801ZW7S fpop13XPbxoGbnOp4Vizut5iB/weQ4ky+szwwhaKyqdEBKqlzdpQ4fD+3LrBdAb5 OizSikkEHVSODJHQmXLzKEsUMIjCiJcbV8S7rzs0hwTdhbyca4sXYLMKtkXyhLT4 eVnJEKDEgsDbpdi8mkZjicdHXYIV19xFl/BtoA5eWMYPCTAuodjhn9lcsYlrzQpu iR5iR+pXB4kZ5b+aS80g3XVzASZOPVsjeCcQ4OhxkQ5N4ZISloh0nTCCUJywfioM rZMlibONyaLMCXFZE8Te6exstvitvy3A4UFNnKvpNqZ8p27ZjkhVV0p9v0i7kF5I /Kg949gB531eWsWPI6wE =0q5Y -----END PGP SIGNATURE----- --zxuizdoh2sruf3su--