Re: [exim-dev] [Bug 2235] New: CVE-2018-6789

Hi, + int l = Ustrlen(code); + *ptr = result = store_get(1 + l/4 * 3 + l%4); An easier (or at least shorter) fix would have been uschar *result = store_get((Ustrlen(code)+1)*3/4 + 1); Anyway, I wonder why we need two base64 decoding functions. Sure, they serve different purposes, but the

[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 Jeremy Harris changed: What|Removed |Added Status|NEW |ASSIGNED

[exim-dev] [Bug 2242] New: exim_dbmbuild fails to open output files relative to cwd if no / in name

https://bugs.exim.org/show_bug.cgi?id=2242 Bug ID: 2242 Summary: exim_dbmbuild fails to open output files relative to cwd if no / in name Product: Exim Version: 4.90 Hardware: x86 OS: Windows

Re: [exim-dev] [Bug 2235] New: CVE-2018-6789

On 14/02/18 10:58, Jakob Hirsch via Exim-dev wrote: > Anyway, I wonder why we need two base64 decoding functions. Sure, they > serve different purposes, but the inner parts mostly do the same (apart > from error handling). Shouldn't we consolidate this? > Any objections? Consolidation is good,