hexadecimated

5 ms·

1.
by hexadecimated 9y ago
Sorry but I don't quite understand your comment. What do the chemical underpinnings of evolution have to do with AGI?
2.
by hexadecimated 9y ago
> whether humans are the fittest carrier of information for our DNA We humans are defined by our DNA, so are we not by definition the fittest carrier for it?
3.
by hexadecimated 9y ago
It's freely available in the Windows 10 store as "WinDbg Preview". I recall reading somewhere that they will be rolling it into the Windows SDK once the preview is complete. WinDbg can work with managed code through extension
4.
by hexadecimated 9y ago
I think the more interesting question would be, how much data do they retain on you if you close your account?
5.
by hexadecimated 9y ago
> most of what you said is nothing more than a personal subjective judgement Indeed it was, I was offering my own considered opinion, not some absolute universal truth. No surprise such opinions don't go down favourably on HN thou
6.
by hexadecimated 9y ago
I don't see what other response he could have reasonably expected from Microsoft, given that his complaints were about the iOS Exchange connector, and actually had nothing to do with Exchange Server.
7.
by hexadecimated 9y ago
Before Ctrl+C and Ctrl+V to copy and paste, the usual method was Ctrl+Ins and Shift+Ins (and Shift+Del for cut), so this key did have a lot of use back in the day. These key combinations still work in most Windows software.
8.
by hexadecimated 9y ago
Such hideously wasteful extravagance, and how sad that these people who are already absurdly rich are still greedy for more.
9.
by hexadecimated 9y ago
The post-fork canary value could be paired with the stack pointer at which it became valid. If not valid, the process could walk a linked list of pre-fork canary and stack pointer pairs, to find the correct value to use. Would be interestin
10.
by hexadecimated 9y ago
Perhaps OpenBSD should consider randomizing the per-process stack canary value upon fork().
11.
by hexadecimated 9y ago
A sensible business decision by Cloudflare, and a fine moral stand to take. There is nothing positive to be gained by servicing such neo-Nazi websites, and Cloudflare is under no obligation to keep them as customers. Similarly, the Daily St
12.
by hexadecimated 9y ago
If it works inside a VM, an attacker could potentially cause a widespread denial of service on cloud computing platforms like Azure and AWS.
13.
by hexadecimated 9y ago
One exception may be if you could steal an authenticated pointer to a buffer that's about to have some generated machine code written to it (e.g. for JIT execution), and use that to write your own arbitrary code instead.
14.
by hexadecimated 9y ago
The exploits were released yesterday and the linked article says they have all been patched.
15.
by hexadecimated 9y ago
It was patched last month, so how is it a zero day when these exploits were released yesterday?
16.
by hexadecimated 9y ago
Room 641A wasn't a software vulnerability trying to hide in plain sight, it was a secret network tap.
17.
by hexadecimated 9y ago
That's just an insinuation of conspiracy with no evidence whatsoever behind it. The more believable alternative is that developers simply make mistakes now and then.
18.
by hexadecimated 9y ago
This idea that Microsoft is deliberately introducing bugs into its software so nation states can exploit them is so absurd, it really is tinfoil hat conspiracy theory ludicrousness.
19.
by hexadecimated 9y ago
Nice to see that these weren't zero day exploits after all, despite the claims being spread over Twitter. Looks like some amateur security researchers forgot to patch their test VMs.
20.
by hexadecimated 9y ago
Once a patch is released, it's generally quite straightforward to compare before and after, reverse engineering it to find the vulnerability. So the general advice is always to patch as soon as possible.
21.
by hexadecimated 9y ago
The provenance of these exploits is irrelevant to whether or not their products have been patched, so why would they?
22.
by hexadecimated 9y ago
How do you know it's the same bug?