Nostr notes by LΞX/NØVΛ :Fire_Lesbian:

So today as #CISO i recommended to a meeting to add a ...

2025-10-16T12:55:19Z

So today as #CISO i recommended to a meeting to add a Nextcloud 📱☁️💻 (npub1rk6…hv4q) server in our system to see if it can help us, increase our data security while cutting the cost of Microsoft.

3 years ago i would not even dared to propose it, now they will research onto it so they consider it.

Big win for #FOSS

at least if we also had open sim, both hardware and software, we ...

2025-10-15T23:27:17Z

In reply to nevent1q…azus
_________________________

at least if we also had open sim, both hardware and software, we could, unlike know, be sure that even if the tower wanted they could not infect our device.

because even if not probable, as i guess many people have monitored the sim, it's possible that they have a function in the sim that try to infect the OS or try to take over the GPS to give info to the tower.

the lack of transparency open the door for many bad thing to happen.

you must mean open hardware and source sim ? because the sim is a ...

2025-10-15T23:12:12Z

In reply to nevent1q…q08t
_________________________

you must mean open hardware and source sim ?

because the sim is a micro computer in itself, with it's own cpu, ram etc.

Also here even if we had an open hardware sync and all source open the issue reside in the network itself, so even there they could track you.

we can only fix this by disabling anything before 5G SA, as the SS7 issue was only fixed on 5G SA, so even 5G NSA is vulnerable as it reuse the 4G config.

NSA for Non Stand Alone

just hope they will support modern and secure hardware, like the ...

2025-10-15T21:18:49Z

In reply to nevent1q…fuge
_________________________

just hope they will support modern and secure hardware, like the one GrapheneOS (npub1kwa…e0nj) like to work with so we can have more open and secure device to chose from.

they will still track you, because it's not your phone they ...

2025-10-15T13:31:33Z

In reply to nevent1q…ezng
_________________________

they will still track you, because it's not your phone they track but your sim.

So if you move your sim to an hotspot, you move the problem and they will track the hotspot instead.

also Wi‑Fi‑calling can leak the same IMSI over the internet, so you will remain trackable.

And disabling 2G, 3G, or 4G on the client side will do nothing as it's a vulnerability in the ISP core network.

As such it will remain.

The only FIX is to disable everything brefore 5G (Stand alone) and use 5G stand alone.

As 5G NSA (Non Stand Alone), use 4G control model that is vulnerable too.

and as i said previously, the hotspot itself will be tracked anyway in your "test"

thanks, i was asking if the "missing part" is already in ...

2025-10-15T01:29:49Z

In reply to nevent1q…aht8
_________________________

thanks, i was asking if the "missing part" is already in the 901 (i obviously enabled the preview), but since it cover december it's the case.

I was asking because i like to maintain track of issue per device to know witch one are vulnerable to what.

Thanks again for your work :)

@npub1kwa…e0nj does this mean that on the last 901 version ...

2025-10-14T23:58:44Z

GrapheneOS (npub1kwa…e0nj) does this mean that on the last 901 version it's already fix ? (the CVE from december update i mean).

Tracked as CVE-2025-48561, the underlying flaw was addressed by Google in a recent Android security patch. The research team told Google and Samsung that the initial fix was insufficient, and Google now plans to issue an additional patch for Pixnapping in the December Android update cycle. No exploitation attempts are currently known in the wild. GPU vendors, however, are reportedly still declining to patch the underlying GPU.zip side-channel issue.

at later date could you make more clear witch new cve is ...

2025-10-10T00:30:49Z

In reply to nevent1q…kvkq
_________________________

at later date could you make more clear witch new cve is "fixed" between 01 patch in the release note, because it's not clear on the first read witch are the new cve fixed and witch one where already

for instance here i had to go to the older post, to see, on this version of .01 the new CVE are : CVE-2025-48622, CVE-2025-48626, CVE-2025-48628, CVE-2025-48629

both apple / google make billion with it with nearly no return ...

2025-10-09T13:18:26Z

In reply to nevent1q…vgzn
_________________________

both apple / google make billion with it with nearly no return for KDE (npub1ncy…3x0q)