Axel Rau | 2 May 2011 14:58
Picon

Re: [Bug 1031] Implement database logging of completed remote delivery

Hi Phil,

is this patch on the road for 4.76 now?
Anything to do on my side?

Am 14.02.2011 um 19:16 schrieb Phil Pennock:

> On 2011-02-14 at 11:32 +0100, Axel Rau wrote:
>> Meanwhile, I ported this to 4.73 and now to 4.74 (patch just uploaded).
>> My code is running in production with a PostgreSQL DB since last October
>> w/o problems, is not hacky and well documented. (-;
>> At least one more person is interested in it.
>> 
>> What can I do to get this included in 4.75?
> 
> Will you settle for 4.76?  :)
> 
> The 4.74 release was a little too rushed, for more security fixes, and
> has a major new feature still finding old compiler bugs.  I'd like to
> get out a 4.75 which has bug-fixes and only those new features which are
> clearly correct by inspection.
> 
> It's probably best to think of 4.75 as the stabilisation release,
> post-security-lockdown.
> 
> Unless another maintainer decides to merge this for 4.75, I'll
> investigate more closely for a 4.76 merge.  It does look pretty clean,
> although I do wonder about what happens with DB connections
> happening from multiple users, depending on which user Exim was running
> as when it opened the connection?
(Continue reading)

Phil Pennock | 3 May 2011 00:06

Re: [Bug 1031] Implement database logging of completed remote delivery

On 2011-05-02 at 14:58 +0200, Axel Rau wrote:
> Hi Phil,
> 
> is this patch on the road for 4.76 now?
> Anything to do on my side?

It's on my list of things I want to pull in before 4.76.  There is no
timetable for 4.76, or guarantee that it won't be cut by someone else
before I pull it in.  Someone else can pull it in too!

I started a new job a month ago and things have been a little hectic.  I
should be back at home later this week and might (*might*) have time for
non-emergency patching of Exim this weekend.  Anything I've done
recently has been mailing-list commentary or patching of egregious bugs
which warranted fast fixes.

-Phil

Milan Kocian | 2 May 2011 13:26
Picon

exiqgrep trivial patch

helo,

this patch adds possibility to use alternative configuration in exim.

--- a/exiqgrep	2011-01-30 22:19:01.000000000 +0100
+++ b/exiqgrep	2011-05-02 12:50:44.000000000 +0200
 <at>  <at>  -44,7 +44,7  <at>  <at> 
   $base = 62;
 };

-getopts('hf:r:y:o:s:zxlibRc',\%opt);
+getopts('hf:r:y:o:s:C:zxlibRc',\%opt);
 if ($opt{h}) { &help; exit;}

 # Read message queue output into hash
 <at>  <at>  -79,11 +79,17  <at>  <at> 
 	-i		Message IDs only
 	-b		Brief Format
 	-R		Reverse order
