Bug 12664 - update request: postgrey
Summary: update request: postgrey
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: has_procedure advisory MGA4-64-OK MGA...
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2014-02-08 15:11 CET by Guillaume Rousse
Modified: 2014-02-08 20:40 CET (History)
3 users (show)

See Also:
Source RPM: postgrey
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Guillaume Rousse 2014-02-08 15:11:40 CET 
Stricter taint mode checking in perl 5.18 prevents postgrey to work as a daemon.

To reproduce the issue, just run the following command:
/usr/sbin/postgrey --pidfile=/run/postgrey.pid --unix=/var/spool/postfix/extern/postgrey/socket --auto-whitelist-clients --daemonize

And check than /run/postgrey.pid file has not been created.

The postgrey-1.34-8.2.mga4 release, in updates_testing, fix this issue.

Suggested advisory:
The postgrey package shipped in mageia 4 was not fully functional, as stricter
taint mode checking in perl 5.18 prevented the program to work when daemonized.

Reproducible: 

Steps to Reproduce:
claire robinson 2014-02-08 16:18:59 CET

Whiteboard: (none) => has_procedure

Comment 1 David GEIGER 2014-02-08 17:16:54 CET 
Tested mga4_64,

Before (postgrey-1.34-8.mga4):

# /usr/sbin/postgrey --pidfile=/run/postgrey.pid --unix=/var/spool/postfix/extern/postgrey/socket --auto-whitelist-clients --daemonize

# LC_ALL=C cat /run/postgrey.pid
cat: /run/postgrey.pid: No such file or directory

---------------------------------------------------------------------------------
After update (postgrey-1.34-8.2.mga4):

# /usr/sbin/postgrey --pidfile=/run/postgrey.pid --unix=/var/spool/postfix/extern/postgrey/socket --auto-whitelist-clients --daemonize

# LC_ALL=C cat /run/postgrey.pid
6849

I confirm that this update work and fix this issue.

CC: (none) => geiger.david68210
Whiteboard: has_procedure => has_procedure MGA4-64-OK

Comment 2 David GEIGER 2014-02-08 17:17:55 CET 
Tested mga4_32,

Before (postgrey-1.34-8.mga4):

# /usr/sbin/postgrey --pidfile=/run/postgrey.pid --unix=/var/spool/postfix/extern/postgrey/socket --auto-whitelist-clients --daemonize

# LC_ALL=C cat /run/postgrey.pid
cat: /run/postgrey.pid: No such file or directory

---------------------------------------------------------------------------------
After update (postgrey-1.34-8.2.mga4):

# /usr/sbin/postgrey --pidfile=/run/postgrey.pid --unix=/var/spool/postfix/extern/postgrey/socket --auto-whitelist-clients --daemonize

# LC_ALL=C cat /run/postgrey.pid
4289

I confirm that this update work and fix this issue.

Whiteboard: has_procedure MGA4-64-OK => has_procedure MGA4-64-OK MGA4-32-OK

Comment 3 claire robinson 2014-02-08 18:24:08 CET 
Advisory uploaded. Validating

Could sysadmin please push to 4 updates

Thanks!

Keywords: (none) => validated_update
Whiteboard: has_procedure MGA4-64-OK MGA4-32-OK => has_procedure advisory MGA4-64-OK MGA4-32-OK
CC: (none) => sysadmin-bugs

Comment 4 Thomas Backlund 2014-02-08 20:40:44 CET 
Update pushed:
http://advisories.mageia.org/MGAA-2014-0027.html

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.