| 1 |
On Mon, Jun 25 2018, Mick wrote: |
| 2 |
|
| 3 |
> On Monday, 25 June 2018 10:19:07 BST Marc Joliet wrote: |
| 4 |
>> Am Montag, 25. Juni 2018, 03:10:57 CEST schrieb allan gottlieb: |
| 5 |
>> > I have two laptops call them A and B both running gentoo. |
| 6 |
>> > I recently did on each an emerge --sync after a long absence. |
| 7 |
>> > |
| 8 |
>> > The large emerge --update @world's finally finished on each machine. One |
| 9 |
>> > new behavior is that |
| 10 |
>> > |
| 11 |
>> > If I use the console to log into A and then ssh to B, I get |
| 12 |
>> > |
| 13 |
>> > warning: agent returned different signature type ssh-rsa (expected |
| 14 |
>> > rsa-sha2-512) |
| 15 |
>> > |
| 16 |
>> > If I use the console to log into B and then ssh to A, |
| 17 |
>> > I get the same warning. |
| 18 |
>> > |
| 19 |
>> > I see no ill effects. |
| 20 |
>> > |
| 21 |
>> > Need I take any action? |
| 22 |
>> > |
| 23 |
>> > thanks in advance, |
| 24 |
>> > allan |
| 25 |
>> |
| 26 |
>> I saw the same, but it was temporary. I use gpg-agent instead of ssh-agent, |
| 27 |
>> so I assumed it had to do with that, and then the warning disappeared after |
| 28 |
>> upgrading gnupg, but perhaps that was just a coincidence? |
| 29 |
> |
| 30 |
> This warning message is generated when you are using gpg-agent as ssh-agent |
| 31 |
> and there is a mismatch on the ciphers between the two - i.e. when gpg-agent |
| 32 |
> can't/won't use the ciphers expected by sshd. |
| 33 |
> |
| 34 |
> Do you get the same warning when you exclude the agent from the equation? |
| 35 |
> |
| 36 |
> ssh -a -i $HOME/.ssh/Your_SSH_Key user@host |
| 37 |
|
| 38 |
Yes, thanks. |
| 39 |
allan |
| 40 |
|
| 41 |
gottlieb@E7450 /local/allan/gottlieb $ ssh -a -i $HOME/.ssh/id_rsa E6430 |
| 42 |
warning: agent returned different signature type ssh-rsa (expected rsa-sha2-512) |
| 43 |
You have new mail in folder /var/mail/gottlieb. |
Archives