This JPEG is also a webpage • Hacker News Board

Re: This JPEG is also a webpage

#231

Post by mrb » Thu, Aug 11, 2016, 3:50 PM UTC

ftvbffg wrote: post #218

mrb wrote: post #52

Earlier quoted context omitted.

1. Most Gmail users can receive money by email ( https://support.google.com/mail/answer/3141103 and coredump.cx MX records point to Gmail) 2. Ask him his Bitcoin address 3. Paypal to this address :)

You don't need to ask him for Bitcoin address. Just send him private key of a bitcoin wallet. Or this https://www.bctip.org/en/

You are perfectly right. As a matter of fact I have done this in the past—written a brainwallet passphrase on a birthday card :)

Re: This JPEG is also a webpage

#232

Post by slice-beans » Thu, Aug 11, 2016, 4:25 PM UTC

Jaruzel wrote: post #219

slice-beans wrote: post #212

Earlier quoted context omitted.

I visited some other black listed sites .> and discovered the pattern, then dug around in the router settings to see what had changed. Disabling parental controls sorted it and I can now see the squirrel/chipmunk/unidentified rodent. Lesson learned: just use a VPN.

> I visited some other black listed sites .> Is that an ASCII representation of what I think it is? (a well known .cx site)

It was shifty eyes. But good imagination skills +1

Re: This JPEG is also a webpage

#233

Post by dwaltrip » Thu, Aug 11, 2016, 7:58 PM UTC

danbruc wrote: post #36

rimantas wrote: post #30

Earlier quoted context omitted.

Or one of the best. Switch wen browsers to strict processong and you will hardly find working web page.

Which are the faults of the authors. No one expects malformed source code to compile, a video with corrupted headers to play properly or a binary containing invalid instructions not to crash. This decision allowed people to get away with broken web pages instead of forcing them to fix their mistakes.

The web would not have been as successful if it wasn't for this leniency. Full correctness is only worthwhile if both attaining it does not excessively harm other goals and the cost of not attaining it is severe enough.

The cost of a malformatted HTML document rendering despite the errors is not that severe compared to the benefits it provides, as we have seen.

Re: This JPEG is also a webpage

#234

Post by TazeTSchnitzel » Sat, Aug 13, 2016, 7:19 PM UTC

286c8cb04bda wrote: post #208

TazeTSchnitzel wrote: post #148

Earlier quoted context omitted.

I think it may only work if you omit a Content-Type header. Checking Firefox's Network tab, it looks like the server isn't serving one for that page.

It's sending the "wrong" one -- $ curl -I http://lcamtuf.coredump.cx/squirrel/ HTTP/1.1 200 OK Date: Thu, 11 Aug 2016 05:18:00 GMT Server: Apache Last-Modified: Mon, 19 Sep 2011 23:31:49 GMT Accept-Ranges: bytes Content-Length: 135938 Content-Type: text/html

Oh. Huh. My bad.

I guess browsers only forbid ignoring Content-Type for stuff like JS, then. For JPEG it's probably not a security concern.

Re: This JPEG is also a webpage

#235

Post by govindpatel » Wed, Aug 17, 2016, 2:14 PM UTC

well I just thought that it is some bug in html img tag. But still nice finding

Re: This JPEG is also a webpage

#236

Post by michaelmior » Tue, Aug 23, 2016, 4:27 PM UTC

instakill wrote: post #211

michaelmior wrote: post #106

Earlier quoted context omitted.

This is why it's important to correctly set the Content-Type header when serving files. Also why it's a good idea to have user-uploaded content served from a separate domain.

Please elaborate on the part about UCG from a separate domain. Why is this?

Sorry, didn't see this comment earlier. GitHub's blog post on why they did this gives some good insight.

https://github.com/blog/1452-new-github-pages-domain-github-...