[Bug 357998] Re: openssh-client (amd64) can't login after upgrade to jaunty

[Maarten Bezemer]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version. When you test
it and it is still an issue, kindly upload the updated logs by running
apport-collect 357998 and any other logs that are relevant for this
particular issue.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/357998

Title:
  openssh-client (amd64) can't login after upgrade to jaunty

Status in Seahorse:
  New
Status in “openssl” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: openssh-client

  Hi,

  I've just upgraded an AMD64 machine from intrepid to jaunty, and since
  then my ssh-client can't login to a debian machine with its sshd
  anymore. The secret key is not accepted anymore. The client just says
  that the server did not accept the public key. The (unmodified) debian
  server has for each login attempt an entry in the log

  sshd[680]: error: RSA_public_decrypt failed:
  error:0407006A:lib(4):func(112):reason(106)

  The login still worked two hours ago, just until the upgrade from
  intrepid to jaunty.

  Interestingly, I did not see that problem on an x86 machine where I
  did the same upgrade. Seems to be an AMD64 specific bug in the crypto
  stuff.

  regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/357998/+subscriptions