jcs.org
mutt stable branch with some hacks
automatic post-release commit for mutt-1.9.5
+96
-1
+91
ChangeLog
+91
ChangeLog
···
1
+
2018-04-13 20:39:35 -0700 Kevin McCarthy <kevin@8t8.us> (ceb0534d)
2
+
3
+
* Improve gss debug printing of status_string.
4
+
5
+
Commit f52ee2f7 ensured the debug strings were properly '\0'
6
+
terminated. However, it did not prevent the strncpy from reading past
7
+
the end of the status_string.value data; it simply capped it
8
+
afterwards. Improve the code so it only reads up to
9
+
status_string.length without overwriting the buffer.
10
+
11
+
M imap/auth_gss.c
12
+
13
+
2018-04-13 19:03:29 -0700 Kevin McCarthy <kevin@8t8.us> (f52ee2f7)
14
+
15
+
* Remove trailing null count from gss_buffer_desc.length field.
16
+
17
+
RFC 2744 section 3.2.2 clearly states that trailing NULL characters
18
+
are not to be included in the length field, and are not to be assumed
19
+
to be present in the value field.
20
+
21
+
Thanks to Greg Hudson, who recently debugged this same issue with
22
+
fetchmail, and kindly took the time to look at Mutt's code too.
23
+
24
+
M imap/auth_gss.c
25
+
26
+
2018-04-08 15:37:09 -0700 Kevin McCarthy <kevin@8t8.us> (a550d535)
27
+
28
+
* Rename _regex.h to _mutt_regex.h to avoid name collision on Macs.
29
+
30
+
On Macs, <regex.h> includes <_regex.h>. Because Mutt defines '-I .'
31
+
during compilation, our bundled version of _regex.h was being used
32
+
instead of the system one.
33
+
34
+
I have no idea how it managed to work before, but starting in Xcode
35
+
9.3, the differences in struct size and fields started to produce a
36
+
crash and other strange behavior.
37
+
38
+
The real issue is our use of '-I .' during compilation, which allows
39
+
our local headers to override system ones. An easier fix for now is
40
+
to rename the header.
41
+
42
+
Many thanks to Charles Diza, Christian Ebert, and Fabian Groffen for
43
+
their help trying things out and helping to debug the problem.
44
+
45
+
Also, a huge thanks to Steve Karmeinsky for allowing me to ssh in to
46
+
his Mac so I could track down the underlying issue.
47
+
48
+
M Makefile.am
49
+
R100 _regex.h _mutt_regex.h
50
+
M mutt_regex.h
51
+
M regex.c
52
+
53
+
2018-04-02 11:30:31 -0700 Kevin McCarthy <kevin@8t8.us> (4fe6cfeb)
54
+
55
+
* configure: check for tinfo matching ncurses
56
+
57
+
When we selected ncursesw, look for tinfow as well. Since ncurses-6.1
58
+
the binary compatibility between tinfo and tinfow disappeared, resulting
59
+
in crashes and other odd behaviour.
60
+
61
+
This change checks for tinfo or tinfow based on which ncurses we found
62
+
to continue with.
63
+
64
+
https://bugs.gentoo.org/651552
65
+
66
+
[Thanks to Fabian Groffen for the patch. I made a minor modification
67
+
to fall back to tinfo because pre-6.1 systems may not have a tinfow
68
+
but still need tinfo to compile.]
69
+
70
+
M configure.ac
71
+
72
+
2018-03-22 09:32:31 -0700 Kevin McCarthy <kevin@8t8.us> (eeba9a9b)
73
+
74
+
* Fix s/mime non-detached signature handling.
75
+
76
+
This fix is based on stbuehler's patch from
77
+
https://dev.gnupg.org/T2919.
78
+
79
+
Recent versions of gpgme seem to terminate the connection for a
80
+
protocol error. stbuehler's analysis is that this is actually a
81
+
gpgme bug, but recreating the context works around the problem.
82
+
83
+
M crypt-gpgme.c
84
+
85
+
2018-03-03 13:40:27 -0800 Kevin McCarthy <kevin@8t8.us> (9eeb406b)
86
+
87
+
* automatic post-release commit for mutt-1.9.4
88
+
89
+
M ChangeLog
90
+
M UPDATING
91
+
M VERSION
1
92
2018-02-28 15:20:59 -0800 Kevin McCarthy <kevin@8t8.us> (65068235)
2
93
3
94
* Add subjectrx section to the muttrc man page.
+4
UPDATING
+4
UPDATING