News for hackers. Stuff that matters.
Re:Do Not Use Go for 32bit Development by burgerbrain on Sunday April 08, 2012 @08:18PM (#3815334)
Isn't Go normally statically linked if cgo isn't being used? Would that mean that the DLL's in the virtual address space definitely shouldn't be there?
Re:Do Not Use Go for 32bit Development by 4ad on Monday April 09, 2012 @06:28AM (#3816398)
Statically linked in Linux, in Windows the Go runtime and packages are statically linked into the binary, but the binary itself is dynamically linked to kernel32.dll because issuing syscalls directly is not supported.

Why was kernel32.dll rebased when Go doesn't force the rebase is a very good question indeed. I suspect a 3rd party user mode hook, it doesn't even have to be malware, there are legit "security" and monitoring applications that use this technique.

Re:Do Not Use Go for 32bit Development by mbe on Monday April 09, 2012 @11:37AM (#3817418)
ASLR I would guess.
Re:Do Not Use Go for 32bit Development by 4ad on Monday April 09, 2012 @11:47AM (#3817469)
ASLR support needs to be stamped in the PE header. You can enable it globally, but the randomization space is smaller than it should matter for this.

It's definitely something to investigate though.