Partisanship is a cancer. Inaction is a choice.

Singular they. Or whatever you like, I won’t take offence.
100% win rate in Highguard. Proud member of the Banned By Tesseract Club.

  • 2 Posts
  • 68 Comments
Joined 3 years ago
cake
Cake day: June 24th, 2023

help-circle







  • rtxn@lemmy.worldtoProgrammer Humor@programming.dev•Shoulda listened
    link
    fedilink
    arrow-up
    28
    arrow-down
    2
    ·
    edit-2
    23 days ago

    It’s still used because momentum is a powerful factor. That doesn’t make PHP better, but it can make it a more expedient choice.

    PHP is a preprocessor that grew too big for its britches. It’s a monolithic monster that runs only one thread per request in an interpreter. It works well enough if you need to manage the data of an internet forum, but it becomes increasingly unsuitable as the task’s complexity grows. If you need threading or background tasks, or if scalability is important, PHP is not it; just read any number of Nextcloud vs OpenCloud comparisons.




  • rtxn@lemmy.worldtoProgrammer Humor@programming.dev•Shoulda listened
    link
    fedilink
    arrow-up
    14
    arrow-down
    2
    ·
    23 days ago

    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.


  • 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.



  • rtxn@lemmy.worldtoSelfhosted@lemmy.world•PSA: eMudhra Intermediate CA Compromise
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    1
    ·
    edit-2
    23 days ago

    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.



  • No, we were taught about HTTP, the fundamentals of hypertext and how it gets rendered, how embedded code (Flash at the time; yes, I’m old) runs in the browser, and the concept of the digital footprint. The cybersecurity implications were obvious.

    Actually, I have to correct myself. Some of this was taught in the 7th or 8th year of primary school, around ages 12-14. I was fortunate to be born in a country, at the right time, where the public education system was still worth something. My heart bleeds when I hear of what goes on across the ocean.