[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchp
same with ssh -vvv -i linux_test_server -l username 192.168.1.222
I can log in without any problems, but this is expected because there I
specified the key file. The "weird" behavior shows up, if I do not specify any
key file and can still log into the server.
"myself" is the standard ubuntu acc
this account 'myself': are you logged in to it, or did you sudo to it?
As another exercise, please 'ssh -vvv -i linux_test_server -l username
192.168.1.222'.
--
openssh client logs into server without specifying the correct key file.
https://bugs.launchpad.net/bugs/642866
You received this bug n
@C de-Avillez:
In both cases I can connect to 192.168.1.222 without having to specify
any password.
--
openssh client logs into server without specifying the correct key file.
https://bugs.launchpad.net/bugs/642866
You received this bug notification because you are a member of Ubuntu
Server Team
I cannot repeat on Maverick; renaming the id_rsa and id_rsa.pub causes
SSH to drop to password validation.
@Canoblus: some things to try/verify:
1. what happens when you try to open the session as 'ssh -vvv
usern...@192.168.1.222'?
2. what happens when you try to open the session as 'ssh -vvv -i
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/642866/+attachment/1608934/+files/Dependencies.txt
--
openssh client logs into server without specifying the correct key file.
https://bugs.launchpad.net/bugs/642866
You received this bug notification because you are a m
