Comment 26 for bug 1315964

[Impact]

An uninitialized variable makes cryptkeeper randomly crash on start
in Trusty.

The fix for it had been applied in newer releases (see bug 1420812),
starting from Vivid. Would be nice to apply it in Trusty as well.

The debdiff which is attached to this report contains the fix.

[Test Case]

Since it's a random crash, it may take several attempts to reproduce
it. So just run cryptkeeper a few times from the terminal. It should
crash right on start if it hits some random value in uninitialized
variable.

[Regression Potential]

None. It had been confirmed that the patched version of cryptkeeper
doesn't crash on start anymore (reported by Xenial users for example).