From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) by sourceware.org (Postfix) with ESMTPS id 4D35A386EC79 for ; Tue, 2 Jun 2020 20:26:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4D35A386EC79 Received: by mail-qv1-xf2b.google.com with SMTP id e2so763595qvw.7 for ; Tue, 02 Jun 2020 13:26:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=rFzySvWDNJJfnAbR6FB0rzbvo/0kcQkIcMSHkQQwD1o=; b=AdWQ1yCmPEHnjdbPf8DESJtodTxTS10DCEhYoMaAS+3NeZy0E42Y6mJZ/wYreZeluz Pvohosfwr9ADMWgSU7nFdx9JV5WT9RxRS82iaMFUv/Y/YZzJpP6h+S1RiwVijEAZVe1/ qBXVtn1Uvh43Cq4q+W1xE2pe47Vs4HJT9YCu+TYavDJpVzCccizoN5jgYMNEiuuxgUXN XNJzlejxa85fo2gAdiNQX5TBV4NA2rEx0dotW/jKigZCdoOId/6jlOElnH+FL9Z2XZxx beKrbm+HaJG5jxagMbmcUWdKQDxIeDesd7BpxopxvRZur5gWuKTNC0bNeU28XKYxQsBp VoJg== X-Gm-Message-State: AOAM533LkxI7n3Py8HCf69V5CR0V/2pZJAwfzR2H+sywNvc2f1ssxW53 2EySitDzAGBkSkhfX5HjLJA= X-Google-Smtp-Source: ABdhPJwmg8r5tKonyPmHhqihWxXmHemM+aAHySSlTKKPO+TqPx/HEAFa/r6Y0Uitx+eitAEJERdXnw== X-Received: by 2002:a0c:f84c:: with SMTP id g12mr10351370qvo.31.1591129590762; Tue, 02 Jun 2020 13:26:30 -0700 (PDT) Received: from [192.168.0.41] (75-166-103-121.hlrn.qwest.net. [75.166.103.121]) by smtp.gmail.com with ESMTPSA id g5sm3722864qta.46.2020.06.02.13.26.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Jun 2020 13:26:29 -0700 (PDT) Subject: Re: sign_and_send_pubkey: signing failed: agent refused operation To: Overseers mailing list , "Frank Ch. Eigler" Cc: Jonathan Wakely , gcc mailing list References: <20200601181037.GB16575@redhat.com> From: Martin Sebor Message-ID: Date: Tue, 2 Jun 2020 14:26:27 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no 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:26:45 -0000 On 6/1/20 1:12 PM, Jonathan Wakely via Overseers wrote: > On Mon, 1 Jun 2020 at 19:11, Frank Ch. Eigler via Gcc 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? >> >>> 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. > > Yes, it is. "agent" refers to the ssh-agent program. > > Martin, what does 'ssh-add -l' show? > > Is there only one ssh-agent process shown by 'ps -ef | fgrep > [s]sh-agent'? Does its PID match $SSH_AGENT_PID? > > Another possible cause is that the file permissions are not strict > enough on the private key, or on the ~/.ssh directory that contains > it. Key files should be 600 and ~/.ssh should be 700. We solved the problem over IRC last night so just to close the loop on it here: it turned out to be caused by Gnome keyring setting SSH_AUTH_SOCK=/run/user/1000/keyring/ssh. With the environment variable undefined I get prompted for the password as expected. Thank you both again for your help in getting to the bottom of it! Martin