I have found this http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=483838">bug in Debian. I know for me that I
use a 2039 bit RSA key to reduce the chance of a differential analysis
attack. I will check with a 2048 bit key and see if this fixes the
problem.
** Bug watch added: Debian Bug tracker
This is also present on x86, as per attachment.
** Attachment added: "attach1.txt"
http://launchpadlibrarian.net/26209636/attach1.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a membe
Hi,
I've go the same problem.
Upgrade 8.04 64bits to 9.04 bits and I've got Debian server (Lenny
64bits)
On my server this error was report on /var/log/auth.log
"sshd[7864]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)"
--
openssh-client (amd64) can't login af
I am also having the exact same problem, on x86, right after upgrading
from intrepid to jaunty. I can also confirm that the workaround by
Nathan works. I am pretty sure it is a problem with seahorse, because
nothing has changed on the server or with the key. I can login from
another machine with th
Another workaround seems to be to disable gnome messing in the key
management - with the gconf-editor go to apps/gnome-keyring/daemon-
components and disable 'ssh'. A few colleagues are using this (on x86)
and it works.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.la
This happens for me on i686 as well after upgrading from Intrepid to
Jaunty. It appears to be related to seahorse-agent rather than the
openssh-client.
If I run:
SSH_AUTH_SOCK=0 ssh localhost
I am prompted for my passphrase for my key and it authenticates me fine.
If I run:
eval `ssh-agent`
ss
Could you post ssh -vvv output please?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
ok, is attached. btw, the ssh login fails even if I try login to
localhost, i.e. to the ubuntu machine itself.
I had an RSA key only, the one that failed ufter upgrade.
I could workaround by generating an dsa key, which works.
Might be related to debian bug #357998
I am not really sure whether
$ openssl errstr 0407006A
error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Likely, though not certain, to be a bug in openssl rather than openssh.
** Package changed: openssh (Ubuntu) => openssl (Ubuntu)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubu
Surely you don't mean Debian bug #357998? It's a different bug, and I
find the coincidence of a Debian bug report with the same bug number as
the corresponding Ubuntu bug report a bit hard to swallow :-)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs
Since you can reproduce this on a machine you control, could you also
run 'sudo /etc/init.d/ssh stop', then run 'sudo /usr/sbin/sshd -ddd',
try connecting to it to reproduce this bug, and post the output of that?
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Here it is...
** Attachment added: "ssh-debug.txt"
http://launchpadlibrarian.net/25246203/ssh-debug.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I can confirm that it worked again using a newly generated 2048bit RSA
key. I had a 2047 Bit key before.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Same here. ssh / authorized_keys was working fine for rsa logins with Ubuntu
8.10 on AMD arch.
I upgraded to 9.04 on my desktop, and now I can not login to my server with my
rsa key.
May 24 09:26:29 sshd[25434]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)
My s
My testing is same a others. I had to traverse two bugs to find
solution.
SUMMARY:
* After upgrade to 9.04, can not ssh with rsa keys.
* Using my pre-existing non-standard bit length rsa key (1999), ssh to host
generates this error in /var/log/messages: "error: RSA_public_decrypt failed:
error:0
I have found this http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=483838">bug in Debian. I know for me that I
use a 2039 bit RSA key to reduce the chance of a differential analysis
attack. I will check with a 2048 bit key and see if this fixes the
problem.
** Bug watch added: Debian Bug tracker
This is also present on x86, as per attachment.
** Attachment added: "attach1.txt"
http://launchpadlibrarian.net/26209636/attach1.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a membe
I can confirm that it worked again using a newly generated 2048bit RSA
key. I had a 2047 Bit key before.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Hi,
I've go the same problem.
Upgrade 8.04 64bits to 9.04 bits and I've got Debian server (Lenny
64bits)
On my server this error was report on /var/log/auth.log
"sshd[7864]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)"
--
openssh-client (amd64) can't login af
I am also having the exact same problem, on x86, right after upgrading
from intrepid to jaunty. I can also confirm that the workaround by
Nathan works. I am pretty sure it is a problem with seahorse, because
nothing has changed on the server or with the key. I can login from
another machine with th
Another workaround seems to be to disable gnome messing in the key
management - with the gconf-editor go to apps/gnome-keyring/daemon-
components and disable 'ssh'. A few colleagues are using this (on x86)
and it works.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.la
This happens for me on i686 as well after upgrading from Intrepid to
Jaunty. It appears to be related to seahorse-agent rather than the
openssh-client.
If I run:
SSH_AUTH_SOCK=0 ssh localhost
I am prompted for my passphrase for my key and it authenticates me fine.
If I run:
eval `ssh-agent`
ss
I can confirm that it worked again using a newly generated 2048bit RSA
key. I had a 2047 Bit key before.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
This happens for me on i686 as well after upgrading from Intrepid to
Jaunty. It appears to be related to seahorse-agent rather than the
openssh-client.
If I run:
SSH_AUTH_SOCK=0 ssh localhost
I am prompted for my passphrase for my key and it authenticates me fine.
If I run:
eval `ssh-agent`
ss
I have found this http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=483838">bug in Debian. I know for me that I
use a 2039 bit RSA key to reduce the chance of a differential analysis
attack. I will check with a 2048 bit key and see if this fixes the
problem.
** Bug watch added: Debian Bug tracker
Hi,
I've go the same problem.
Upgrade 8.04 64bits to 9.04 bits and I've got Debian server (Lenny
64bits)
On my server this error was report on /var/log/auth.log
"sshd[7864]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)"
--
openssh-client (amd64) can't login af
I am also having the exact same problem, on x86, right after upgrading
from intrepid to jaunty. I can also confirm that the workaround by
Nathan works. I am pretty sure it is a problem with seahorse, because
nothing has changed on the server or with the key. I can login from
another machine with th
Another workaround seems to be to disable gnome messing in the key
management - with the gconf-editor go to apps/gnome-keyring/daemon-
components and disable 'ssh'. A few colleagues are using this (on x86)
and it works.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.la
This is also present on x86, as per attachment.
** Attachment added: "attach1.txt"
http://launchpadlibrarian.net/26209636/attach1.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a membe
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Here it is...
** Attachment added: "ssh-debug.txt"
http://launchpadlibrarian.net/25246203/ssh-debug.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Could you post ssh -vvv output please?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
ok, is attached. btw, the ssh login fails even if I try login to
localhost, i.e. to the ubuntu machine itself.
I had an RSA key only, the one that failed ufter upgrade.
I could workaround by generating an dsa key, which works.
Might be related to debian bug #357998
I am not really sure whether
$ openssl errstr 0407006A
error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Likely, though not certain, to be a bug in openssl rather than openssh.
** Package changed: openssh (Ubuntu) => openssl (Ubuntu)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubu
Surely you don't mean Debian bug #357998? It's a different bug, and I
find the coincidence of a Debian bug report with the same bug number as
the corresponding Ubuntu bug report a bit hard to swallow :-)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs
Since you can reproduce this on a machine you control, could you also
run 'sudo /etc/init.d/ssh stop', then run 'sudo /usr/sbin/sshd -ddd',
try connecting to it to reproduce this bug, and post the output of that?
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad
Same here. ssh / authorized_keys was working fine for rsa logins with Ubuntu
8.10 on AMD arch.
I upgraded to 9.04 on my desktop, and now I can not login to my server with my
rsa key.
May 24 09:26:29 sshd[25434]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)
My s
My testing is same a others. I had to traverse two bugs to find
solution.
SUMMARY:
* After upgrade to 9.04, can not ssh with rsa keys.
* Using my pre-existing non-standard bit length rsa key (1999), ssh to host
generates this error in /var/log/messages: "error: RSA_public_decrypt failed:
error:0
This is also present on x86, as per attachment.
** Attachment added: "attach1.txt"
http://launchpadlibrarian.net/26209636/attach1.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a membe
Hi,
I've go the same problem.
Upgrade 8.04 64bits to 9.04 bits and I've got Debian server (Lenny
64bits)
On my server this error was report on /var/log/auth.log
"sshd[7864]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)"
--
openssh-client (amd64) can't login af
I am also having the exact same problem, on x86, right after upgrading
from intrepid to jaunty. I can also confirm that the workaround by
Nathan works. I am pretty sure it is a problem with seahorse, because
nothing has changed on the server or with the key. I can login from
another machine with th
Another workaround seems to be to disable gnome messing in the key
management - with the gconf-editor go to apps/gnome-keyring/daemon-
components and disable 'ssh'. A few colleagues are using this (on x86)
and it works.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.la
This happens for me on i686 as well after upgrading from Intrepid to
Jaunty. It appears to be related to seahorse-agent rather than the
openssh-client.
If I run:
SSH_AUTH_SOCK=0 ssh localhost
I am prompted for my passphrase for my key and it authenticates me fine.
If I run:
eval `ssh-agent`
ss
Could you post ssh -vvv output please?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
ok, is attached. btw, the ssh login fails even if I try login to
localhost, i.e. to the ubuntu machine itself.
I had an RSA key only, the one that failed ufter upgrade.
I could workaround by generating an dsa key, which works.
Might be related to debian bug #357998
I am not really sure whether
$ openssl errstr 0407006A
error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Likely, though not certain, to be a bug in openssl rather than openssh.
** Package changed: openssh (Ubuntu) => openssl (Ubuntu)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubu
Surely you don't mean Debian bug #357998? It's a different bug, and I
find the coincidence of a Debian bug report with the same bug number as
the corresponding Ubuntu bug report a bit hard to swallow :-)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs
Since you can reproduce this on a machine you control, could you also
run 'sudo /etc/init.d/ssh stop', then run 'sudo /usr/sbin/sshd -ddd',
try connecting to it to reproduce this bug, and post the output of that?
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Here it is...
** Attachment added: "ssh-debug.txt"
http://launchpadlibrarian.net/25246203/ssh-debug.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I have found this http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=483838">bug in Debian. I know for me that I
use a 2039 bit RSA key to reduce the chance of a differential analysis
attack. I will check with a 2048 bit key and see if this fixes the
problem.
** Bug watch added: Debian Bug tracker
I can confirm that it worked again using a newly generated 2048bit RSA
key. I had a 2047 Bit key before.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Same here. ssh / authorized_keys was working fine for rsa logins with Ubuntu
8.10 on AMD arch.
I upgraded to 9.04 on my desktop, and now I can not login to my server with my
rsa key.
May 24 09:26:29 sshd[25434]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)
My s
My testing is same a others. I had to traverse two bugs to find
solution.
SUMMARY:
* After upgrade to 9.04, can not ssh with rsa keys.
* Using my pre-existing non-standard bit length rsa key (1999), ssh to host
generates this error in /var/log/messages: "error: RSA_public_decrypt failed:
error:0
I have found this http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=483838">bug in Debian. I know for me that I
use a 2039 bit RSA key to reduce the chance of a differential analysis
attack. I will check with a 2048 bit key and see if this fixes the
problem.
** Bug watch added: Debian Bug tracker
This is also present on x86, as per attachment.
** Attachment added: "attach1.txt"
http://launchpadlibrarian.net/26209636/attach1.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a membe
I can confirm that it worked again using a newly generated 2048bit RSA
key. I had a 2047 Bit key before.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Hi,
I've go the same problem.
Upgrade 8.04 64bits to 9.04 bits and I've got Debian server (Lenny
64bits)
On my server this error was report on /var/log/auth.log
"sshd[7864]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)"
--
openssh-client (amd64) can't login af
I am also having the exact same problem, on x86, right after upgrading
from intrepid to jaunty. I can also confirm that the workaround by
Nathan works. I am pretty sure it is a problem with seahorse, because
nothing has changed on the server or with the key. I can login from
another machine with th
Another workaround seems to be to disable gnome messing in the key
management - with the gconf-editor go to apps/gnome-keyring/daemon-
components and disable 'ssh'. A few colleagues are using this (on x86)
and it works.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.la
This happens for me on i686 as well after upgrading from Intrepid to
Jaunty. It appears to be related to seahorse-agent rather than the
openssh-client.
If I run:
SSH_AUTH_SOCK=0 ssh localhost
I am prompted for my passphrase for my key and it authenticates me fine.
If I run:
eval `ssh-agent`
ss
Same here. ssh / authorized_keys was working fine for rsa logins with Ubuntu
8.10 on AMD arch.
I upgraded to 9.04 on my desktop, and now I can not login to my server with my
rsa key.
May 24 09:26:29 sshd[25434]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)
My s
My testing is same a others. I had to traverse two bugs to find
solution.
SUMMARY:
* After upgrade to 9.04, can not ssh with rsa keys.
* Using my pre-existing non-standard bit length rsa key (1999), ssh to host
generates this error in /var/log/messages: "error: RSA_public_decrypt failed:
error:0
Could you post ssh -vvv output please?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
ok, is attached. btw, the ssh login fails even if I try login to
localhost, i.e. to the ubuntu machine itself.
I had an RSA key only, the one that failed ufter upgrade.
I could workaround by generating an dsa key, which works.
Might be related to debian bug #357998
I am not really sure whether
$ openssl errstr 0407006A
error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Likely, though not certain, to be a bug in openssl rather than openssh.
** Package changed: openssh (Ubuntu) => openssl (Ubuntu)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubu
Surely you don't mean Debian bug #357998? It's a different bug, and I
find the coincidence of a Debian bug report with the same bug number as
the corresponding Ubuntu bug report a bit hard to swallow :-)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs
Since you can reproduce this on a machine you control, could you also
run 'sudo /etc/init.d/ssh stop', then run 'sudo /usr/sbin/sshd -ddd',
try connecting to it to reproduce this bug, and post the output of that?
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Here it is...
** Attachment added: "ssh-debug.txt"
http://launchpadlibrarian.net/25246203/ssh-debug.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Same here. ssh / authorized_keys was working fine for rsa logins with Ubuntu
8.10 on AMD arch.
I upgraded to 9.04 on my desktop, and now I can not login to my server with my
rsa key.
May 24 09:26:29 sshd[25434]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)
My s
My testing is same a others. I had to traverse two bugs to find
solution.
SUMMARY:
* After upgrade to 9.04, can not ssh with rsa keys.
* Using my pre-existing non-standard bit length rsa key (1999), ssh to host
generates this error in /var/log/messages: "error: RSA_public_decrypt failed:
error:0
Could you post ssh -vvv output please?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
ok, is attached. btw, the ssh login fails even if I try login to
localhost, i.e. to the ubuntu machine itself.
I had an RSA key only, the one that failed ufter upgrade.
I could workaround by generating an dsa key, which works.
Might be related to debian bug #357998
I am not really sure whether
$ openssl errstr 0407006A
error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Likely, though not certain, to be a bug in openssl rather than openssh.
** Package changed: openssh (Ubuntu) => openssl (Ubuntu)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubu
Surely you don't mean Debian bug #357998? It's a different bug, and I
find the coincidence of a Debian bug report with the same bug number as
the corresponding Ubuntu bug report a bit hard to swallow :-)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs
Since you can reproduce this on a machine you control, could you also
run 'sudo /etc/init.d/ssh stop', then run 'sudo /usr/sbin/sshd -ddd',
try connecting to it to reproduce this bug, and post the output of that?
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Here it is...
** Attachment added: "ssh-debug.txt"
http://launchpadlibrarian.net/25246203/ssh-debug.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I have found this http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=483838">bug in Debian. I know for me that I
use a 2039 bit RSA key to reduce the chance of a differential analysis
attack. I will check with a 2048 bit key and see if this fixes the
problem.
** Bug watch added: Debian Bug tracker
This is also present on x86, as per attachment.
** Attachment added: "attach1.txt"
http://launchpadlibrarian.net/26209636/attach1.txt
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a membe
Hi,
I've go the same problem.
Upgrade 8.04 64bits to 9.04 bits and I've got Debian server (Lenny
64bits)
On my server this error was report on /var/log/auth.log
"sshd[7864]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)"
--
openssh-client (amd64) can't login af
I am also having the exact same problem, on x86, right after upgrading
from intrepid to jaunty. I can also confirm that the workaround by
Nathan works. I am pretty sure it is a problem with seahorse, because
nothing has changed on the server or with the key. I can login from
another machine with th
Another workaround seems to be to disable gnome messing in the key
management - with the gconf-editor go to apps/gnome-keyring/daemon-
components and disable 'ssh'. A few colleagues are using this (on x86)
and it works.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.la
This happens for me on i686 as well after upgrading from Intrepid to
Jaunty. It appears to be related to seahorse-agent rather than the
openssh-client.
If I run:
SSH_AUTH_SOCK=0 ssh localhost
I am prompted for my passphrase for my key and it authenticates me fine.
If I run:
eval `ssh-agent`
ss
I can confirm that it worked again using a newly generated 2048bit RSA
key. I had a 2047 Bit key before.
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Same here. ssh / authorized_keys was working fine for rsa logins with Ubuntu
8.10 on AMD arch.
I upgraded to 9.04 on my desktop, and now I can not login to my server with my
rsa key.
May 24 09:26:29 sshd[25434]: error: RSA_public_decrypt failed:
error:0407006A:lib(4):func(112):reason(106)
My s
My testing is same a others. I had to traverse two bugs to find
solution.
SUMMARY:
* After upgrade to 9.04, can not ssh with rsa keys.
* Using my pre-existing non-standard bit length rsa key (1999), ssh to host
generates this error in /var/log/messages: "error: RSA_public_decrypt failed:
error:0
Could you post ssh -vvv output please?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
ok, is attached. btw, the ssh login fails even if I try login to
localhost, i.e. to the ubuntu machine itself.
I had an RSA key only, the one that failed ufter upgrade.
I could workaround by generating an dsa key, which works.
Might be related to debian bug #357998
I am not really sure whether
$ openssl errstr 0407006A
error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Likely, though not certain, to be a bug in openssl rather than openssh.
** Package changed: openssh (Ubuntu) => openssl (Ubuntu)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs/357998
You received this bug notification because you are a member of Ubu
Surely you don't mean Debian bug #357998? It's a different bug, and I
find the coincidence of a Debian bug report with the same bug number as
the corresponding Ubuntu bug report a bit hard to swallow :-)
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad.net/bugs
Since you can reproduce this on a machine you control, could you also
run 'sudo /etc/init.d/ssh stop', then run 'sudo /usr/sbin/sshd -ddd',
try connecting to it to reproduce this bug, and post the output of that?
--
openssh-client (amd64) can't login after upgrade to jaunty
https://bugs.launchpad
1 - 100 of 102 matches
Mail list logo
