From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk1-xa35.google.com (mail-vk1-xa35.google.com [IPv6:2607:f8b0:4864:20::a35]) by sourceware.org (Postfix) with ESMTPS id D06743851C2B for ; Tue, 2 Jun 2020 20:00:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D06743851C2B Received: by mail-vk1-xa35.google.com with SMTP id z3so1210638vka.10 for ; Tue, 02 Jun 2020 13:00:20 -0700 (PDT) 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=jHjjcJKQsjs1+H+gRD9CGpJJwQNlMMA7p04yITAJ01E=; b=EFH/+mc7GwwMj3wUy+JFv6bWnTZ+oRLZ39+K7sNOcCSZoo1eacMK0UZGQBZaqtotr7 rALQ7oQopDO0DyXzGOGG4bA0qUmYl2R1uYMDsmUMpKC7QvAvDZ16UBqsmdJxjpshaOg8 tRh6VQY9BuuZKDb/OmVQrfldY1z3FXaVJ1EbTOfJUv8WvN8yV4uYAPTN20QxIKaI2ROW 9vpf6iHuzY+vjzUnxLN54+2x5unEGW9BylIcIgPlraHcG28jZrG8+wXdXWPaB3pUoh+2 bvylcNGxRfAco2yCqtLXLllF/e5DjchdhRzPVW9ENieOvEdB0YTzmew2HHJsN+ZcrOA3 sE9g== X-Gm-Message-State: AOAM5318NJTBnNoCx7EMU0Lg4xFvOrMqisxUDWM7U99xWzQ3fLystsTU r//DnWoq+io2B5FSIhCD7/rY9EKdbkOs/PbatnLcXA== X-Google-Smtp-Source: ABdhPJz3NeJZrd0hKCFZAWfTupUMRX2iN3gdV4GJoKOkYqqvpeo3awhaPmjJ/FuLlodrhAnzyJnKBb7xlphO453f99I= X-Received: by 2002:a1f:1a4e:: with SMTP id a75mr10816916vka.10.1591128020359; Tue, 02 Jun 2020 13:00:20 -0700 (PDT) MIME-Version: 1.0 References: <20200601181037.GB16575@redhat.com> <74ac89cb-31b7-770b-0e2a-c1256db64db1@gmail.com> <20200601195301.GC16575@redhat.com> In-Reply-To: From: Jim Wilson Date: Tue, 2 Jun 2020 13:00:09 -0700 Message-ID: Subject: Re: sign_and_send_pubkey: signing failed: agent refused operation To: Martin Sebor Cc: "Frank Ch. Eigler" , gcc mailing list , Overseers mailing list Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 20:00:22 -0000 On Mon, Jun 1, 2020 at 3:33 PM Martin Sebor via Gcc wrote: > So it sounds like you wouldn't expect the "agent refused operation" > error either, and it's not just a poor error message that I should > learn to live with. That makes me think I should try to figure out > what's wrong. I think the ~/.ssh/ contents are pretty standard: My experience with Ubuntu 18.04 is that 2K bit keys aren't accepted by something (gnome UI?) anymore. I had to upgrade to 4K bit keys. Though oddly ssh-keygen still generates 2K bit keys by default even though they won't be accepted by the gnome UI (or whatever). The work around is to run ssh-add manually to register your 2K bit key, because ssh-add will still accept 2K bit keys, and then ssh will work, and can be used to install a 4K bit public key on the other side, and then things will work normally again. A web search suggested that there was some security problem with 2K bit keys and apparently they are trying to force people to upgrade, but the inconsistent approach here between different packages makes this confusing as to what is actually going on. Jim