AlexanderYamanu

well, I configure my services te request their own wildcard certs from a caching proxy acme to letsencrypt. Easy peasy.

wow, so many apples and oranges comparisons. No wait, I mean apples and cars comparisons.

Anyway, this is clickbait.

I have read the article. It's speculative and not a reveal of anything new. All is ITU spec and came down from there. So there is quite some overlap in emergency service short code regions. Another poster mentions 'ping', which is called pinprick for 112, which does work always, but requires authorization to be used. That I can confirm from experience.

yeah, there always was. It's a service code, like getting your imei. But it was a weird long one, and manufacturer dependent. Now UI switches are created for it apparantly. Can't find it anywhere on the internet though. I don't work there anymore, so can't look it up.

euhm, well. 112 programmer here. There are multiple levels. Cell tower triangulation come in automatically from providers. But they are only in tower numbers. They might be wrongly entered by engineers, hence the confirming question about where you are. Second is subscription information, as in registered address. Chances are if called from nearby your address, you are at your address. Next is a text to your phone number, which is intercepted by firmware and sends gps coords back. This can be turned off, since implementation.

Apparantly a WD_BLACK SN770 1TB, fw 731100WD, drive is affected by this update. I can confirm that the update to 24H2 was started and that the SSD has gotten a corrupted partition table. Diskpart shows nothing, TestDisk shows double entries and not markers and the log says check_part_gpt failed for partition. With the corresponding line No FAT, NTFS, ext2, JFS, Reiser, cramfs, or XFS marker in the console. I am currently rebuilding the partition table from gpt backup, but I don't know if the 24H2 update has a repartitioning action in it. Also the boot partition is Bitlocker enabled. It is a nice challenge to try and recover it fully.

But, if the update hasn't been completed and the hammering continues, then I think chances are it might happen again.

My guess is that the firmware of the ssd needs to be updated first to account for the HMD bug?

Oh well...