Jump to content

D.Draker

Member
  • Posts

    3,846
  • Joined

  • Last visited

  • Days Won

    172
  • Donations

    0.00 USD 
  • Country

    France

Everything posted by D.Draker

  1. Excuse me, I don't like "everyone is bad approach". A specific matter is being discussed, and it's not about SSL, why? Because it doesn't aim to replace 'em! It (QUIC) aims to replace http/2 connections.
  2. I increased the page file to 32GB and it helped a bit. At least now I can finish to browse the latest goods in the store where I purchase sports food without crashing.
  3. Axal. Pff! Giving up already? https://www.collinsdictionary.com/dictionary/english/axal
  4. Those they change manually in the end, to target a specific OS version. I think win32 wrote about it somewhere.
  5. AstroSkipper, which sites did you test it with? I have the same issue Dave wrote about, memory leaks (and then crashes, sometimes just hangs) while scrolling instagram. I have 16Gb of RAM currently, can extend to 32.
  6. Of course not, but it's not a bug deal, just open with CFF Explorer and change PE Header to 5.1 or smth. But! I guess there was a reason he blocked it from running on OS below 10.
  7. In case you missed, Hybrid Post Quantum Key + QUIC (Kyber draft "X25519Kyber768Draft00"), instructions on bruteforcing that weak "encryption" method. https://msfn.org/board/topic/186176-x25519kyber768draft00-hybrid-post-quantum-secure-key/?do=findComment&comment=1265284
  8. You're indeed right! It very well can be, seeing they already call it HTTP/3, I still hope it won't happen very soon because the format is flawed.
  9. Oh, not again! Kyber has been obsolete and outdated for ages, I warned you, you don't listen, I honestly don't understand why. D.Draker never gives bad advice. On the link below, you can enjoy the precise instructions on bruteforcing that weak "encryption" method. "Challenge 1: Breaking baby Kyber." "After a couple of hours (or way less depending on your configurations), we obtain the following solution..." Decrypting the communications: "From this point, having recovered the four server private keys (one for each communication), the rest of the challenge is straightforward. Having access to the ciphertext from the pcap file, we can use the OQS_KEM_kyber_NS_decaps function to recover the 32-byte shared secret. Here is the example code for the case NS5" https://blog.quarkslab.com/sandboxaq-ctf-2024.html
  10. You don't have to worry about it, it's not used on older OS like XP. Vista needs a small update for 11, KB971512 and for Firefox - KB2117917, too.
  11. From my experience, 382.xx versions and below are the only ones that were written for Windows Vista and 7. Later are just ported 10 drivers. To be 100% sure, try R375 (376.xx) series.
  12. Yes, looks very weird it's still not there, I mean for a fifteen years old totally out-of-support buggy OS.
  13. I'd start with a well-known, 100% proven to be working video driver. Then try another videocard, I had a similar issue, the reason was - one dead VRAM module Korean Hynix. Unfortunately I can't assist in details, I'm still recovering from an eye trauma.
  14. Probably Thorium author assumes you have the latest kernel from March 2023 and didn't bother to adjust to the older version.
  15. Supermium is the same as usual Chrome, but with tweaks to make it work on old OS. GDI rendering instead of Dwrite for XP, rewritten memory functioning. Supermium understands Chrome flags. Some flags added, some removed. All of the usual connections to Google servers are present.
  16. Real
  17. Heal
  18. Zeal
  19. Meal
  20. By any chance, no PAE patch?
  21. Mear
  22. I'm not sure I understand, you force the PC off to prevent the long Supermium startup you wrote about? Why not just wait and/or kill it with the task manager?
  23. team
  24. peak
×
×
  • Create New...