Grom_PE

Websites like Imgur are able to detect whether the browser is requesting the image as a part of an <img> tag or a separate document by sniffing the Accept header.

So when a direct Imgur image link is opened in its own tab, Imgur can redirect to a webpage if it feels like it. In Firefox, by changing about:config value "image.http.accept" to

  */*

it's possible to avoid this behavior and it will load exactly what you asked for.

I never quite understood why do browsers let a webserver know the context you're loading the requested resource in, for privacy's sake.

I just use this 6 kb no-dependencies command line program:

http://code.kliu.org/misc/elevate/

Far Manager is my favorite TUI and is the primary reason I haven't switched over to Linux yet.

It does have a look similar to images drawn in Deluxe Paint, though without the characteristic dithering since there is no color limitations.

XMPP and Jappix Mini, for example.

Incorrect. It does, since 12.18:

http://www.opera.com/blogs/security/2016/02/opera-12-and-ope...

Ideally, like this:

    fs rep gs fs ; Note: extraneous prefix
    mov eax, [fs:ebx]

Some of disassemblers may put them as raw bytes (db 0x63, 0xf3, 0x65, 0x64).

> Note that code can jump past some of the prefixes. The C library on Linux does this to bypass prefixes

What's the use case for this?

I wouldn't split the prefix from the instruction and would rather use label+1 where it's absolutely required.

I believe MASM-style assemblers require "dword ptr" at all times and many disassemblers keep outputting that in unambiguous situations.

Your example won't assemble because size can't be guessed, but this will:

    mov dword [fs:ebp-10], 5

No. This is misleading:

    fs movs byte [edi], [esi]

This is a syntax error:

    movs byte [fs:edi], [esi]

And this is a valid override with sensible syntax:

    movs byte [edi], [fs:esi]

As AT&T syntax is still being used, at this point I'm willing to believe it's to purposely make x86 assembly hard and unpleasant to read and write. Perhaps so people will want to stay away from it, and in a way, to reduce the amount of code that is tied to the x86 platform. It spreads the thinking x86 assembly is terrible and ugly.

Intel syntax is much cleaner, in particular, Intel Ideal (as opposed to MASM), and specifically, FASM (flat assembler). FASM makes it as clean as possible and turns writing assembly into a joy.

Compare:

    movl %fs:-10(%ebp), %eax       ; AT&T
    mov eax, dword ptr fs:[ebp-10] ; MASM
    mov eax, [fs:ebp-10]           ; FASM

An algorithm that takes two downscaled images of different resolutions and rebuilds a higher resolution image.

They made it primarily to support the functionality called "Project Infinite":

https://news.ycombinator.com/item?id=11571813

I removed Dropbox from my Windows computer as soon as they started to include a minifilter driver with new versions.

https://www.dropbox.com/en/help/9249

I don't believe a program needs to integrate so deeply into the system just to sync the files.

document.write is still the only way to overwrite the current page completely, for use in userscripts:

https://github.com/grompe/Drawception-ANBT/blob/b9aeb21efdcc...

Yeah, it would definitely be more interesting if it allowed users to connect via XMPP/IRC/telnet like PSYCed server does, for example.

This setting disables both reading and writing third-party cookies. I just found a cookie testing webpage:

https://www.grc.com/cookies/forensics.htm

Sure. Those who haven't modernized their money-making technologies yet should stop relying on this security hole. There are alternatives.

Ah, third-party cookies, the bad idea to begin with, is causing problems again.

Hopefully this will force browser vendors to disable that misfeature by default.

MD5 is broken in a sense that you can craft two different files with the same hash, but it's still hard to create a file with specific MD5 hash.

So it's still good for identifying files that aren't specifically crafted to have a malicious counterpart.

How about tracker music? It is top-down instead of left-to-right. It is computer native and unambiguous.

MSVCRT.DLL is what programs compiled with Visual Studio 6.0 link to. So I think it's safe to expect MS retaining compatibility for the forseeable future.

Interesting. As I've reverse engineered Windows keyboard layout format, I went ahead and added Workman keyboard layout, along with additional symbols, for easy editing and installing:

https://github.com/grompe/kbdasm/commit/fd595046ffa996f5e309...

Some time ago I was surprised that my Google Search page was replaced by something else after I returned from some spammy page (opened in another tab).

As the browser I use, Opera 12, also treats all links manually opened in the new tab as if they had target="_blank", giving them opener access, I decided to remove the window.opener altogether by replacing the "opener" string with "opera" in the opera.dll. This way it gets overwritten by the normal window.opera variable and is essentially hidden. So far I haven't encountered a site legitimately relying on this behavior.

The most interesting points of flat assembler are elegant syntax, "Same source - same output" philosophy, and a very powerful macro system that consists of preprocessing and assembling stage; the fasm preprocessor has been shown to be turing-complete [0].

In 2008 I've played with it, creating macros that patch a binary file (and used it to extend a closed-source Windows program [1]), made PE format from scratch [2], a simple PE encryptor [3].

[0]: http://board.flatassembler.net/topic.php?t=6624

[1]: http://board.flatassembler.net/topic.php?t=8876

[2]: http://board.flatassembler.net/topic.php?t=8632

[3]: http://board.flatassembler.net/topic.php?t=8951