[exim-dev] [Bug 2242] exim_dbmbuild fails to open output fil…

Top Page
Delete this message
Reply to this message
Author: admin
Date:  
To: exim-dev
Subject: [exim-dev] [Bug 2242] exim_dbmbuild fails to open output files relative to cwd if no / in name
https://bugs.exim.org/show_bug.cgi?id=2242

Git Commit <git@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |git@???


--- Comment #2 from Git Commit <git@???> ---
Git commit:
https://git.exim.org/exim.git/commitdiff/15ae19f96fb9e6c7262fd4f69049e97e9403f4c8

commit 15ae19f96fb9e6c7262fd4f69049e97e9403f4c8
Author:     Jeremy Harris <jgh146exb@???>
AuthorDate: Thu Feb 22 11:26:34 2018 +0000
Commit:     Jeremy Harris <jgh146exb@???>
CommitDate: Thu Feb 22 11:31:27 2018 +0000


    Fix exim_dbmbuild to permit directoryless filenames.  Bug 2242


    Broken-by: 0a6c178c6c
---
 doc/doc-txt/ChangeLog   | 2 ++
 src/src/exim_dbmbuild.c | 2 ++
 2 files changed, 4 insertions(+)


diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 3fd3f38..d672ee7 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -118,6 +118,8 @@ JH/23 Fix memory leak during multi-message connections
using STARTTLS under
       OpenSSL.  Certificate information is loaded for every new TLS startup,
       and the resources needed to be freed.


+JH/24 Bug 2242: Fix exim_dbmbuild to permit directoryless filenames.
+

Exim version 4.90
-----------------
diff --git a/src/src/exim_dbmbuild.c b/src/src/exim_dbmbuild.c
index c95e168..afd5095 100644
--- a/src/src/exim_dbmbuild.c
+++ b/src/src/exim_dbmbuild.c
@@ -210,6 +210,8 @@ Ustrcat(temp_dbmname, ".dbmbuild_temp");
Ustrcpy(dirname, temp_dbmname);
if ((bptr = Ustrrchr(dirname, '/')))
*bptr = '\0';
+else
+ Ustrcpy(dirname, ".");

/* It is apparently necessary to open with O_RDWR for this to work
with gdbm-1.7.3, though no reading is actually going to be done. */

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