From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) by sourceware.org (Postfix) with ESMTPS id 9E1D73870868 for ; Mon, 1 Jun 2020 19:25:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 9E1D73870868 Received: by mail-io1-xd43.google.com with SMTP id d5so8167559ios.9 for ; Mon, 01 Jun 2020 12:25:51 -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=Eo+BR96q/hyUw2LDPdkYyvHi8nUIfFGF8QyL5pPzK38=; b=qzUvh8TNGnIkfE+cb4uCNdI+WeZyJ067N+6vA9JkV6Jru1T0rm9UNu/MKW9jnTvRnC TfZ4tK+1btRsDbQfwuNA1WDfUKqMNKssbgsJG2N0Kywg4RLEqxbHbg6SwuWYh5yZc/kB B3Ji8lGJ+ap/vCjv02phfiNkvPsZYZOwjCvdDRg1b84eF/RXJDX/m6nlyaLJ3Az53e7r KHIp06aO6pSz2UmcIKKSvXWUaYBLRCKGP7wcOtI3GrAf7sWu+PXhQr9uW6iXra9NZv6O Oe6S9MIcz+VhKJP+hYgyKkV+Y8gblfIWpE3CbI05fYN8xLhBDf+ASXEZQ8wtbnL4QtYg fXIg== X-Gm-Message-State: AOAM531AGVEBT9qoj4IG2TkeIUlMKBv7rUvY5rtcV7XutVZ8U/BSa+RD rqRbOhpN63PWJbEY8vx/VSM+Rxc4cCHXhaUzVvU= X-Google-Smtp-Source: ABdhPJyEYFa4NrZe9W+yuVK4M8cNb+p0Phpt9ez8nt/LEas9wwLQWuxKSgH9E7CVq0BVv/LtwO8ty6jXsTStLNPBVbY= X-Received: by 2002:a02:cc49:: with SMTP id i9mr15036529jaq.52.1591039551138; Mon, 01 Jun 2020 12:25:51 -0700 (PDT) MIME-Version: 1.0 References: <20200601181037.GB16575@redhat.com> <74ac89cb-31b7-770b-0e2a-c1256db64db1@gmail.com> In-Reply-To: <74ac89cb-31b7-770b-0e2a-c1256db64db1@gmail.com> From: Jonathan Wakely Date: Mon, 1 Jun 2020 20:25:40 +0100 Message-ID: Subject: Re: sign_and_send_pubkey: signing failed: agent refused operation To: Martin Sebor Cc: "Frank Ch. Eigler" , Overseers mailing list , gcc mailing list Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, 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: Mon, 01 Jun 2020 19:26:02 -0000 On Mon, 1 Jun 2020 at 20:16, Martin Sebor via Gcc wrote: > > On 6/1/20 12:10 PM, Frank Ch. Eigler wrote: > > Hi - > > > >> git pull from the GCC and Glibc repos is failing for me with the error > >> below. It worked fine last week and I haven't made any changes to my > >> ssh keys. > > > > And are you logging in from the same workstation with access to the same > > set of ssh private keys? > > Yes. > > > > >> Is this a transient glitch or has something changed recently that I > >> need to make some adjustments for? > > > > I know of nothing relevant that has changed on the sourceware side. > > > >> sign_and_send_pubkey: signing failed: agent refused operation > >> msebor@gcc.gnu.org: Permission denied (publickey). > >> fatal: Could not read from remote repository. > > > > The usual advice is to run % ssh -vv gcc.gnu.org alive > > and report the ssh level error. > > > > "agent refused operation" sounds like a problem on the client end. > > Until last week, when I ran git pull from the GCC or Glibc repo > I'd get prompted for my password. I'd either type it in or hit > ctrl-C, enter ssh-add, and start over. > > After deleting ~/.ssh/known_hosts to resolve the problem I asked > about last week (Re: ssh key conflicts), I'm no longer prompted > for my password. Instead, I get the error above. Is ~/.ssh/known_hosts no longer present? Is ~/.ssh writable by your user? The ssh client (or the agent) will try to create ~/.ssh/known_hosts if it doesn't exist, to add the host key. If ~/.ssh is not writable that will fail. > Both of this is new (I think since the recent server changes). Now The host key did change after the server upgrade, that's expected. The other problem is not caused by the server. > that I've seen it and know what to expect I can adjust to it but it > seems like things have gotten worse. Certainly the errors I got > in both instances (i.e., last week as well as today) are not helpful. SSH errors usually aren't. > I captured the ssh -vv gcc.gnu.org output below for a successful > invocation and a failed one if that sheds more light on why it's > failing in (to me) a mysterious way. The failed attempt shows that your public key is offered to the server, and the server says it will accept it (meaning it matches a ~/.ssh/authorized_keys entry on the server) but then your client refuses to use that key. Check your ~/.ssh and ~/.ssh/id_rsa* permissions.