Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 521912 - postgrey crashes immediately
Summary: postgrey crashes immediately
Status: RESOLVED DUPLICATE of bug 518684
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL: https://forums.gentoo.org/viewtopic-t...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-01 20:55 UTC by Joe Kane
Modified: 2014-09-04 10:15 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Kane 2014-09-01 20:55:33 UTC
after a perl update, postgrey no longer starts, and crashes immediately.
syslog only shows that the process starts in background
running from command line exits immediately.
strace postgrey gives a line
write(2, "Insecure dependency in socket wh"..., 121Insecure dependency in socket while running with -T switch at /usr/lib64/perl5/5.18.2/x86_64-linux/IO/Socket.pm line 81.


Reproducible: Always

Steps to Reproduce:
1. update perl to 5.18
2. /etc/init.d/postgrey restart
3. rc-status | grep crash
Actual Results:  
shows postgrey crashed

Expected Results:  
shows postgrey started

https://github.com/schweikert/postgrey/pull/4/files

adjust /usr/sbin/postgrey from line 557

  if($opt{dbdir}) {
         $opt{dbdir} =~ /^(.*)$/; $opt{dbdir} = $1;
     }
+    # untaint what is given on --pidfile. It is not security sensitive since
+    # it is provided by the admin
+    if($opt{pidfile}) {
+        $opt{pidfile} =~ /^(.*)$/; $opt{pidfile} = $1;
+    }
+    # untaint what is given on --inet. It is not security sensitive since
+    # it is provided by the admin
+    if($opt{inet}) {
+        $opt{inet} =~ /^(.*)$/; $opt{inet} = $1;
+    }
 
     # determine proper "logsock" for Sys::Syslog
     my $syslog_logsock;
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2014-09-04 10:15:27 UTC

*** This bug has been marked as a duplicate of bug 518684 ***