From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: git wants a password to portage sync
Date: Wed, 6 Dec 2017 18:51:24 +0800 [thread overview]
Message-ID: <3f6a4da3-565c-14ca-7882-f479e0ef8d7f@iinet.net.au> (raw)
In-Reply-To: <92c56489-aebb-20c9-a098-cb315a023d71@gmail.com>
On 06/12/17 06:43, Alan McKinnon wrote:
> On 06/12/2017 00:35, Ian Zimmerman wrote:
>> On 2017-12-06 05:53, Bill Kenworthy wrote:
>>
>>> No, all machines are set up as keyless ssh - git has never needed it
>>> there. In frustration I created keys and set portage up as a keyless
>>> ssh account as well, no change.
>>
>> ssh messages are sometimes misleading. For instance, ssh would say
>> something like "pubkey authentication failed" when in fact I prohibited
>> root logins on the server.
>>
>> I'd try connecting with bare ssh as the user in question, with maximum
>> verbosity turned on (-vvv).
>>
>
>
> The error messages from the ssh client are, by design, intentionally
> vague. They amount to a teeny bit more detail than just "something went
> wrong", plus the available auth methods listed in parenthesis.
>
> This is because the sshd server avoids information leakage that
> attackers could use.
>
> To find out why ssh does not work, start by looking at the server logs,
> then examine the client is nothing obvious stands out.
>
Got it! Needed ssh keys for portage@remote from root@local. Its working
but no idea why its only this machine that required it.
Thanks,
BillK
prev parent reply other threads:[~2017-12-06 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 10:40 [gentoo-user] git wants a password to portage sync Bill Kenworthy
2017-12-05 13:15 ` [gentoo-user] " Nikos Chantziaras
2017-12-05 21:53 ` Bill Kenworthy
2017-12-05 22:35 ` Ian Zimmerman
2017-12-05 22:43 ` Alan McKinnon
2017-12-06 10:51 ` Bill Kenworthy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f6a4da3-565c-14ca-7882-f479e0ef8d7f@iinet.net.au \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox