Thank you for taking the time to file this bug and helping to make
Ubuntu better.
I cannot reproduce this on Trusty. Additionally, I don't see that the
openssh-server or openssh-client binary packages pull in gcrypt at all.
Are you sure this isn't some PAM module that uses gcrypt that ssh is
simply calling due to its configuration? This would explain sudo as
well.
Please could you post steps to reproduce this bug on a fresh 14.04
installation and then change the bug status back to New?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1397666
Title:
sshd does not properly initialize libgcrypt
Status in openssh package in Ubuntu:
Incomplete
Bug description:
The following warnings can be found in syslog:
pieter-local@test-02:~$ grep "please fix the application" /var/log/syslog
|grep sshd
Nov 30 12:19:21 test-02 sshd[1226]: Libgcrypt warning: missing initialization
- please fix the application
Nov 30 12:20:06 test-02 sshd[1293]: Libgcrypt warning: missing initialization
- please fix the application
Nov 30 12:24:27 test-02 sshd[1089]: Libgcrypt warning: missing initialization
- please fix the application
Nov 30 12:40:34 test-02 sshd[1257]: Libgcrypt warning: missing initialization
- please fix the application
Nov 30 12:40:58 test-02 sshd[1324]: Libgcrypt warning: missing initialization
- please fix the application
Nov 30 12:41:36 test-02 sshd[1403]: Libgcrypt warning: missing initialization
- please fix the application
Nov 30 13:16:30 test-02 sshd[1095]: Libgcrypt warning: missing initialization
- please fix the application
Nov 30 13:16:46 test-02 sshd[1228]: Libgcrypt warning: missing initialization
- please fix the application
These seem to be related to the following change:
http://git.gnupg.org/cgi-
bin/gitweb.cgi?p=libgcrypt.git;a=commitdiff_plain;h=7627f9646701e88c827bbadd1231221d5f0c89a6
It looks like that sshd does not properly initialize libgcrypt. From
looking at the above patch, it does not seem to do any harm, since the
lib will then initialize itself. When trying to find issues on a
system, warnings like this will make things a bit more cloudy then
needed. A proper implementation for this would be beneficial to the
system in general.
These warnings are present in 14.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1397666/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
