On 08/21/2018 10:55 PM, Xi Ruoyao wrote:
On 2018-08-21 17:00 +0100, Ken Moffat wrote:
libX11-1.6.6 :
https://lists.x.org/archives/xorg-announce/2018-August/002915.html
CVE-2018-14596..600
I think x86 treats char as unsigned, in which case 14600 would not
apply.
No.
$ cat test.c
#include
On 2018-08-21 17:00 +0100, Ken Moffat wrote:
> libX11-1.6.6 :
>
> https://lists.x.org/archives/xorg-announce/2018-August/002915.html
>
> CVE-2018-14596..600
>
> I think x86 treats char as unsigned, in which case 14600 would not
> apply.
No.
> $ cat test.c
> #include
>
> int main()
> {
>
On Tue, Aug 21, 2018 at 11:15 AM Ken Moffat wrote:
> libX11-1.6.6 :
>
> https://lists.x.org/archives/xorg-announce/2018-August/002915.html
>
> CVE-2018-14596..600
>
> I think x86 treats char as unsigned, in which case 14600 would not
> apply.
>
> But 14598 can apparently cause a segfault.
>
> ĸen
libX11-1.6.6 :
https://lists.x.org/archives/xorg-announce/2018-August/002915.html
CVE-2018-14596..600
I think x86 treats char as unsigned, in which case 14600 would not
apply.
But 14598 can apparently cause a segfault.
ĸen
--
Entropy not found, thump keyboard to continue
--
http: