From owner-freebsd-ports@freebsd.org Fri Jul 20 14:23:30 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 848C41047522 for ; Fri, 20 Jul 2018 14:23:30 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from mail-yb0-x234.google.com (mail-yb0-x234.google.com [IPv6:2607:f8b0:4002:c09::234]) (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 23DF67EAC6 for ; Fri, 20 Jul 2018 14:23:30 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by mail-yb0-x234.google.com with SMTP id i9-v6so4692919ybo.5 for ; Fri, 20 Jul 2018 07:23:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamw-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hqdojOoCEY0eDCA8KPJ1EVWqzmFNd08w7Svg3koVmGA=; b=ZGdJSBn2yx3xT5OFGLECE90lbJRp3TzgPtEqQs7u4/m/2NXsEeFWKs0ARedbGYenLj Zqrv+cpFISSmJsuY80SL2u9/Y080L6naCQ0pUjgLA1zBskFjk8BLwaKY+hy8w0FBGBjO MWLkWp9GZuWfw4O5IMVRk97vIPnPizwqwqWOFBrqnKU3JxWbtCKTSis9gDcjfaes/faZ COZoulS58jvjmGySTchNkv59JQLuuOymdurXhp1Fuwmlro0isMAIMK2m73zXvnX5SvOO uiLYBNlxUVONka6LFFKNy4BwF3lmZ5y27s4xKtnYwwy5bkKGMVNwYDNIDElKgc78LS/L S7Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hqdojOoCEY0eDCA8KPJ1EVWqzmFNd08w7Svg3koVmGA=; b=cOwrICfHgOUVeIITIACxOHYqFrFguI1gt5YXo8WkbSQYqtjNw3+On0wC1ZtTEm1isi oHR/ZQm2FrcHjXq0hbM1YTke26FL2UJftdyak9Xq6OknhP8fPO1epLOQlC2oXiHzTniA SCQMSaPCe4FBfVU5y+OTfe6iMLw1hck7xn5jQmKe5fOXeI3DqUPQBkWZvcdnT0QN4Idc GpI9u8M/1ulwWf18+Fm8SWajJXveBevd1p7YTgOCmh8gtXixSk2GOdv1QnuZvORLnt7p D5GfFkIjxedSJn95YPsnZQzDmGPguQf7eGlVSM63OytImJa2W1STCmes0lnDR0BMpFIh Vvwg== X-Gm-Message-State: AOUpUlFZXB/3b9eTuIFDuAbkFCWYg2kwohrO/WEbQ2k+D4b7bShpYtSv URC5E27oXWVNKPG/ytNf7W3XVap3j340hV0kESDgtiT3v3A= X-Google-Smtp-Source: AAOMgpeu0xkcHWVPHFvfsxpF4WVQpWQDj+pRuLt0eVcqQs3PUOqRVScYT8P9BhNO7W9W64kw4hIsBF5GumNg28tjtig= X-Received: by 2002:a25:ad9a:: with SMTP id z26-v6mr1128464ybi.246.1532096609143; Fri, 20 Jul 2018 07:23:29 -0700 (PDT) MIME-Version: 1.0 References: <20180720125251.GE12958@albert.catwhisker.org> In-Reply-To: <20180720125251.GE12958@albert.catwhisker.org> From: Adam Weinberger Date: Fri, 20 Jul 2018 08:23:13 -0600 Message-ID: Subject: Re: After mutt-1.10.0_1 -> mutt-1.10.1 upgrade, gnupg fails To: david@catwhisker.org Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2018 14:23:30 -0000 On Fri, Jul 20, 2018 at 6:53 AM David Wolfskill wrote: > > This is running: > > FreeBSD g1-215.catwhisker.org 11.2-STABLE FreeBSD 11.2-STABLE #685 r336523M/336541:1102501: Fri Jul 20 03:40:05 PDT 2018 root@g1-215.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 > > and after updating all installed ports to reflect the ports "head" > branch at r475002. > > A symptom is that an attempt to send a signed, unencrypted message > yields a failure, with the messages: > > | gpg: skipped "0x6757003D": Unusable secret key > | gpg: signing failed: Unusable secret key > > This works on another machine (the one I'm using to send this > message), with the same gnupg/mutt setup, but running mutt-1.10.0_1. > > I have not configured mutt to use gpgme, though I'm willing to try > it. I recall that I needed to tweak ~/.muttrc a bit after the > gnupg-2.0 -> gnupg-2.1 update -- though that change was merely > commenting out the 'pgp_verify_command' line. > > I note that a result of the mutt upgrade is that > /usr/local/share/examples/mutt/gpg.rc has changed, but that change > was merely to remove the pgp_decryption_okay setting (which I don't > have) and add 'set pgp_check_gpg_decrypt_status_fd'; I tried adding > that, to no avail. > > Any hints or suggestions? > > Thanks! > > Peace, > david Hi, David! FWIW, I'd highly suggest using gpgme. set crypt_use_gpgme=yes has replaced my entire gnupg command file. gnupg was just updated to 2.2.9 a few days ago, so that might be the cause (and not mutt). Are you able to successfully use that key from the command-line? # Adam -- Adam Weinberger adamw@adamw.org https://www.adamw.org