Outside of bots and spam, third party Discord clients also often disable a lot of Electron's options that guard against XSS stuff escaping the sandbox, which is pretty dangerous. I wouldn't be surprised if Discord wanted to minimize the chance of some really big problem stemming from lots of users using these unsafe versions.
Neither really, it's demonstrating that it's kind of dumb to consider a paid advertisement "speech" for the purposes of "free speech", considering there's inherently a restriction there on how much "speech" you get, because you have to pay for the ability to "speak".
Yeah, the SEC did. After the contempt hearing, they had to renegotiate what constitutes "material" information as a part of their settlement, and that was essentially Musk/Tesla's wake-up call of "Oh, we only just BARELY got out of that mess". So as a result, they've actually been following what the original spirit of the settlement was meant to enforce.
Of course, we're still seeing issues where Musk is getting sued for threatening workers on Twitter for unionizing, but that's a slightly different issue than lying about production predictions.
* FCC Improves Access to 911 and Timely Assistance from First Responders - This is more-or-less explicitly requiring that phones in hotels, campuses, office buildings, etc be able to directly dial 911 without having to do any sort of prefix, that could be unknown or confusing in an emergency.
* FCC Bans Malicious Spoofing of Text Messages & Foreign Robocalls - This makes it easier for the FCC to pursue action against scammers who spoof caller ID (previously there were loopholes so that they couldn't take action if it was a text, or if the call originated from outside the US, or if it's a one-way VOIP call.
* FCC Authorizes $121 Million In Rural Broadband Funding In 16 States - Pretty self-explanatory
* FCC Reaches $550,000 Cramming Settlement with CenturyLink - This was in response to CenturyLink placing "unauthorized third-party charges and fees onto consumers' bills"
* Chairman Pai Recommends Approving T-Mobile/Sprint Merger - This one's more controversial, but you can make a strong case that allowing T-Mobile/Sprint (two relatively small providers) to merge would allow for them to compete at a higher level against Verizon and AT&T, increasing consumer choice and competition for most Americans. It also requires for them to sell off Boost Mobile to address competition concerns at the lower level, and to also invest a lot into pushing 5G technology.
So, in short, the FCC has been focusing on the following to improve the consumer experience with communications in the US:
It seems like the big distinction is going to be between "they didn't tell investors that they were a huge climate change contributor" and "they didn't tell investors how much money they'd lose out on from stricter environmental regulation".
* Hutchins (MalwareTech on social media) used to be a black hat, and developed/sold a banking trojan that would become Kronos.
* Since then, he's given up black hat activity and began reverse-engineering malware and providing educational material along the same lines.
* He came into the spotlight when he realized that the Wannacry ransomware was attempting to contact a particular web domain that was unregistered. He registered it to see what they were trying to send and why, and found out that it was a global killswitch, fully shutting down the initial strain of the malware.
* After Def Con 2017, he was arrested at the airport when attempting to leave the US. He was being charged with devleoping Kronos, and prosecutors were effectively adding new charges in retaliation every time he refused to plead guilty.
* He eventually caved and plead guilty, and today was sentenced to a year of supervised release, with no jail time (Though he likely won't be able to enter the US again). The judge strongly indicated that the lenient sentence was due to the fact that he stopped breaking the law of his own volition, and started using his skills to better the world.
* This article doesn't mention it, but the judge also suggested that he and his legal counsel seek a pardon, which could potentially allow him to enter the US again. They are planning to go forward with that path.
It was definitely for the banking trojan he created and sold, that would later become Kronos. That said, he also became sort of a public figure in the field due to stopping the initial strain of Wannacry, so news articles were popping up talking about how he was at least tangentially related to Wannacry, and was recently arrested for malware charges. People saw that and started drawing the false conclusion that he created Wannacry.
I mean that's a perfect choice as long as your marketing strategy isn't to hope that people pay extra for the feature thinking that it's FSD. The fact that Tesla still hasn't done something like this is proof that they're kind of relying on people to think that autopilot is something that automatically pilots the vehicle, which it doesn't.
Can someone tell me what I'm missing here? The author is saying that, on hover, it indicates a different URL than what the href actually goes to, which is a much more serious issue than just "HTML element text doesn't match the href", which is also what most people here in the comments are talking about. But then the author calls for a solution of just enforcing that the element text match the href, which wouldn't fix this issue! I'm inclined to think that something's not right in this article.
A sort of ELI5 on this for those that may not be familiar with any of this:
Ray tracing algorithms require checking to see if a ray will intersect with objects in a scene. This takes a LOT of time, and if you want this to be interactive ray tracing (e.g. in a game, where you need a frame drawn in a very short time), you have to find ways to reduce the number of objects you're comparing the ray against.
A lot of the time this includes culling algorithms, which essentially give you very quick ways to say that a number of objects have literally no way of being intersected by a ray, so you can ignore them. There's also things like bounding volume hierarchies (BVHs), which says things like, if a ray doesn't intersect with a given massive invisible cube that contains objects, then it can't possibly intersect things contained in that cube.
This is a bit different of a solution. If I'm understanding it right, this involves simplifying the representation of the objects themselves, so that something that was once a lot of triangles to be checked individually, can now be checked as one object. This means that a) you don't have to check for as many intersections, and b) it uses a lot less memory.
Oh, if that's the case, then the reporters were just wrong about how the software worked. If it only required the read access, then that would be a legitimate vulnerability.
The point is that, if an admin misconfigures the software, then the vulnerability is on them, and the software itself doesn't need to change (minus arguments of usability but that's a whole other can of worms).
I kinda went back and forth on this. The initial comments here made me think that this was basically the reporter saying "person with su can do su things".
Then I looked at the PostgreSQL statement, which said that the report claimed that users with a read-access role could do the su things, and they said that the claim was not true.
And then I looked at the actual report, which stated that you have to have the read-access role, and the execute-access role (or su).
So, what it seems like is that both parties didn't represent the actual situation well, but the root (ha) issue was that it was reported as "IF YOU HAVE READ ACCESS (and execute access) THEN YOU CAN EXECUTE ARBITRARY CODE!!11!!!"