linux-kernel - Re: [Ksummit-discuss] [PATCH 0/9] Get rid of bitmap images

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <877f7vy684.fsf@intel.com>
Date:   Tue, 22 Nov 2016 15:49:47 +0200
From:   Jani Nikula <jani.nikula@...el.com>
To:     Mauro Carvalho Chehab <mchehab@...pensource.com>,
        Jonathan Corbet <corbet@....net>
Cc:     Markus Heiser <markus.heiser@...marIT.de>,
        ksummit-discuss@...ts.linuxfoundation.org,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sakari Ailus <sakari.ailus@...ux.intel.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: [Ksummit-discuss] [PATCH 0/9] Get rid of bitmap images

On Mon, 21 Nov 2016, Mauro Carvalho Chehab <mchehab@...pensource.com> wrote:
> Em Mon, 21 Nov 2016 10:44:44 -0700
> Jonathan Corbet <corbet@....net> escreveu:
>
>> On Sun, 20 Nov 2016 14:08:31 -0200
>> Mauro Carvalho Chehab <mchehab@...pensource.com> wrote:
>> > NOTE: some images use more than 998 columns, causing troubles
>> > with some MTA and MUA that could refuse them, because of an IETF
>> > RFC 2821 violation:  
>> 
>> Hard would it be to bash out a little tool that could break those long
>> lines?  It seems like the format should be able to support that?  I'm no
>> XML expert, but a quick experiment breaking the long lines in
>> fieldseq_bt.svg didn't create any problems; white space is white space.
>
> I'm not sure. The problem happens on strings like this one:
>
> x="103.58983 109.09226 113.67899 118.26572 122.85246 127.43919 132.47964 134.77301 140.27545 144.86218 150.81833 155.40506 160.44553 166.86365 188.62184 194.12427 198.711 203.29774 207.88448 212.47121 217.51166 219.80502 225.30746 229.8942 235.85034 240.43707 245.9395 252.35764 257.3981 262.43854 268.85669 375.69293 381.19534 385.78207 390.3688 394.95554 399.54227 404.58273 406.8761 412.37854 416.96527 422.92142 427.50815 433.01059 439.42871 444.46918 449.50961 455.92776 1.551828 7.0542617 11.640993 16.227724 20.814463 25.401194 30.441652 32.735016 38.237442 42.824177 48.780331 53.367065 58.869492 65.287621 70.328079 75.368538 81.786659"
>
> I've no idea if breaking lines inside strings on XML would cause
> troubles for SVG handling, and, if all SVG libraries would do the
> same thing.

It *should* be okay to just replace spaces within attributes with
newlines, and they should be normalized back to spaces by any compliant
xml parser.

You can use tidy or xmllint to clean up the xml before
committing. Unfortunately I couldn't make tidy actually wrap the long
attributes, but could be PEBKAC.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center