sshd does not properly initialize libgcrypt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openssh (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
The following warnings can be found in syslog:
pieter-
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:
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.
libpam-ccreds and sudo seem to have the same issue /bugs.launchpad .net/ubuntu/ +source/ libpam- ccreds/ +bug/869166 /bugs.launchpad .net/ubuntu/ +source/ sudo/+bug/ 1397663
https:/
https:/