| 1 |
On 06/12/2017 00:35, Ian Zimmerman wrote: |
| 2 |
> On 2017-12-06 05:53, Bill Kenworthy wrote: |
| 3 |
> |
| 4 |
>> No, all machines are set up as keyless ssh - git has never needed it |
| 5 |
>> there. In frustration I created keys and set portage up as a keyless |
| 6 |
>> ssh account as well, no change. |
| 7 |
> |
| 8 |
> ssh messages are sometimes misleading. For instance, ssh would say |
| 9 |
> something like "pubkey authentication failed" when in fact I prohibited |
| 10 |
> root logins on the server. |
| 11 |
> |
| 12 |
> I'd try connecting with bare ssh as the user in question, with maximum |
| 13 |
> verbosity turned on (-vvv). |
| 14 |
> |
| 15 |
|
| 16 |
|
| 17 |
The error messages from the ssh client are, by design, intentionally |
| 18 |
vague. They amount to a teeny bit more detail than just "something went |
| 19 |
wrong", plus the available auth methods listed in parenthesis. |
| 20 |
|
| 21 |
This is because the sshd server avoids information leakage that |
| 22 |
attackers could use. |
| 23 |
|
| 24 |
To find out why ssh does not work, start by looking at the server logs, |
| 25 |
then examine the client is nothing obvious stands out. |
| 26 |
|
| 27 |
-- |
| 28 |
Alan McKinnon |
| 29 |
alan.mckinnon@×××××.com |
Archives