Hacker Newsnew | past | comments | ask | show | jobs | submit | tech234a's commentslogin

This article is about another one of Microsoft’s Copilot products.

However you can disable the AI chat window on the GitHub homepage in settings: https://github.com/settings/copilot/features


This is an app published by Google itself


It’s currently March

Oops. Thank you for correcting me!

That page was written by Jason Scott in 2011 and has barely been changed since then.


Why mess with perfection?


Notably these exploits were originally patched for newer devices in 2023 and 2024. However, the Coruna exploits are now publicly available because some of the IOC URLs mentioned in Google's recent blog post [1] were found to still be live. Jailbreakers are already repurposing the code to make web-based tools [2].

[1]: https://cloud.google.com/blog/topics/threat-intelligence/cor...

[2]: https://x.com/Little_34306/status/2031823581513204009 (Note: the link in this tweet goes to an exploit page that uses code repurposed from malware)


So when the exploit was discovered these phones were supposed to still receive security updates? And Apple decided to not patch these because what?

Thanks Google for forcing their hand.



That was something else entirely. Not for scripting but to write compiled ActiveX browser add-ons.


At least they increased the base storage to 256GB


The webpage would have to scan the entire UUID space to create this fingerprint, which seems unlikely.


Just have a database of UUIDs. Seems pretty trivial to generate and sort as it's only 16 bytes each.


That's actually a bright idea! Have you ever thought about applying for VC funds?

Once you deliver that, you can also think about a database of natural numbers!


But that has no moat. Anyone can generate a database of natural numbers using SOTA models.


lol

Let's go a step further and just iterate through them on the client. I plan on having this phone well past the heat death of the universe, so this is guaranteed to finish on my hardware.

  function* uuidIterator() {
   const bytes = new Uint8Array(16); 
   while (true) {
     yield formatUUID(bytes);

     let carry = 1;
     for (let i = 15; i >= 0 && carry; i--) {
       const sum = bytes[i] + carry;
       bytes[i] = sum & 0xff;
       carry = sum > 0xff ? 1 : 0;
     }
 
     if (carry) return;
   }
 }
 
 function formatUUID(b) {
   const hex = [...b].map(x => x.toString(16).padStart(2, "0"));
   return (
     hex.slice(0, 4).join("") + "-" +
     hex.slice(4, 6).join("") + "-" +
     hex.slice(6, 8).join("") + "-" +
     hex.slice(8, 10).join("") + "-" +
     hex.slice(10, 16).join("")
   );
 }
This is free. Feel free to use it in production.


What license is this? Company policy says we can't use Apache licensed stuff.


Free space heater



The write-up for it is surprisingly interesting! https://eieio.games/blog/writing-down-every-uuid/#toc:entrop...


Woosh


someone took your joke and made it real


16 bytes is a lot. 4 bytes are within reach, we can scan all of them quickly, but even 8 bytes are already too much.

Kolmogorov said that computers do not help with naturally hard tasks; they raise a limit compared to what we can fo manually, but above that limit the task stays as hard is it was.



"Just" have a database, and then what? I can set up a database of all UUIDs very easily, but I don't think it's helpful.


Where are you storing them, a black hole?


All you need is basic compression, like storing the start and stop points of each block of UUIDs in the database.

Wait, you already linked to everyuuid. Do you think the server it's on uses black hole storage?


Fast writes, very slow reads.


I would store them as offsets within the digits of pi.



See also: a demo page for the same technique that can enumerate many extensions installed in your browser: https://browserleaks.com/chrome


Yuck. Disgusting that extension detection is possible.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: