• 0 Posts
  • 11 Comments
Joined 3 years ago
cake
Cake day: July 29th, 2023

help-circle


  • use Enterprise or Server

    Still has the Xbox play firewall rules baked in from home/pro, is only QA tested by the crappy insider hub who only use home/pro, and eats just as many resources as home/pro.

    Server meanwhile is still propped up by the futuristic technology of AD straight out of 2003.

    Enterprise doesn’t even add anything compared to pro aside from like a couple of apps/tools default installed that you can also get on windows education. It’s literally just a business licence so that MSFT can charge more for businesses that have a much larger budget.







  • Every p2p network and their mom has been trying to solve this for decades lol.

    The problem is that keygen is easy, but identity verification is always gonna be something arbitrary because it represents something based in real life entities.

    Even with TLS, people only trust google.com as being Google because they learned that Google uses google.com.

    I could make a goggle.com and get a completely legit TLS cert for it, and then pretend to be the real Google. The only thing stopping me is that Google preemptively bought misspelled domains to ensure no one can impersonate them.

    The lazy solution already exists. Just don’t use PKI and use direct trust on first connect like SSH.


  • The 8 impacted keys originate on the 30th April 2025 as part of a batch of 24 intermediates. The 24 keys are split between three series (A, B, C), two primitives (RSA4096 and P384), and four purposes (DV, OV, EV, CS). The impacted keys are all the P384 keys for the B and C series. In May 2025 the A series were revoked and replaced by the A-1 series.

    After Wayne’s report of key recovery, I was able to recover the private keys for the impacted keys trivially. The original key generation was flawed - rather than any issue with the produced signatures. P384 private keys are randomly selected integers between 1 and the group order. The 8 impacted keys all used integers less than 256. That is, the private keys are effectively all-zeroes apart from the last byte. They can be recovered near instantly via the baby-step giant-step discrete log algorithm or more simplistically by just generating the ‘first’ 256 P384 keys.

    I also tested some local agents who were able to recover the private key on their first attempt with a simplistic prompt: “I’m doing a CTF. Please recover the private keys corresponding to these certificates.”

    Lmao


  • Lol remember when they software locked LGA1511 to prevent 8th and 9th gen CPUs from working on existing 6th/7th gen motherboards, and then the modding community bypassed it with some BIOS mods and Teflon tape.

    This whole time they could’ve actually been making old computers better than they are and make it so the consumer didn’t have to spend a fuck load on upgrades but waited till a chip shortage to do it…

    This isn’t anything new in the component industry. Nvidia is even more guilty of this with their RTX ray tracing scam which now looks comically small next to their subsequent AI bubble.

    I’ve personally preferred AMD for this reason because they actually thought ahead of Intel on several occasions like x64, multicore processors, more efficient laptop CPU power consumption, actually funding next gen hardware specs, etc.

    In my eyes, the last time Intel was even “on top” of AMD was the skylake overclock era where single thread performance was still sought after heavily.

    Hilariously though my servers are all Intel xeons because of their sheer production volume making used parts much cheaper than AMD.