+
+Exim options:
+	-C <file>	Path to alternative configuration
+
 EOF
 }

 sub collect() {
-	open(QUEUE,"$exim $eargs |") or die("Error openning pipe: $!\n");
+	my $cparam = '';
+	$cparam = "-C $opt{C}" if (defined($opt{C}));
(Continue reading)

Phil Pennock | 5 May 2011 03:46
Favicon
Gravatar

[Bug 1107] Git master does not build "conflicting types for 'log_write'"

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1107

Phil Pennock <pdp <at> exim.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pdp <at> exim.org

--- Comment #1 from Phil Pennock <pdp <at> exim.org>  2011-05-05 02:46:01 ---
Fixed, thanks.

--

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email

Git Commit | 5 May 2011 04:17
Favicon

[Bug 1107] Git master does not build "conflicting types for 'log_write'"

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1107

Git Commit <git <at> exim.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |git <at> exim.org

--- Comment #2 from Git Commit <git <at> exim.org>  2011-05-05 03:17:27 ---
Git commit:
http://git.exim.org/exim.git/commitdiff/ad2f0c19ffa5056fee65fdc36554e35ed1b86db8

commit ad2f0c19ffa5056fee65fdc36554e35ed1b86db8
Author:     Phil Pennock <pdp <at> exim.org>
AuthorDate: Wed May 4 21:41:58 2011 -0400
Commit:     Phil Pennock <pdp <at> exim.org>
CommitDate: Wed May 4 21:41:58 2011 -0400

    Fix compile of exim_monitor

    The "Compiler masochism compliance" patch changed the log_write()
    prototype to use "const char *" instead of "char *"; I don't have X11 on
    my main box, so neglected to handle exim_monitor's duplicate definition
    of log_write().

    Fixes bug 1107
---
(Continue reading)

Phil Pennock | 6 May 2011 13:23
Favicon
Gravatar

Exim 4.76 RC1 uploaded - SECURITY


I have uploaded Exim 4.76 RC1 to:
	ftp://ftp.exim.org/pub/exim/exim4/test/

I regret to inform you that 4.76 is a security-fix release, again.  In
this case, CVE-2011-1764: a format string attack in logging DKIM
information from an inbound mail may permit anyone who can send you
email to cause code to be executed as the Exim run-time user.  No
exploit is known to exist, but we do not believe that an experienced
attacker would find the exploit hard to construct.

ChangeLog can be found at:
  http://git.exim.org/exim.git/blob/c8d52a009aa7bc80a1380adec35085755d389ea7:/doc/doc-txt/ChangeLog

This RC is expected to be released as 4.76 before Monday.  If you are
unhappy with running an RC in production over the weekend, then this
patch should apply cleanly to 4.75:
  http://git.exim.org/exim.git/commitdiff_plain/337e3505b0e6cd4309db6bf6062b33fa56e06cf8

Untar the 4.75 source, then download the patch above with:
  curl -o 475format.patch http://git....
read/review and then apply with:
  patch -p2 < 475format.patch
and then build Exim as normal.

For the 4.76 RC, the files are signed with the PGP key 0x3903637F, which
has a uid "Phil Pennock <pdp <at> exim.org>".  Please use your own discretion
in assessing what trust paths you might have to this uid.  This email
should be signed with the same key, which should provide some
authentication for the above patching instructions and, because of git's
(Continue reading)

Lars Müller | 6 May 2011 22:25
Picon
Favicon
Gravatar

[Bug 1108] New: ldap_set_option() called with int as third arg instead of void

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1108
           Summary: ldap_set_option() called with int as third arg instead
                    of void
           Product: Exim
           Version: 4.75
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Lookups
        AssignedTo: nigel <at> exim.org
        ReportedBy: lars <at> samba.org
                CC: exim-dev <at> exim.org

While moving exim in the server:mail project of the openSUSE Build Service to
version 4.75 the build failed.

All other calls to ldap_set_option() make already use of this type cast.

--

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email

Lars Müller | 6 May 2011 22:27
Picon
Favicon
Gravatar

[Bug 1108] ldap_set_option() called with int as third arg instead of void

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1108

--- Comment #1 from Lars Müller <lars <at> samba.org>  2011-05-06 21:27:26 ---
Created an attachment (id=477)
 --> (http://bugs.exim.org/attachment.cgi?id=477)
ldap_set_option() third arg cast

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
--

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at
http://www.exim.org/ ##
Phil Pennock | 7 May 2011 00:16
Favicon
Gravatar

[Bug 1108] ldap_set_option() called with int as third arg instead of void

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1108

Phil Pennock <pdp <at> exim.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pdp <at> exim.org
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Phil Pennock <pdp <at> exim.org>  2011-05-06 23:16:45 ---
There are a few other calls which don't use this type-cast.  I suspect that the
failure is actually a promoted warning, fixed as PP/01 in the 4.76 release,
currently at RC1; it's a security critical fix, so your best bet is probably to
try 4.76_RC1 and see if that builds?

The actual fix in your patch is to use "&", which was missing from the patch
applied and not caught in review for 4.75, quickly fixed in 4.76.  The explicit
void cast just masks such issues.

The relevant commit for this is 109066729a54f6ba5c4e8bc174133da33242e930:

http://git.exim.org/exim.git/commitdiff/109066729a54f6ba5c4e8bc174133da33242e930

So, fixed as duplicate of an issue which didn't have a tracking bug (sorry).

--

-- 
(Continue reading)

Lars Müller | 7 May 2011 15:43
Picon
Favicon
Gravatar

[Bug 1108] ldap_set_option() called with int as third arg instead of void

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1108

--- Comment #3 from Lars Müller <lars <at> samba.org>  2011-05-07 14:43:34 ---
Thanks Phil for your update.  And no need to feel sorry.

I've pulled your commit from comment #2 and replaced the patch used for the
exim builds at http://download.opensuse.org/repositories/server:/mail/

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
--

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at
http://www.exim.org/ ##

Gmane