From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] pngread: alloc chunk's length
Date: Tue, 13 Jul 2021 11:46:35 +0200 [thread overview]
Message-ID: <CAFSF3XPMyuTaMF3f5NU4ighwtk=xz+BmC0j1yGKeMc2HZ2zY4Q@mail.gmail.com> (raw)
In-Reply-To: <7c354c3b-899-26d-01e-e69abde0b322@SDF.ORG>
you seem to propose that if the png tells us to then we should
allocate 2GB per chunk, just bec. the spec allows it
even if the spec doesn't tell us a limit, we might want to have a limit.
On 7/13/21, adr via 9fans <9fans@9fans.net> wrote:
> On Tue, 13 Jul 2021, hiro wrote:
>> are you saying this is a purely synthetic error, it doesn't happen in
>> the wild bec. these sizes are normally more sane?
>
> No, no... you got it wrong. You have to follow the specification
> of the format, unless you want to have surprises like this one.
>
> The file you'll obtain with the example I gave you will be as
> correct as any other png file.
>
> Regards,
> adr.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4a714ed14c50767a-M76541e57925480ab6206e560
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-07-13 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 21:28 adr via 9fans
2021-07-10 21:49 ` adr via 9fans
2021-07-12 12:53 ` ori
2021-07-12 16:28 ` adr via 9fans
2021-07-12 16:01 ` ori
2021-07-12 17:01 ` adr via 9fans
2021-07-12 18:04 ` hiro
2021-07-12 23:31 ` adr via 9fans
2021-07-12 23:49 ` adr via 9fans
2021-07-13 8:16 ` hiro
2021-07-13 9:40 ` adr via 9fans
2021-07-13 9:46 ` hiro [this message]
2021-07-13 12:04 ` adr via 9fans
2021-07-13 12:11 ` adr via 9fans
2021-07-14 15:52 ` ori
2021-07-14 17:05 ` adr via 9fans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFSF3XPMyuTaMF3f5NU4ighwtk=xz+BmC0j1yGKeMc2HZ2zY4Q@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).