1,327 karma · joined October 11, 2016
The window of acceptable speech is only going to narrow until everyone is toeing the party line in order to have access to food, shelter and banking. Until they introduce mandatory internet passports I will happily take the insane volatility of Bitcoin over kowtowing to stern ideologues advancing towards their goal of absolute conformity under the banner of tolerance. It's trans/feminism today and some arbitrary other thing tomorrow but the common denominator will always be exploiting our culture's unassailable values like tolerance, sexual freedom and racial guilt in order to justify any measure. Even if this appears to be a honest intervention for the betterment of society, it should be clear from the nature and trajectory of contemporary social justice activism that no amount of conformity will ever be satisfactory, and everyone will be crushed by this machine.
Nonsense. If you can code, you can start next week. You can set up a website and start selling things. If you make good music, people will come. If you solve a problem that saves people time or money, they will buy it.
Apart from people like you, most people don't care all that much about race.
I can't think of a single mainstream institution which has spoken out against the atrocities going on in Australia. The media are deliberately silent on the matter. Don't expect anyone but a few lonesome, throttled Twitter accounts to stand up for you when you're rounded up. The future is very dark and you're on your own from here on out.
Another fun one: With FD_CLR, FD_ISSET, FD_SET you can corrupt memory by merely passing a socket descriptor that is not 0..1024. Pass a negative integer for some undefined behavior as well (shift by negative value occurs here [1])
[1] https://github.com/lattera/glibc/blob/895ef79e04a953cac14938...
- Alcohol does not make people more aggressive to a large extent. In the vast majority of clubs/festivals almost everybody is inebriated but violence is fairly rare (in my experience). (I'm a non-drinker btw so I have no horse in this race).
- David Bowie's music is unremarkable.
- We should keep Linux unpopular because the more users it gets, the more malware/spyware/advertising/telemetry it will attract. It is fine where it is now in terms of its userbase.
Thiel isn't necessarily a good person in the sense that he'd readily share his sandwich with you if the two of you were lost in the desert together, but his unique perspectives on things and his willingness to share them are what makes him quite fascinating.
I'd argue writing an emulator is actually quite difficult. Due to the avalanche effect, slight errors in your emulation won't cause the emulated system to be slightly off, but it makes it completely unbootable, similar to how a bug in a (cryptographic) hash function can make the output entirely different from what it's intended to be. And unless there is an existing emulator you can compare against, debugging such bugs is very difficult and they can only be identified by painstakingly cross-referencing your entire implementation with the CPU specs. Years ago I wrote an Intel 8086 emulator and even the decoding of the instructions was non-trivial: the whole deal with MOD R/M encoding and prefix bytes can take considerable time to get perfectly right. Then there's the timer interrupt system, the IO layer, rendering the visuals by polling specific regions of memory depending on the mode, 80286+ protected mode etc.
I've been deeply fuzzing cryptographic libraries for a few years and found about 130 bugs [1]. The vast majority of these did not receive a CVE. Now some of these are merely theoretical, others will only manifest under particular circumstances like specific calling sequences, others were caught in the development phase before landing in stable releases, but a number of them are outright vulnerabilities. The usefulness of CVE incidence is questionable when it is so strongly influenced by the vendor's propensity for reporting these.
[1] https://github.com/guidovranken/cryptofuzz#bugs-found-by-cry...
What stands out to me:
- "Mercurial cores are extremely rare" but "we observe on the order of a few mercurial cores per several thousand machines". On average one core per 1000 machines is faulty? That's quite a high rate.
- Vendors surely must know about this? If not by testing then through experiencing the failures in their company servers.
- I've read the whole paper and I see no mention of them even reaching out to vendors about this issue. Their are strong incentives on both sides to solve or mitigate this issue so why aren't they working together?
The premise of bug bounties is that the reward amount is at the discretion of the program host and that the time incurred by developing a fix will influence the moment of payout, but refusing to pay and even communicate (for years!) for clearly eligible submissions is well beyond a reasonable interpretation of the conditions, and to consistently keep facilitating this abuse is simply fraudulent.