randint string expansion causes syslog error message

Bug #1680019 reported by TobiasGrave
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
exim4 (Ubuntu)
Invalid
Undecided
Unassigned
Trusty
Won't Fix
Undecided
Unassigned

Bug Description

Using the randint string expansion (e.g. `exim -be '${randint:10}'`) causes the following syslog error message:

exim: Libgcrypt warning: missing initialization - please fix the application

This is most likely just a cosmetic issue and no critical bug. I am not sure if this is an issue with Exim or a problem that just occurs with the Ubuntu Exim4 package.

Versions:
Ubuntu 14.04.5 LTS
exim4 4.82-3ubuntu2.2
libgcrypt20 1.7.2-2ubuntu1

Tags: bitesize
Revision history for this message
Andreas Metzler (k-launchpad-downhill-at-eu-org) wrote :

This bug only applies to Ubuntu up to trusty (14.04LTS). xenial (16.04LTS) and later releases use GnuTLS 3.x with nettle as crypto backend.

Revision history for this message
Nish Aravamudan (nacc) wrote :

Thank you for filing this bug report! I have subscribed the server team and put it on our backlog.

Changed in exim4 (Ubuntu):
status: New → Invalid
Changed in exim4 (Ubuntu Trusty):
status: New → Confirmed
status: Confirmed → Triaged
tags: added: bitesize
Revision history for this message
Bryce Harrington (bryce) wrote :

Standard support has ended for Trusty. Extended security maintenance options are available, but as described this is a cosmetic issue rather than security, so closing out for now. Upgrading would be recommended if you've not done so already.

Changed in exim4 (Ubuntu Trusty):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.