Re: [pcre-dev] [Bug 1705] heap-buffer-overflow in match src/pcre2_match.c:3321:20

On Thu, 5 Nov 2015, ad...@bugs.exim.org wrote: > It's a bit sad -- there's so much code using PCRE1 and UTF and can't be ported > just yet to PCRE2. How is the problem of \C solved in PCRE2 anyhow? PCRE2 has an option PCRE2_NEVER_BACKSLASH_C, which locks out the use of \C. It also has

[pcre-dev] [Bug 1705] heap-buffer-overflow in match src/pcre2_match.c:3321:20

https://bugs.exim.org/show_bug.cgi?id=1705 --- Comment #8 from Philip Hazel --- PCRE2 has an option PCRE2_NEVER_BACKSLASH_C, which locks out the use of \C. It also has --enable-never-backslash-C, which forces this option on all patterns. I know there's a lot of code

[pcre-dev] [Bug 1705] heap-buffer-overflow in match src/pcre2_match.c:3321:20

https://bugs.exim.org/show_bug.cgi?id=1705 --- Comment #7 from Giuseppe D'Angelo --- It's a bit sad -- there's so much code using PCRE1 and UTF and can't be ported just yet to PCRE2. How is the problem of \C solved in PCRE2 anyhow? -- You are receiving this mail because:

[pcre-dev] [Bug 1705] heap-buffer-overflow in match src/pcre2_match.c:3321:20

https://bugs.exim.org/show_bug.cgi?id=1705 --- Comment #6 from Philip Hazel --- I could add "has \C" to the info, but only in PCRE2. I don't want to do anything to PCRE1 other than mend bugs. Using \C in a UTF-8 match can cause crashes (as documented) so even doing what

[pcre-dev] [Bug 1705] heap-buffer-overflow in match src/pcre2_match.c:3321:20

https://bugs.exim.org/show_bug.cgi?id=1705 --- Comment #5 from Giuseppe D'Angelo --- Isn't there a way either to just know (via full_info) if there's a \C in the pattern? Could it be possible to add it, if not? (My understanding is that by NOT knowing it, it means that in

[pcre-dev] [Bug 1705] heap-buffer-overflow in match src/pcre2_match.c:3321:20

https://bugs.exim.org/show_bug.cgi?id=1705 --- Comment #3 from Kostya Serebryany --- (In reply to Giuseppe D'Angelo from comment #2) > However there's no way to exclude \C from PCRE 1, isn't it? I hope Philip can comment. -- You are receiving this mail because: You are on the

[pcre-dev] [Bug 1705] heap-buffer-overflow in match src/pcre2_match.c:3321:20

https://bugs.exim.org/show_bug.cgi?id=1705 Giuseppe D'Angelo changed: What|Removed |Added CC||dange...@gmail.com ---