Re: [openpgp] gpg unresponsive

Daniel Huigens <d.huigens@protonmail.com> Mon, 18 July 2022 10:33 UTC

Return-Path: <d.huigens@protonmail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2CECC13D06E for <openpgp@ietfa.amsl.com>; Mon, 18 Jul 2022 03:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3avu5BkNjULh for <openpgp@ietfa.amsl.com>; Mon, 18 Jul 2022 03:33:00 -0700 (PDT)
Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3337CC14F74B for <openpgp@ietf.org>; Mon, 18 Jul 2022 03:33:00 -0700 (PDT)
Date: Mon, 18 Jul 2022 10:32:46 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1658140376; x=1658399576; bh=RXPCdti+FbMmnmIq0KyEzHPk3ld94ti58DVg5k6SXt8=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=yhUt7k5CabyXH427a+tUa9igdRQYFh+DZo8vLVbMbfT3h8Vd6OXJepcMoRe6BuG0w MQiqTTxRrAFCRKLXH1JZ3VDNiofHUzxCBdnQYxGuMOgrRj00X/VlZ6gOWe8iDYua9W pAKvBgQm4AmCkU+P9vUPkgxkKlE0h7YDYe/8Om9S4TE08VrkuVt+8sOuc2YNrxpBFF cffzRJPbXs7GcvXPbpjeCgz5GBKqPcxxulzUo84oHubXIzXtQnzNd7cyg1gRnR4NAc HKIonuXJUDFExVOmZ4FLk+HEF6c1CzbhqdfxeOEixHxLc8sBzK/mX4G0SvdbFm6CDw N/MLUdv2PGiFQ==
To: Yan Rajesh <yanrajesh@gmail.com>
From: Daniel Huigens <d.huigens@protonmail.com>
Cc: openpgp@ietf.org
Reply-To: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <qvXiG8Lio_wzqVvLfo_3DneLovnuks6THYjx-2IiD9-ptbpRhMoat3nQEy3940EVq-xBh6LBj-09dUhdXuRr9PIhnLbvGhOg0C_59wr-650=@protonmail.com>
In-Reply-To: <CAOs5+e3TH5yfVNrOm34eS=T9kf6h1VQ2==TXXVcoER_Z7SHpPA@mail.gmail.com>
References: <CAOs5+e3TH5yfVNrOm34eS=T9kf6h1VQ2==TXXVcoER_Z7SHpPA@mail.gmail.com>
Feedback-ID: 2934448:user:proton
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_U5bNEp7SlNWxTIBbzDx5qXx5X27EqOKBgbhiKETs"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/t022EivvyFHLu9fn6eFk6EYvzlY>
Subject: Re: [openpgp] gpg unresponsive
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2022 10:33:04 -0000

Hi Raj,

This is not the right mailing list for this, I think you want gnupg-users@gnupg.org (https://lists.gnupg.org/mailman/listinfo/gnupg-users).

Best,
Daniel

------- Original Message -------
On Monday, July 18th, 2022 at 09:34, Yan Rajesh <yanrajesh@gmail.com> wrote:

> Hi All,
>
> I need your help.
>
> I have a test case where there is no encrypted document but the message was signed. To verify and decrypt, when I run the command, there is no output or Error message. I have to press Ctrl+c to exit from the command line.
>
> Was it a valid scenario? If not, was there a fix for it?
>
> Iam using Version 2.2.0.
>
> Thanks for your help.
>
> Regards,
> Raj