This is cool. Though the 133kb download size for the html isn't great.
Yeah but the image comes straight out of cache.
This JPEG is also a webpage
151–160 of 236 posts
Re: This JPEG is also a webpage
#152I abused this concept to compress demo code in PNG files, with great success. http://demoseen.com/blog/2011-08-31_Superpacking_JS_Demos.ht... This is, at present, the most efficient way to pack demos on the web; a few characters of uncompressed bootstrap code, then the rest is deflated.
My democrew (Ninjadev) has used this technique for multiple WebGL/Javascript productions over the last few years now.
You can see the final packed .PNG results here: Crankwork Steamfist https://stianj.com/crankwork-steamfist/, Everything is Fashion https://stianj.com/fashion/, and Inakuwa Oasis http://arkt.is/inakuwa-oasis/.
The tool used for creating both the demos and the packed .PNG is made by us and available on GitHub here https://github.com/ninjadev/nin/.
Re: This JPEG is also a webpage
#153Earlier quoted context omitted.
> To take this article as an example, according to the HTTP specification, the `Content-Type` header is supposed to have the final say in what media type is being served. Internet Explorer decided it would be better to use heuristics. I think the idea was that if a web host was misconfigured, rather than have the web developer fix their bug, it would try to guess its way out of the error. Which kinda worked. The prob…
> I think this is a fair bit different than being lenient on HTML interpretation. It's not. There are two areas where the leniency was a problem here. Firstly, the leniency in rendering one media type as a completely different media type because the browser heuristic thought it was being lenient. Secondly, the leniency in parsing HTML out of an image file – you can't do that with valid HTML. > Accepting malformed HTM…
> It's not. There are two areas where the leniency was a problem here. Firstly, the leniency in rendering one media type as a completely different media type because the browser heuristic thought it was being lenient. Secondly, the leniency in parsing HTML out of an image file – you can't do that with valid HTML.
I think you can argue the first is a problem. You have an example demonstrating as much. Arguing that the second is a problem is much harder. Lenient HTML acceptance been hugely advantageous to the adoption of the web. There may have been some issues from this, but it's valuable enough that the effort to "fix" it was abandoned and the W3C and WHATWG returned to codifying what leniency should look like.
> I've literally just given three specific examples of it causing security vulnerabilities.
Well, at least one example. Coercing a file served as an image to HTML isn't an issue of accepting malformed HTML, nor would I agree that the JS example is a problem with leniency.
> No, it was intentional. It was specifically Unicode characters that looked like less than and greater than signs, but weren't.
Okay, I reread your last comment. I initially thought you were saying that Netscape was treating '<' as '> Somebody noticed that href="java\nscript:…" wasn't being parsed as JavaScript, and it was causing some malformed pages to fail to work properly. Rather than let it fail, they tried to fix it by stripping out the whitespace, and caused a security vulnerability.
So the issue here is incompetent input sanitization. I don't think the browsers being lenient here is the issue.
> If these three examples aren't enough, take a look at OWASP's XSS filter evasion cheat sheet. There's plenty of examples in there of lenient parsing causing security problems: https://www.owasp.org/index.php/XSS_Filter_Evasion_Cheat_She...
A few of these are interesting in the context of browsers being lenient. e.g. This one requires lenience as well as poor filtering:
alert("XSS")">
Re: This JPEG is also a webpage
#154Some PoC||GTFO PDFs are also valid in other formats—"polyglots". They usually do PDF+HTML+ZIP, though sometimes they get (even more) creative. https://www.alchemistowl.org/pocorgtfo/
Keep in mind that combining most normal formats with most archive formats is trivial, because normal formats start at the beginning, and archive formats have a table of contents at the end. Concatenate both files and you're done.
Combining with PDF is also on the easy end of things, because the PDF header just has to be somewhere vaguely near the start.
Re: This JPEG is also a webpage
#155Interestingly, this page is intercepted by my router which then just sends me a redirect to one of its settings pages. Odd.
Well now, that is interesting… deep packet inspection? or just a truly insane bug? What router is it?
Here's the request and response from router: http://pastebin.com/e7rxLsGJ
The router itself is a BT Internet (UK) branded one. Not sure of the exact model but I'll try to find out...
Re: This JPEG is also a webpage
#156Earlier quoted context omitted.
which begs the question: where are all the "essential squirrel facts" that were promised?
Maybe a product manager realized it didn't make sense to provide "essential squirrel facts" to a page featuring the image of a chipmunk. :-)
The fact they didn't want us to know
Re: This JPEG is also a webpage
#157Earlier quoted context omitted.
Well now, that is interesting… deep packet inspection? or just a truly insane bug? What router is it?
Here's the request and response from router: http://pastebin.com/e7rxLsGJ The router itself is a BT Internet (UK) branded one. Not sure of the exact model but I'll try to find out...
Besides the model number, can you also tell us the firmware version?
Re: This JPEG is also a webpage
#158Earlier quoted context omitted.
Well now, that is interesting… deep packet inspection? or just a truly insane bug? What router is it?
Here's the request and response from router: http://pastebin.com/e7rxLsGJ The router itself is a BT Internet (UK) branded one. Not sure of the exact model but I'll try to find out...
I found some references online to something called "Smart Setup", which you can apparently turn of under Advanced Settings -> Home Network -> Smart Setup, but no idea what it actually does and why it intercepts random requests...
Re: This JPEG is also a webpage
#159No explanation of what's going on?
Re: This JPEG is also a webpage
#160I abused this concept to compress demo code in PNG files, with great success. http://demoseen.com/blog/2011-08-31_Superpacking_JS_Demos.ht... This is, at present, the most efficient way to pack demos on the web; a few characters of uncompressed bootstrap code, then the rest is deflated.
My democrew (Ninjadev) has used this technique for multiple WebGL/Javascript productions over the last few years now. You can see the final packed .PNG results here: Crankwork Steamfist https://stianj.com/crankwork-steamfist/ , Everything is Fashion https://stianj.com/fashion/ , and Inakuwa Oasis http://arkt.is/inakuwa-oasis/ . The tool used for creating both the demos and the packed .PNG is made by us and available…
Also a Ninjadever. Daeken's blog post was one of the inspirations that led us to implementing this in our toolchain. p01's Matraka [1] was another. The PNG trick is pretty common in the js scene nowadays, with packing tools such as JsExe [2] readily available.