Live data from Hacker News

Show HN: My first WebGL demo, the first self-extracting PNG ever?

demoseen.com

51–56 of 56 posts

Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?

#51

So, it the header makes it look like a PNG: magister.html: PNG image data, 1242 x 1, 8-bit grayscale, non-interlaced If you look at this in an image viewer, it's as advertised: a long black bar. So what this is is some garbage data with a PNG header, a token PNG image, and some HTML that bootstraps a javascript program whose main body looks like binary garbage. But it's not a self-extracting PNG, it's a very strange…

looks like it was designed as a firewall bypass

Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?

#53
post #52

I can't get this to work; low end laptop with low end gpu. But is it anything like what Rsnake posted on ha.ckers.org? Link: http://ha.ckers.org/blog/20070623/hiding-js-in-valid-images/ Example: https://github.com/christopherwoodall/ImgJs

The bootstrap code (which unpacks the second stage, compressed in the PNG image data) does indeed work this way. The key difference is that in addition to the code at the top level of the image, there's the second stage inside.

Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?

#54
post #49
post #41

Earlier quoted context omitted.

Can you post OS and browser versions along with the hardware revision? That sounds bad.

weren't you recently searching for exploitable webgl driver bugs?

Indeed I am. In the development of this demo (and the framework which built it), I've found more bugs than while actually attempting to attack WebGL; I don't know whether to be happy or sad about this.

Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?

#55
post #41
post #37

(Repeated) kernel panic on Macbook Air/Chrome I'm afraid.

Can you post OS and browser versions along with the hardware revision? That sounds bad.

Sorry for the late reply. Here are my details:

Mac OS X 10.6.8 all updated / Google Chrome 12.0.742.122 / MacBookAir3,2 / 2.13 GHz / 4GB RAM

Would be interesting to know if you have, indeed, found an exploitable driver bugs.

Post reply on HN