sudo does not properly initialize libgcrypt

[Pieter H]

The following warnings can be found in syslog:

pieter-local@test-02:~$ grep "please fix the application" /var/log/syslog |grep sudo
Nov 30 12:20:20 test-02 sudo: Libgcrypt warning: missing initialization - please fix the application
Nov 30 12:25:15 test-02 sudo: Libgcrypt warning: missing initialization - please fix the application
Nov 30 12:46:27 test-02 sudo: Libgcrypt warning: missing initialization - please fix the application
Nov 30 13:15:02 test-02 sudo: Libgcrypt warning: missing initialization - please fix the application
Nov 30 13:16:57 test-02 sudo: 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 sudo 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.

[Pieter H (ubuntu-low)]

libpam-ccreds and sshd seem to have the same issue
https://bugs.launchpad.net/ubuntu/+source/libpam-ccreds/+bug/869166
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1397666

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.