--- You are receiving this mail because: ---
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1278
--- Comment #5 from Philip Hazel p...@hermes.cam.ac.uk 2012-10-28 11:45:13
---
Did you ever make any progress on this? Is there any reason to keep this bug
On Sat, 27 Oct 2012, Tom Bishop, Wenlin Institute wrote:
I don't know if anyone has had a chance yet to study the change I
proposed in an earlier message.
I have to confess that I have (almost) ignored this, because I was
leaving all the 32-bit stuff to other people, and I have no experience
On Sun, 28 Oct 2012, Christian Persch wrote:
I'm against a compile time switch like this;
(I knew I should have kept out of this discussion, but now that I
haven't...)
I too am against a compile-time switch.
that there is just one bit left in the 32-bit integer for the pcre
flags, so I'd
--- You are receiving this mail because: ---
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1308
--- Comment #1 from Philip Hazel p...@hermes.cam.ac.uk 2012-10-28 17:19:37
---
I don't understand this patch at all. According to my man pages, fileno is
On Oct 28, 2012, at 8:27 AM, Christian Persch c...@gnome.org wrote:
The standard also notes, There are important security issues
associated with encoding conversion, especially with the conversion
of malformed text. See also http://www.unicode.org/reports/tr36/.
There are no security
On Sun, 28 Oct 2012, Tom Bishop, Wenlin Institute wrote:
A naive PCRE user only wants to know whether a file begins with a
particular character sequence, for example, #!/bin/bash. Not caring
whether the file is valid UTF-32 and not having read the documentation
very carefully, this programmer
Hi,
I am still a little lost of this masking feature. I know why we need it in
compile. But why we need it in exec? I know if you read a character, which is
0x10, and read its UCD value (e.g matching to a unicode property), you get
a crash regardless of masking. But that is ok, since the
Hi;
Am Sun, 28 Oct 2012 20:16:38 +0100 (CET)
schrieb Zoltán Herczeg hzmes...@freemail.hu:
I am still a little lost of this masking feature. I know why we need
it in compile.
We *don't* need it in compile, actually :-) I specifically didn't
implement that, because a) it was too much work, and
The idea is this: the programme that's using the pcre32 API wants to
use it on some data it has. That data isn't only used for matching
however, ie it may also be displayed, etc, and the programme has
therefore stored some flags into the unused-by-UTF-32 high bits of the
Wow, wow... stop it right
Guten Tag Ze'ev Atlas,
am Sonntag, 28. Oktober 2012 um 21:35 schrieben Sie:
Wow, wow... stop it right there. Back in the seventies, when we
used such techniques, they were already considered IMPOLITE (or
shall we say, downright wrong).
I'm not involved in any of the UTF-32 bit work but I
On Oct 28, 2012, at 2:10 PM, Philip Hazel p...@hermes.cam.ac.uk wrote:
... Due to widespread misunderstanding of the API, many
programs using libcurl have made this error: setting
CURLOPT_SSL_VERIFYHOST to TRUE, will result in the SSL connection
being insecure against a man-in-the-middle
11 matches
Mail list logo
