I don't think the author is presenting these ideas based on "any negative depiction of poor people is bad". It's more as a pointer on these common tropes that exist in storytelling, and some of the implied unrealistic assumptions that underly them.
860 karma · joined February 13, 2018
I don't think the author is presenting these ideas based on "any negative depiction of poor people is bad". It's more as a pointer on these common tropes that exist in storytelling, and some of the implied unrealistic assumptions that underly them.
Similarly, your comment didn't specify anything about what this political viewpoint might be, nor any reasons why you think this article is based on such a viewpoint.
But then it's lacked credibility from the start. Nobel only funded it to help rebrand his anticipated legacy, to offset being remembered as "le marchand de la mort".
This checks out - pretty much everything being posted by Trump fans in this thread is a rewording of the PR spin we see Twitter bots spamming everywhere.
As you note, it is often a team effort, and so the whole team should be rewarded with the credit for the invention. Rather than basically ignoring those whose design and/or engineering expertise were essential to its completion and delivery.
Downplaying the essential role of an experienced and knowledgeable engineer as merely being a "lackey" is the real disservice.
So the engineer did all the actual hard work here in coming up with a working prototype, but the wealthy funder takes almost all of the credit, and puts the patent solely in their name.
A much fairer framing would be that the two of them were co-inventors.
Seems rather suspicious to see so many commenters enthusiastically salivating over an advert for a very expensive radio.
And also for said advert to hit the #1 spot on this site, despite not fitting into the usual categories for a compelling post.
Please could you explain how ASLR makes your programs impossible to debug?
I'm surprised to hear this, as I work on such executables in my debugger every day, with no problems whatsoever caused by them having ASLR enabled.
> On the other hand, stuff like ASAN is great.
It is, but it's not intended as an exploit mitigation. You typically wouldn't apply it to your binaries running in production, due to the performance hit. Its purpose is to help detect memory safety bugs during development and testing.
> a society in which one is treated badly when one doesn't strive to keep up with the Joneses
> the never-ending hamster wheel situation
> perhaps humanity wouldn't be so rapacious of the earth
Whatever cognitive path you're on that's led you to conclude this, I advise you to swiftly veer away from it.
Blaming all the women isn't going to help with anything. People will just think, oh there's that weird sexist guy ranting on again. That's not going to get you anywhere useful.
I wonder how this comment section would look if it was revealed that people from a low income background had hacked the admissions system to gain entry. I expect the tone would be much more critical, calling for prosecutions and sanctions, and lamenting the sheer unfairness of it. I'm pretty sure it would be in stark contrast to all the bribery apologism we can see in these threads.
I've found zssh can be quite handy for that, it layers an extra pty over the SSH connection, for file transfer. By default it uses the ZMODEM protocol via rz/sz, but any pair of programs can be plugged in instead - useful if the connection isn't 8-bit clean.
But in WSL2 the whole thing runs in a Hyper-V VM, with a customised Linux kernel (available via http://linux.microsoft.com) to help with interoperability between WSL and Windows.
I think it's not too surprising, this sort of post always seems to bring HN's resident landlords out to argue in favour of whatever happens to benefit them financially, and gives them more control over their tenants' lives.
It's a bit like how any topic here relating to social justice attracts hordes of far-righteous types peppering the comments with comically bad takes, before flagging the submission off the front page.
It's just one of the very few risks a person of wealth might have to accept, should they decide to use their elevated position in society to inflict landlordism upon people.
Obviously not the best solution for the landlords, but, really, so what? Removing a class of parasites from the housing system would be a feature, not a bug.
> The oppressors are not always landlords - they are [...] other tenants who sit on their rent controlled housing until they die.
Why shouldn't low income earners pay lower rent? From a humanitarian perspective, it doesn't make sense to have a landlord greedily siphoning off the vast majority of a person's income, just so that person can have fulfilled the basic human right of not being homeless. It's parasitic.
Configuration was easy, I just ended up writing a simple shell script for the deploy challenge hook, to copy the certificates and reload configurations on nginx etc.
The two times I chose to intervene were straightforward too. The first was because of the ACME protocol upgrade, for which I just needed to drop in a newer copy of dehydrated, and rename references to its old name. The second was because I needed to configure the ACME DNS challenge to get a wildcard domain, and that just involved modifying the deploy challenge hook to temporarily run a custom DNS server that responded to the challenge.
I did take a look at certbot, or whatever it was called back then, and decided against it quite quickly due to the perceived complexity. Also I seem to recall it didn't support nginx properly.
After reading this user review, I'm quite glad I did that. Though I do wonder why the author persisted in using that client despite all the problems they were having with it, given the choices available in the wider Let's Encrypt ecosystem.
Sounds like a great way to get scammed by charlatans, and potentially interfere with the treatment you're receiving from medical professionals.
If it's nothing to do with software or hardware security, then it's not hacking.
And yes, this site is itself woefully misnamed.
And their fantastically detailed writeup of a PoC they wrote for that vulnerability: https://doar-e.github.io/blog/2019/06/17/a-journey-into-ionm...
This exploit is different in that they use the arbitrary read/write primitive gained by CVE-2019-9810 to flip a couple of bits and patch out a few instructions with the effect of removing the security boundary between a normal web page and XPCOM. The interesting difference in this exploitation approach is there's no need for ROP chains and shellcode, as you have all the XPCOM components available to use.
Once they're in that privileged context in the content process, they escape its sandbox by exploiting CVE-2019-11708. This works by sending an particular IPC message to the parent process, that causes a web page of the exploiter's choice to load in that process. In this case, the choice is to exploit CVE-2019-9810 again, then use XPCOM components to drop an executable to disk and run it.
Awesome work, and a real pleasure to read, it's satisfying to see such well-commented and clear exploit code.