Re: [Development] qdds image format

2018-04-19 Thread Sean Harmer
On 17/04/2018 15:33, Иван Комиссаров wrote: At the point i wrote the plugin, my usecase was simple - to convert plain QImages to and from DDS icons (used in starcraft2, which uses quite a few formats DDS can handle). But yes, i forgot floating point textures. Compressed textures (DXTN/ATI2) are

Re: [Development] qdds image format

2018-04-17 Thread Thiago Macieira
On Tuesday, 17 April 2018 07:35:44 PDT Konstantin Tokarev wrote: > FWIW, hardware decoding of JPEG is usually supported by devices featuring > hardware video decoding support. But that's still decompressing it. You're just using the HW to do it faster. The only use-case I can easily think of for

Re: [Development] qdds image format

2018-04-17 Thread Konstantin Tokarev
17.04.2018, 17:33, "Иван Комиссаров" : > At the point i wrote the plugin, my usecase was simple - to convert plain > QImages to and from DDS icons (used in starcraft2, which uses quite a few > formats DDS can handle). > But yes, i forgot floating point textures. > Compressed textures (DXTN/ATI2

Re: [Development] qdds image format

2018-04-17 Thread Иван Комиссаров
At the point i wrote the plugin, my usecase was simple - to convert plain QImages to and from DDS icons (used in starcraft2, which uses quite a few formats DDS can handle). But yes, i forgot floating point textures. Compressed textures (DXTN/ATI2) are just compressed (a)rgb32, nobody uses compresse

Re: [Development] qdds image format

2018-04-17 Thread Jason H
> From: "Giuseppe D'Angelo" > On 17/04/18 13:21, Иван Комиссаров wrote: > > Ok, there's another problem with QImage - ARGB64 and friends... This can > > be solved adding QImage::pixel64() or something like that... or use > > QTexture with 64bit "pixel" > > And a bunch of packed formats not curr

Re: [Development] qdds image format

2018-04-17 Thread Giuseppe D'Angelo
On 17/04/18 13:21, Иван Комиссаров wrote: Ok, there's another problem with QImage - ARGB64 and friends... This can be solved adding QImage::pixel64() or something like that... or use QTexture with 64bit "pixel" And a bunch of packed formats not currently supported, and floating point channels

Re: [Development] qdds image format

2018-04-17 Thread Иван Комиссаров
Ok, there's another problem with QImage - ARGB64 and friends... This can be solved adding QImage::pixel64() or something like that... or use QTexture with 64bit "pixel" 2018-04-17 11:48 GMT+03:00 Иван Комиссаров : > > > 2018-04-17 11:02 GMT+03:00 Giuseppe D'Angelo : > >> On 17/04/18 08:09, Иван К

Re: [Development] qdds image format

2018-04-17 Thread Иван Комиссаров
2018-04-17 11:02 GMT+03:00 Giuseppe D'Angelo : > On 17/04/18 08:09, Иван Комиссаров wrote: > >> Looking at the email archives: it was fuzzed through AFL. I don't have >>> the test images still around, but in my experience a simple multi-image >>> file was enough to trigger a crash. (I used to see

Re: [Development] qdds image format

2018-04-17 Thread Giuseppe D'Angelo
On 17/04/18 08:09, Иван Комиссаров wrote: Looking at the email archives: it was fuzzed through AFL. I don't have the test images still around, but in my experience a simple multi-image file was enough to trigger a crash. (I used to see this in Creator, when accidentally opening a DDS in its bu

Re: [Development] qdds image format

2018-04-16 Thread Иван Комиссаров
> 16 апр. 2018 г., в 16:03, Giuseppe D'Angelo > написал(а): > > On 16/04/18 12:23, Иван Комиссаров wrote: >> So, how those issues are checked? Any tool or what? > > Looking at the email archives: it was fuzzed through AFL. I don't have the > test images still around, but in my experience a si

Re: [Development] qdds image format

2018-04-16 Thread Giuseppe D'Angelo
On 16/04/18 12:23, Иван Комиссаров wrote: So, how those issues are checked? Any tool or what? Looking at the email archives: it was fuzzed through AFL. I don't have the test images still around, but in my experience a simple multi-image file was enough to trigger a crash. (I used to see this

Re: [Development] qdds image format

2018-04-16 Thread Иван Комиссаров
So, how those issues are checked? Any tool or what? 2018-04-16 0:41 GMT+03:00 Thiago Macieira : > On Sunday, 15 April 2018 12:59:35 PDT Giuseppe D'Angelo wrote: > > Hello, > > > > Il 15/04/2018 18:14, Иван Комиссаров ha scritto: > > >> The usual amount of parsing a file without doing bounds check

Re: [Development] qdds image format

2018-04-15 Thread Thiago Macieira
On Sunday, 15 April 2018 12:59:35 PDT Giuseppe D'Angelo wrote: > Hello, > > Il 15/04/2018 18:14, Иван Комиссаров ha scritto: > >> The usual amount of parsing a file without doing bounds checks, so making > >> the user vulnerable to crashes / code execution / overflows and the > >> like.> > > Are

Re: [Development] qdds image format

2018-04-15 Thread Giuseppe D'Angelo
Hello, Il 15/04/2018 18:14, Иван Комиссаров ha scritto: The usual amount of parsing a file without doing bounds checks, so making the user vulnerable to crashes / code execution / overflows and the like. Are there any tickets on Jira related? All tickets i found are fixed and closed long ago

Re: [Development] qdds image format

2018-04-15 Thread Иван Комиссаров
> 15 апр. 2018 г., в 18:59, Giuseppe D'Angelo > написал(а): > > Il 15/04/2018 17:32, Иван Комиссаров ha scritto: >> Hello, what happened to the qdds image plugin? >> I found the note in the docs: "For security reasons, the Direct Draw Surface >> (DDS) handler is not built by default since Qt

Re: [Development] qdds image format

2018-04-15 Thread Giuseppe D'Angelo
Il 15/04/2018 17:32, Иван Комиссаров ha scritto: Hello, what happened to the qdds image plugin? I found the note in the docs: "For security reasons, the Direct Draw Surface (DDS) handler is not built by default since Qt 5.8" but could not find any open issues. Does anyone know what are those "

[Development] qdds image format

2018-04-15 Thread Иван Комиссаров
Hello, what happened to the qdds image plugin? I found the note in the docs: "For security reasons, the Direct Draw Surface (DDS) handler is not built by default since Qt 5.8" but could not find any open issues. Does anyone know what are those "security reasons"? What need to be done to return the