| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| signed-char.patch | fix FTBFS on architectures where char is unsigned Fix error base64.cxx:30:1: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing] by making Base64::sDecTable a signed char. |
gregor herrmann <gregoa@debian.org> | invalid | debian | 2021-04-13 | |
| g++-11.patch | Fix build failure with GCC-11 The failure: . mmfile.cxx: In member function ‘bool mimetic::MMFile::map()’: mmfile.cxx:60:14: error: ordered comparison of pointer with integer zero (‘char*’ and ‘int’) 60 | if(m_beg > 0) | ~~~~~~^~~ . https://gcc.gnu.org/gcc-11/porting_to.html says: . GCC 11 now issues a diagnostic for ordered comparisons of pointers against constant integers. Commonly this is an ordered comparison against NULL or 0. These should be equality comparisons, not ordered comparisons. |
no | debian | upstream | 2021-04-13 | |
| 0001-Mimetic-can-t-parses-address-if-there-are-character-.patch | [PATCH] Mimetic can't parses address if there are '\"' character in quoted-pair. ex) To: "\"abc, def\"" <abc@mail.com>, lmn <lmn@mail.com> |
suhwan park <swanee.park@samsung.com> | no | 2020-12-07 | ||
| 0002-Modify-wrong-memory-reference.patch | [PATCH] Modify wrong memory reference - If input is a string of only spaces, index becomes -1 during removes trailing spaces operation, referencing the wrong memory. - If the referenced memory value is a space, out_of_range occurs because -1 is entered in the erase function pos parameter. - Modify to return immediately if the input value is empty after the removes leading spaces operation. |
"shksh.kim" <shksh.kim@samsung.com> | no | 2021-03-31 | ||
| 0003-Fix-possible-out-of-bound-when-removing-new-line-cha.patch | [PATCH] Fix possible out of bound when removing new line characters. | Oliver Mihatsch <oliver.mihatsch@virtual-solution.com> | no | 2020-10-12 | ||
| 0004-Disable-default-constructor-for-MimeEntity.patch | [PATCH] Disable default constructor for MimeEntity. | Oliver Mihatsch <oliver.mihatsch@virtual-solution.com> | no | 2020-10-13 | ||
| 0005-Fix-warnings.patch | [PATCH 05/17] Fix -Werror=char-subscripts | Luke Mewburn <Luke@Mewburn.net> | no | 2023-04-07 | ||
| 0006-reimplement-find_bm-using-std-search.patch | [PATCH] reimplement find_bm() using std::search Use std::search() to implement find_bm() instead of using a local implementation of Boyer-Moore. Avoids integer overflow reported in issue #31 and PR #31. Should fix build problem in issue #7. std::search is also faster for the test program in issue #31 on a system with an Intel Xeon E-2224 CPU: - gcc 8.5, find_bm(): 3.16s - g++ 8.5, std::search: 2.40s - g++ 13, std::search: 2.16s Experiments using the C++17 std::boyer_moore_searcher or std::boyer_moore_horspool_searcher were also slower than std::search in this experiment. |
Luke Mewburn <Luke@Mewburn.net> | no | 2023-12-29 | ||
| 0007-fix-possible-out-of-bounds-read-in-Base64-decoder-wh.patch | [PATCH] - fix possible out of bounds read in Base64 decoder when the input contains a '|' character - added unit test to verify the correct behaviour |
Oliver Mihatsch <oliver.mihatsch@virtual-solution.com> | no | 2024-01-22 |