sleep_deprived

joined 4 weeks ago
[–] [email protected] 2 points 9 hours ago

In simple terms, they just don't allow you to write code that would be unsafe in those ways. There are different ways of doing that, but it's difficult to explain to a layperson. For one example, though, we can talk about "out of bounds access".

Suppose you have a list of 10 numbers. In a memory unsafe language, you'd be able to tell the computer "set the 1 millionth number to be '50'". Simply put, this means you could modify data you're not supposed to be able to. In a safe language, the language might automatically check to make sure you're not trying to access something beyond the end of the list.

[–] [email protected] 3 points 10 hours ago (2 children)

No, the industry consensus is actually that open source tends to be more secure. The reason C++ is a problem is that it's possible, and very easy, to write code that has exploitable bugs. The largest and most relevant type of bug it enables is what's known as a memory safety bug. Elsewhere in this thread I linked this:

https://www.chromium.org/Home/chromium-security/memory-safety/

Which says 70% of exploits in chrome were due to memory safety issues. That page also links to this article, if you want to learn more about what "memory safety" means from a layperson's perspective:

https://alexgaynor.net/2019/aug/12/introduction-to-memory-unsafety-for-vps-of-engineering/

[–] [email protected] 3 points 10 hours ago

A person that does popular repacks of pirated games - essentially, she takes a pirated game, compresses it as best she can to optimize download size, adds an installer that also handles decompression, and ships it as a new torrent.

[–] [email protected] 1 points 1 day ago

Of course! Thanks for the discourse. Makes the world go 'round.

[–] [email protected] 7 points 1 day ago (2 children)

And as I said, if they manage to entirely switch, I won't have reservations.

As far as security in extant browsers and C++, see here: https://www.chromium.org/Home/chromium-security/memory-safety/

The Chromium project finds that around 70% of our serious security bugs are memory safety problems.

It's a serious issue.

[–] [email protected] 8 points 1 day ago (4 children)

Depends on a lot of factors. Due to uncontrollable factors like small untrackable debris, more satellites is always more dangerous, but that's still an extremely small problem. If all the Starlink-style companies cooperate properly and adopt high tech solutions for collision avoidance, it'll probably be fine - space is really, really big. Additionally, the extremely low orbits are a great mitigating factor for potential parts failures; even if a satellite outright dies, losing its telemetry and maneuvering capability, it'll be gone pretty quick.

Honestly, more than anything, I'd be concerned about the recent science showing that satellites burning up on reentry could be very significantly more damaging to our atmosphere and the ozone layer than previously thought.

[–] [email protected] 4 points 1 day ago (4 children)

Yeah, it was ok when the project started. The issue begins once it transitions from a toy to a potential competitor with Firefox.

[–] [email protected] 6 points 1 day ago (6 children)

Yeah, I know the history. And if they fully switch to Swift and manage decent performance, that would be acceptable, just strange. And it would also be fine to use whatever language if it were only a hobby project. I just reject the notion that C++ is an acceptable choice for new projects in security-critical positions.

[–] [email protected] 7 points 1 day ago

To be pedantic, AFAIK there's no evidence Pythagoras himself had anything to do with the censure of the discovery of irrational numbers. The common story has to do with his later followers, and could well be more fiction than fact in any case.

Talking about creepy numbers, the ones that always fucked with me are uncomputable numbers. That shit's wack, yo

[–] [email protected] 5 points 1 day ago (12 children)

The choice of C++ + Swift feels strange and off-putting to me. Swift, at least, is pretty safe as languages go, but does leave me scratching my head a bit. C++, though, frankly should have no place in a new browser project. For a piece of software whose whole purpose is to essentially download and run untrusted code, C++ is unacceptable.

It's realistically not gonna happen, but what I'd really like to see is Servo developed into a full browser.

[–] [email protected] 30 points 1 week ago

"yeah man it's right above [Xe] 4f^14^ 5d^10^ 6s^1^, you can't miss it"

view more: next ›