(artist is Mathias Leth)

The borrow checker is a feature in the compiler. It only ensures that the source code doesn’t violate its rules at compile time, and if it does, stops the compilation and shows an error message. If the borrow checker is disabled, the code will be compiled even if borrowing rules are violated (as long as the source code is otherwise valid).

In short: removing the borrow checker turns Rust into C.

It’s that damn borrow checker again! Try the rust-- compiler, it disables that antifeature.

You. Are. Late. (mongolian throat singing intensifies)

Since your last post here, a new rule has been introduced. You must disclose AI usage in both the title and in the post body.

Hmmm… do I want to run unverified code in my kernel from the “Programming is too hard!” guys?

The first game I ever paid for, but did not directly purchase, was Garry’s Mod in 2011 or 2012 after UndeadPatch stopped working. I didn’t have a bank account, so I paid a classmate in cash to gift it to me. Considering that I first learned programming through Wiremod’s Expression 2 chip (basically a virtual ESP32), leading directly to my computer science studies and my current job as a sysadmin, I’d say it was $10 well spent.

My first purchase on Steam was “The Classic”, a sniper rifle in TF2, just to remove my account’s F2P trading restriction.

Then I got a whole bunch of games through Humble Bundle’s subscription. The first one was December of 2018, specifically for MGSV.

The first game I ever actually bought, actually on Steam, was Slay The Spire.

The collarbones, and the way the skin gets sucked in between.

In a vacuum, it was middling in all aspects and with some terrible technical and artistic issues, but it was okay. But it didn’t exist in a vacuum. It didn’t live up to the relative success of Inquisition, and was an unworthy successor of the Shepard trilogy.

Damn, I wonder why people are becoming averse to online accounts…

Inevitably there would be some incels who claim that speaking to women like normal human beings is an attempt by the matrix to emasculate men.

deleted by creator

Fuck me, if my choice is between five flavours of Javascript, I’d rather use PHP. I’m developing a QML application and having to work around that abomination that the clinically insane want to call “arrays” in Javascript makes me want to fucking die. There’s also a QList type implemented by QML. It doesn’t help. Array.isArray(qlist) returns false.

A year ago? People called it eight years ago with the Anthem disaster that Dragon Age 4 would be the studio’s last chance. BioWare was already dead, this is just the merciful last bullet.

Honestly, this is one where I can’t put all of the blame on EA. Bioware has been in a decline since My Face Is Tired, and a complete freefall since Anthem. Veilguard was their last chance and they blew it. The Bioware we’re nostallgic for (Baldur’s Gate, KOTOR, DA:O) hasn’t existed for years, and “Bioware magic” turned out to be a fart in the wind.

(edit) And let’s be real, Anthem wasn’t EA’s doing. Most of the game’s failures were Bioware’s fault, mostly incompetent management. https://kotaku.com/how-biowares-anthem-went-wrong-1833731964

Yes… but no. You probably saw a rendering error.

The private keys in question were only eight bits in length (decimal values 0 to 255). A proper key for the specific encryption should have been 384 bits, or about 116 decimal digits. If a string format function expects a 384 bit number, but only receives 8, it might fill out the missing places with zeroes.

Four… Fucking… Pixels?

The working hypothesis is that this was some sort of debug or test key that was never meant to be used in production, being used in production.

The encryption that SSL/TLS provides (that puts the “secure” in HTTPS) uses a public–private key pair and a specific mathematical function. Generating the key pair requires a cryptographically secure random number that is impossible or very difficult to guess, which must be kept secret at all times. If this random number is leaked or guessed by a malicious actor, the private key can be reconstructed and used to impersonate a website or break the encryption.

The security of the encryption comes from the fact that the function is easy to calculate one way, but difficult to calculate its inverse. To demonstrate: multiplying the prime numbers 88117 and 44543 is easy, but the inverse, factorizing the semiprime 3924995531, is extremely lengthy in comparison.

One of the factors that determine the security of the key is the size of the number, i.e. the number of digits. In this case, a proper key should’ve had a length of 384 bits (or 116 decimal digits). In reality, the keys that eMudhra used had eight bits, which can only represent 256 possible values, and can be easily guessed even by brute force. The specific private keys were the numbers 4, 56, 66, 115, 155, 156, 230, and 237.

Currently having a very fun day at work.

Fortunately our own certificates are unaffected, but it’s the autumn break and most of the staff are absent and incommunicado.