toad.social

Kevin Karhan :verified:<a href="https://cloudisland.nz/@xssfox" class="u-url mention" rel="nofollow noopener" target="_blank">@xssfox</a> <a href="https://hachyderm.io/@SnoopJ" class="u-url mention" rel="nofollow noopener" target="_blank">@SnoopJ</a> <a href="https://cloudisland.nz/@pjf" class="u-url mention" rel="nofollow noopener" target="_blank">@pjf</a> really?Is <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a> that cyberfacist?<ul><li>Like I know one's not supposed to have stuff or rather is not allowed to use it for obvious reasons but criminalizing mere possession is just absurd.</li><li>But then again <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a> also <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a>-<a href="https://www.youtube.com/watch?v=zIJavqEzEIw" rel="nofollow noopener" target="_blank">banned</a> devices due to <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> mandate and <a href="https://www.youtube.com/watch?v=r2h3iSA-Vac" rel="nofollow noopener" target="_blank">banned</a> <a href="https://www.youtube.com/watch?v=1OwUphqTBSw" rel="nofollow noopener" target="_blank">encrypted devices</a>…</li></ul>

Kevin Karhan :verified:<a href="https://chaos.social/@LaF0rge" class="u-url mention" rel="nofollow noopener" target="_blank">@LaF0rge</a> <a href="https://mastodon.ie/@kDelta" class="u-url mention" rel="nofollow noopener" target="_blank">@kDelta</a> <a href="https://mastodon.social/@stman" class="u-url mention" rel="nofollow noopener" target="_blank">@stman</a> <a href="https://infosec.exchange/@Sempf" class="u-url mention" rel="nofollow noopener" target="_blank">@Sempf</a> espechally in places like <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a> where regulators like <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> get record-breaking bids for <a href="https://infosec.space/tags/spectrum" class="mention hashtag" rel="nofollow noopener" target="_blank">#spectrum</a> allocations solidly into the billions! <ul><li>And having at least narrowband <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> coverage is considered a "necessary evil" to fulfill spectrum obligations and keep pre-paid assignments if they don't want to get those yoink'd like <a href="https://infosec.space/tags/Quam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quam</a> when they <a href="https://de.wikipedia.org/wiki/Quam" rel="nofollow noopener" target="_blank">faceplanted after their painfully failed launch</a>. </li><li>Not to mention <a href="https://infosec.space/tags/eCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#eCall</a> uses <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> and has been made mandatory for new cars since 2017...</li><li>Also <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a> currently <a href="https://www.youtube.com/watch?v=Q6qb9dml6So" rel="nofollow noopener" target="_blank">learns the hard way</a> that even <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> devices switch to 2G and/or <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> calling once they are dialling <code>000</code> (their local emergency services hotline).</li></ul>

Kevin Karhan :verified:<a href="https://chaos.social/@LaF0rge" class="u-url mention" rel="nofollow noopener" target="_blank">@LaF0rge</a> <a href="https://mastodon.social/@stman" class="u-url mention" rel="nofollow noopener" target="_blank">@stman</a> <a href="https://mastodon.ie/@kDelta" class="u-url mention" rel="nofollow noopener" target="_blank">@kDelta</a> <a href="https://infosec.exchange/@Sempf" class="u-url mention" rel="nofollow noopener" target="_blank">@Sempf</a> obviously that's why it <a href="https://infosec.space/@kkarhan/114863029952059372" rel="nofollow noopener" target="_blank">was discontinued for a time</a> in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a>, as it was considered as obsolete as <a href="https://infosec.space/tags/HSCSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HSCSD</a> is in light of faster standards that - even without guaranteed bandwith - will yield higher throughput.<ul><li>Obviously <a href="https://infosec.space/tags/CellBroadcast" class="mention hashtag" rel="nofollow noopener" target="_blank">#CellBroadcast</a> will necessitate a constant bandwith allocation for functionality as it's design is based upon repeating a message until it's transmissiom being removed.</li></ul>Still, even in contended <a href="https://infosec.space/tags/spectrum" class="mention hashtag" rel="nofollow noopener" target="_blank">#spectrum</a> this is manageable, espechally since most <a href="https://infosec.space/tags/MNOs" class="mention hashtag" rel="nofollow noopener" target="_blank">#MNOs</a> only maintain vestigal <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> or <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> infrastructure solely for <a href="https://infosec.space/tags/emergency" class="mention hashtag" rel="nofollow noopener" target="_blank">#emergency</a> coverage and reliability, as <a href="https://www.youtube.com/watch?v=Q6qb9dml6So" rel="nofollow noopener" target="_blank">most phones will call emergency services over 2G and 3G</a> and not via <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a>. <ul><li>To add insult to injury, most BSCs will downgrade to 2G-only service by default in case of power loss to maximize UPS range and in the case of <a href="https://infosec.space/tags/NewZealand" class="mention hashtag" rel="nofollow noopener" target="_blank">#NewZealand</a> even switch off all services but <a href="https://infosec.space/tags/SMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SMS</a> & <a href="https://infosec.space/tags/EmergencyServicesCalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#EmergencyServicesCalling</a> to enshure people in need can get their calls out, as the population is instructed to use SMS for person-to-person communication (as SMS is a low-priority, non-realtime service using excess bandwith and thus not compete with calling like <a href="https://infosec.space/tags/EDGE" class="mention hashtag" rel="nofollow noopener" target="_blank">#EDGE</a> and <a href="https://infosec.space/tags/CSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSD</a> would.</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@stman" class="u-url mention" rel="nofollow noopener" target="_blank">@stman</a> <a href="https://infosec.exchange/@Sempf" class="u-url mention" rel="nofollow noopener" target="_blank">@Sempf</a> <a href="https://chaos.social/@LaF0rge" class="u-url mention" rel="nofollow noopener" target="_blank">@LaF0rge</a> yes.Because physical SIMs, like any "cryptographic chipcard" (i.e. <a href="https://social.nitrokey.com/@nitrokey" class="u-url mention" rel="nofollow noopener" target="_blank">@nitrokey</a> ) did all that fancy public/private crypto on silicon and unless that was compromizeable (which AFAICT always necessistated physical access to the <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a>, espechally in pre-<a href="https://infosec.space/tags/OMAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMAPI</a> devices) the SIM wasn't 'cloneable' and the weakest link always had been the <a href="https://infosec.space/tags/MNO" class="mention hashtag" rel="nofollow noopener" target="_blank">#MNO</a> /.<a href="https://infosec.space/tags/MVNO" class="mention hashtag" rel="nofollow noopener" target="_blank">#MVNO</a> issueing (may it be through <a href="https://infosec.space/tags/SocialHacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#SocialHacking</a> employees into <a href="https://infosec.space/tags/SimSwapping" class="mention hashtag" rel="nofollow noopener" target="_blank">#SimSwapping</a> or LEAs showng up with a warrant and demanding "<a href="https://infosec.space/tags/LawfulInterception" class="mention hashtag" rel="nofollow noopener" target="_blank">#LawfulInterception</a>"):<ul><li>These "attack vectors" were known and whilst unfixable they could at least be mitigated by i.e. NEVER using a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumber</a> for anything and/or using anonymously obtained <a href="https://infosec.space/tags/SIMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIMs</a>. But more and more services like <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> did <a href="https://infosec.space/tags/regression" class="mention hashtag" rel="nofollow noopener" target="_blank">#regression</a> demanding <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> and more and more nations criminalized <a href="https://infosec.space/tags/AnonymousSimCards" class="mention hashtag" rel="nofollow noopener" target="_blank">#AnonymousSimCards</a> under utterly <a href="https://infosec.space/tags/cyberfacist" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberfacist</a> & <a href="https://infosec.space/tags/FalsePretenses" class="mention hashtag" rel="nofollow noopener" target="_blank">#FalsePretenses</a>!</li></ul>Add to that the regression in flexibility: Unlike a <a href="https://infosec.space/tags/SimCard" class="mention hashtag" rel="nofollow noopener" target="_blank">#SimCard</a> which was designed as a vendor-independent, <a href="https://infosec.space/tags/MultiVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#MultiVendor</a>, <a href="https://infosec.space/tags/MultiProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#MultiProvider</a>, device agnostic unit to facilitate the the <a href="https://infosec.space/tags/authentification" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentification</a> and <a href="https://infosec.space/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a> in <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GSM</a> (and successor standards), <a href="https://infosec.space/tags/eSIMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#eSIMs</a> act to restrict <a href="https://infosec.space/tags/DeviceFreedom" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeviceFreedom</a> and <a href="https://infosec.space/tags/ConsumerChoice" class="mention hashtag" rel="nofollow noopener" target="_blank">#ConsumerChoice</a>, which with shit like <a href="https://infosec.space/tags/KYC" class="mention hashtag" rel="nofollow noopener" target="_blank">#KYC</a> per <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a> (i.e. <a href="https://infosec.space/tags/Turkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Turkey</a> demands it after 90 days of roaming per year) und <a href="https://infosec.space/tags/lMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#lMEI</a>-based <a href="https://infosec.space/tags/Allowlisting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Allowlisting</a> (see <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a>'s shitty <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> + <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> & <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> shutdown!) are just acts to clamp down on <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> and <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>.<ul><li>And with <a href="https://infosec.space/tags/EID" class="mention hashtag" rel="nofollow noopener" target="_blank">#EID</a> being unique per <a href="https://infosec.space/tags/eSIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#eSIM</a> (like the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a> on top!) there's nothing stopping <a href="https://infosec.space/tags/cyberfacist" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberfacist</a> regimes like "P.R." <a href="https://infosec.space/tags/China" class="mention hashtag" rel="nofollow noopener" target="_blank">#China</a>, <a href="https://infosec.space/tags/Russia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Russia</a>, <a href="https://infosec.space/tags/Iran" class="mention hashtag" rel="nofollow noopener" target="_blank">#Iran</a>, ... from banning "<a href="https://infosec.space/tags/eSIMcards" class="mention hashtag" rel="nofollow noopener" target="_blank">#eSIMcards</a>" (<a href="https://infosec.space/tags/eSIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#eSIM</a> in SIM card form factor) or entire device prefixes (i.e. all phones that are supported by <a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> ), as M(V)NOs see the EID used to deploy/activate a profile (obviously they don't want people to activate eSIMs more than once, unless explicitly allowed otherwise.</li></ul>"[…] [Technologies] must always be evaluated for their ability to oppress. […] <ul><li>Dan Olson</li></ul>And now you know why I consider a <a href="https://infosec.space/tags/smartphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#smartphone</a> with eSIM instead of two SIM slots not as a real <a href="https://infosec.space/tags/DualSIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualSIM</a> device because it restricts my ability to freely move devices.<ul><li>And whilst German Courts reaffirmed §77 TKG (Telco Law)'s mandate to letting people choose their devices freely, (by declarong <a href="https://infosec.space/tags/fees" class="mention hashtag" rel="nofollow noopener" target="_blank">#fees</a> for reissue of eSIMs illegal) that is only enforceable towards M(V)NOs who are in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a>, so 'good luck' trying to enforce that against some overseas roaming provider.</li></ul>Thus <a href="https://infosec.space/tags/Impersonation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Impersonation</a> attacks in GSM-based networks are easier than ever before which in the age of more skilled than ever <a href="https://infosec.space/tags/Cybercriminals" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cybercriminals</a> and <a href="https://infosec.space/tags/Cyberterrorists" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cyberterrorists</a> (i.e. <a href="https://infosec.space/tags/NSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#NSA</a> & <a href="https://infosec.space/tags/Roskomnadnozr" class="mention hashtag" rel="nofollow noopener" target="_blank">#Roskomnadnozr</a>) puts espechally the average <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterate</a> User at risk.<ul><li>I mean, anyone else remember the <a href="https://infosec.space/tags/Kiddies" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kiddies</a> that fucked around with <a href="https://infosec.space/tags/CIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CIA</a> director <a href="https://infosec.space/tags/Brennan" class="mention hashtag" rel="nofollow noopener" target="_blank">#Brennan</a>? Those were just using their "weapons-grade <a href="https://infosec.space/tags/boredom" class="mention hashtag" rel="nofollow noopener" target="_blank">#boredom</a>", not being effective, for-profit cyber criminals!</li></ul>And then think about those who don't have privilegued access to protection by their government, but rather "privilegued access" to prosecution by the state because their very existance is criminalized... The only advantage eSIMs broight in contrast is 'logistical' convenience because it's mostly a <a href="https://infosec.space/tags/QRcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#QRcode</a> and that's just a way to avoid typos on a cryptic <a href="https://infosec.space/tags/LocalProfileAgent" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalProfileAgent</a> link.

Kevin Karhan :verified:<a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> <a href="https://fedi.omada.cafe/@fluffery" class="u-url mention" rel="nofollow noopener" target="_blank">@fluffery</a> <a href="https://chaos.social/@maumau" class="u-url mention" rel="nofollow noopener" target="_blank">@maumau</a> <a href="https://social.tchncs.de/@BryanGreyson" class="u-url mention" rel="nofollow noopener" target="_blank">@BryanGreyson</a> <a href="https://mas.to/@fairphone" class="u-url mention" rel="nofollow noopener" target="_blank">@fairphone</a> I.e. <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> could not use any of those because they don't support <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> (not just in <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a>) and thus would be blocked by the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a>-<a href="https://infosec.space/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a>! <a href="https://www.youtube.com/watch?v=zIJavqEzEIw" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=zIJavqEzEIw</a>

LINux on MOBileWeekly GNU-like <a href="https://linuxmobile.social/tags/mobilelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#MobileLinux</a> Update (25/2025): Packed with Goodies <a href="https://linmob.net/weekly-update-25-2025/" rel="nofollow noopener" target="_blank">https://linmob.net/weekly-update-25-2025/</a> This week really was something: <a href="https://linuxmobile.social/tags/postmarketos" class="mention hashtag" rel="nofollow noopener" target="_blank">#postmarketOS</a> ship 25.06 (which, among other things, adds systemd) and work to reverse-engineer <a href="https://linuxmobile.social/tags/volte" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a>, <a href="https://linuxmobile.social/tags/furios" class="mention hashtag" rel="nofollow noopener" target="_blank">#FuriOS</a> 13.1.0 lands with Open-Store support (for <a href="https://linuxmobile.social/tags/ubuntutouch" class="mention hashtag" rel="nofollow noopener" target="_blank">#UbuntuTouch</a> apps) and plenty of other improvements, <a href="https://linuxmobile.social/tags/plasmamobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#PlasmaMobile</a> share detailed log of all the fixes and improvements they managed to land in the past year (and what's to come), Jolla announce free <a href="https://linuxmobile.social/tags/sailfishos" class="mention hashtag" rel="nofollow noopener" target="_blank">#SailfishOS</a> updates for all <a href="https://linuxmobile.social/tags/jollac2" class="mention hashtag" rel="nofollow noopener" target="_blank">#JollaC2</a> customers, I managed to interview <a href="https://linuxmobile.social/tags/liberux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Liberux</a> about their Nexx phone - but there's way more still, including a packed Apps section. Enjoy! <a href="https://linuxmobile.social/tags/furilabsflx1" class="mention hashtag" rel="nofollow noopener" target="_blank">#FuriLabsFLX1</a> <a href="https://linuxmobile.social/tags/pureos" class="mention hashtag" rel="nofollow noopener" target="_blank">#PureOS</a> <a href="https://linuxmobile.social/tags/librem5" class="mention hashtag" rel="nofollow noopener" target="_blank">#Librem5</a> <a href="https://linuxmobile.social/tags/liberuxnexx" class="mention hashtag" rel="nofollow noopener" target="_blank">#LiberuxNexx</a> <a href="https://linuxmobile.social/tags/pinephone" class="mention hashtag" rel="nofollow noopener" target="_blank">#PinePhone</a> <a href="https://linuxmobile.social/tags/phosh" class="mention hashtag" rel="nofollow noopener" target="_blank">#Phosh</a> <a href="https://linuxmobile.social/tags/linuxmobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxMobile</a> <a href="https://linuxmobile.social/tags/linuxonmobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxOnMobile</a>

Kevin Karhan :verified:<a href="https://deppenkessel.de/@nofollownoindex" class="u-url mention" rel="nofollow noopener" target="_blank">@nofollownoindex</a> <a href="https://infosec.exchange/@cR0w" class="u-url mention" rel="nofollow noopener" target="_blank">@cR0w</a> <a href="https://haunted.computer/@Dio9sys" class="u-url mention" rel="nofollow noopener" target="_blank">@Dio9sys</a> <a href="https://infosec.exchange/@da_667" class="u-url mention" rel="nofollow noopener" target="_blank">@da_667</a> <a href="https://infosec.space/tags/Tenda" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tenda</a> <a href="https://infosec.space/tags/EoL" class="mention hashtag" rel="nofollow noopener" target="_blank">#EoL</a>'d such new hardware?<ul><li>Shit, that reminds me that some folks just recently got themselves some <a href="https://infosec.space/tags/4G06" class="mention hashtag" rel="nofollow noopener" target="_blank">#4G06</a> & <a href="https://infosec.space/tags/4G07" class="mention hashtag" rel="nofollow noopener" target="_blank">#4G07</a> units because they needed a cheap <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> - <a href="https://infosec.space/tags/FWT" class="mention hashtag" rel="nofollow noopener" target="_blank">#FWT</a> to hookup seniors' landline phones on because it's cheaper to migrate to <a href="https://infosec.space/tags/sipgate" class="mention hashtag" rel="nofollow noopener" target="_blank">#sipgate</a> / <a href="https://infosec.space/tags/simquadrat" class="mention hashtag" rel="nofollow noopener" target="_blank">#simquadrat</a> than having to swallow a forced migration from <a href="https://infosec.space/tags/AnnexB" class="mention hashtag" rel="nofollow noopener" target="_blank">#AnnexB</a> - based <a href="https://infosec.space/tags/PSTN" class="mention hashtag" rel="nofollow noopener" target="_blank">#PSTN</a> (<a href="https://infosec.space/tags/HyTNAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#HyTNAS</a>) to shitty and overpriced <a href="https://infosec.space/tags/VDSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#VDSL</a>!</li></ul>

StrypeyIt appears my Android can do 4G mobile data, but not VoLTE calling. So ... is that a software support limitation? Could installing LineageOS make it VoLTE capable? There seems to have a LineageOS build for it;<a href="https://wiki.lineageos.org/devices/fajita/" rel="nofollow noopener" translate="no" target="_blank">https://wiki.lineageos.org/devices/fajita/</a><a href="https://mastodon.nzoss.nz/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> <a href="https://mastodon.nzoss.nz/tags/VOLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VOLTE</a> <a href="https://mastodon.nzoss.nz/tags/LineageOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#LineageOS</a> <a href="https://mastodon.nzoss.nz/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#4G</a>

Pyrzout :vm:4G Calling (VoLTE) flaw allowed to locate any O2 customer with a phone call – Source: securityaffairs.com <a href="https://ciso2ciso.com/4g-calling-volte-flaw-allowed-to-locate-any-o2-customer-with-a-phone-call-source-securityaffairs-com/" rel="nofollow noopener" translate="no" target="_blank">https://ciso2ciso.com/4g-calling-volte-flaw-allowed-to-locate-any-o2-customer-with-a-phone-call-source-securityaffairs-com/</a> <a href="https://social.skynetcloud.site/tags/rssfeedpostgeneratorecho" class="mention hashtag" rel="nofollow noopener" target="_blank">#rssfeedpostgeneratorecho</a> <a href="https://social.skynetcloud.site/tags/informationsecuritynews" class="mention hashtag" rel="nofollow noopener" target="_blank">#informationsecuritynews</a> <a href="https://social.skynetcloud.site/tags/ITInformationSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITInformationSecurity</a> <a href="https://social.skynetcloud.site/tags/SecurityAffairscom" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityAffairscom</a> <a href="https://social.skynetcloud.site/tags/CyberSecurityNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurityNews</a> <a href="https://social.skynetcloud.site/tags/PierluigiPaganini" class="mention hashtag" rel="nofollow noopener" target="_blank">#PierluigiPaganini</a> <a href="https://social.skynetcloud.site/tags/SecurityAffairs" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityAffairs</a> <a href="https://social.skynetcloud.site/tags/SecurityAffairs" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityAffairs</a> <a href="https://social.skynetcloud.site/tags/BreakingNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#BreakingNews</a> <a href="https://social.skynetcloud.site/tags/SecurityNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityNews</a> <a href="https://social.skynetcloud.site/tags/surveillance" class="mention hashtag" rel="nofollow noopener" target="_blank">#surveillance</a> <a href="https://social.skynetcloud.site/tags/hackingnews" class="mention hashtag" rel="nofollow noopener" target="_blank">#hackingnews</a> <a href="https://social.skynetcloud.site/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://social.skynetcloud.site/tags/hacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#hacking</a> <a href="https://social.skynetcloud.site/tags/Mobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mobile</a> <a href="https://social.skynetcloud.site/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> <a href="https://social.skynetcloud.site/tags/O2" class="mention hashtag" rel="nofollow noopener" target="_blank">#O2</a>

JannikThe mobile core team at <a href="https://sipgate.social/@sipgate" class="u-url mention" rel="nofollow noopener" target="_blank">@sipgate</a> has disclosed a <a href="https://chaos.social/tags/SIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIP</a> parsing bug in <a href="https://chaos.social/tags/mediatek" class="mention hashtag" rel="nofollow noopener" target="_blank">#mediatek</a>'s <a href="https://chaos.social/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a>/ <a href="https://chaos.social/tags/VoWifi" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoWifi</a> stack which leads to a null-pointer-dereference and ultimately Denial of Service of VoLTE telephony for the affected devices. Around 40 baseband chips were affected which were deployed to over 1000 devices since 2017.<a href="https://www.sipgate.de/blog/sipgate-discovers-null-pointer-dereference-in-mediatek-volte-stack-firmware" rel="nofollow noopener" translate="no" target="_blank">https://www.sipgate.de/blog/sipgate-discovers-null-pointer-dereference-in-mediatek-volte-stack-firmware</a>Thanks to <a href="https://mastodon.social/@hendrikkiel" class="u-url mention" rel="nofollow noopener" target="_blank">@hendrikkiel</a> for the great cooperation!

Hambone Fakenamington<a href="https://mastdatabase.co.uk/blog/2025/05/o2-expose-customer-location-call-4g/" rel="nofollow noopener" translate="no" target="_blank">https://mastdatabase.co.uk/blog/2025/05/o2-expose-customer-location-call-4g/</a>oops - anyone who's likely to be stalked and uses O2 needs to know this is possible and is trivial to do!<a href="https://fosstodon.org/tags/O2" class="mention hashtag" rel="nofollow noopener" target="_blank">#O2</a> <a href="https://fosstodon.org/tags/VMO2" class="mention hashtag" rel="nofollow noopener" target="_blank">#VMO2</a> <a href="https://fosstodon.org/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> <a href="https://fosstodon.org/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#4G</a> <a href="https://fosstodon.org/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GSM</a> <a href="https://fosstodon.org/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://fosstodon.org/tags/geolocation" class="mention hashtag" rel="nofollow noopener" target="_blank">#geolocation</a>

LiohIch fühle mich richtig getrieben von der Industrie. Ich habe ein Pixel 3a Handy. Das ist jetzt 5 Jahre alt und funktioniert super, ich liebe es! Google hat es schon lange aufgegeben. Zum Glück stellt CalyxOS immer noch so gut es geht Updates bereit. Doch nun kommt mein Carrier und stellt im Sommer 3G ab. Das Gerät kann VoLTE, doch der Provider hat es nicht in dessen Whitelist freigegeben. Ich werde zum Neukauf genötigt, obwohl ich mein Handy gerne weiter nutzen würde. <a href="https://social.anoxinon.de/tags/sustainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#sustainability</a> <a href="https://social.anoxinon.de/tags/volte" class="mention hashtag" rel="nofollow noopener" target="_blank">#volte</a>

AptiviUbuntu Touch VoLTE support rollout begins, starting from Fairphone 5 and Volla 22.<a href="https://mastodon.social/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/UbuntuLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#UbuntuLinux</a> <a href="https://mastodon.social/tags/UbuntuTouch" class="mention hashtag" rel="nofollow noopener" target="_blank">#UbuntuTouch</a> <a href="https://mastodon.social/tags/UBports" class="mention hashtag" rel="nofollow noopener" target="_blank">#UBports</a> <a href="https://mastodon.social/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> <a href="https://mastodon.social/tags/Volla" class="mention hashtag" rel="nofollow noopener" target="_blank">#Volla</a> <a href="https://mastodon.social/tags/Fairphone5" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone5</a> <a href="https://mastodon.social/tags/Volla22" class="mention hashtag" rel="nofollow noopener" target="_blank">#Volla22</a> <a href="https://mastodon.social/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> <a href="https://mastodon.social/tags/cellular" class="mention hashtag" rel="nofollow noopener" target="_blank">#cellular</a> <a href="https://mastodon.social/tags/TechNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechNews</a> <a href="https://mastodon.social/tags/TechUpdates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechUpdates</a><a href="https://officialaptivi.wordpress.com/2025/04/03/ubuntu-on-phones-now-receive-initial-volte-support/" rel="nofollow noopener" translate="no" target="_blank">https://officialaptivi.wordpress.com/2025/04/03/ubuntu-on-phones-now-receive-initial-volte-support/</a>

LoutopisteReco' bouquinesque 📕 Comment se prendre une claque en douceur et sans violence?Alors non c'est pas le sujet du livre de <a href="https://mastodon.gougere.fr/@Leo_Henry" class="u-url mention" rel="nofollow noopener" target="_blank">@Leo_Henry</a> ! On est plutôt sur un recueil d'histoires se passant au 12e siècle : chevalerie, guerre, miracle, religion, histoires cheloues, amitié, amourça m'a donné envie de lire des récits autour de la mythologie chrétienne 😅 PS: pour une fois que que je trouve l'illustration belle chez Folio !<a href="https://toot.rhizome.red/tags/livre" class="mention hashtag" rel="nofollow noopener" target="_blank">#livre</a> <a href="https://toot.rhizome.red/tags/fantasy" class="mention hashtag" rel="nofollow noopener" target="_blank">#fantasy</a> <a href="https://toot.rhizome.red/tags/religion" class="mention hashtag" rel="nofollow noopener" target="_blank">#religion</a> <a href="https://toot.rhizome.red/tags/volte" class="mention hashtag" rel="nofollow noopener" target="_blank">#volte</a>

Kevin Karhan :verified:<a href="https://mastodon.nz/@phlogiston" class="u-url mention" rel="nofollow noopener" target="_blank">@phlogiston</a> <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> <a href="https://social.librem.one/@guardianproject" class="u-url mention" rel="nofollow noopener" target="_blank">@guardianproject</a> at least <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> & <a href="https://social.bund.de/@Bundesregierung" class="u-url mention" rel="nofollow noopener" target="_blank">@Bundesregierung</a> didn't cancel <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> / <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GSM</a> / <a href="https://infosec.space/tags/EDGE" class="mention hashtag" rel="nofollow noopener" target="_blank">#EDGE</a> with the <a href="https://infosec.space/tags/3Gshutdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#3Gshutdown</a> like <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a> did recently.<ul><li>Seriously, the Ozzies <a href="https://infosec.space/@kkarhan/113866074599066600" rel="nofollow noopener" target="_blank">mandate</a> <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> and literally block <a href="https://infosec.space/tags/ImportPhones" class="mention hashtag" rel="nofollow noopener" target="_blank">#ImportPhones</a> based off <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a>!</li></ul>

Kevin Karhan :verified:And don't even get me started on <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> <a href="https://www.youtube.com/watch?v=Q6qb9dml6So" rel="nofollow noopener" target="_blank">support</a>...<ul><li>Like <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a> had the glorious idea of shutting down <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> AND <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> as well as <a href="https://infosec.space/tags/allowlisting" class="mention hashtag" rel="nofollow noopener" target="_blank">#allowlisting</a> <a href="https://www.youtube.com/watch?v=RPlTz-3estM" rel="nofollow noopener" target="_blank">only specific</a> <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a>|s, <a href="https://www.youtube.com/watch?v=zIJavqEzEIw" rel="nofollow noopener" target="_blank">banning > 500k devices</a> for no good reason.</li></ul>Also most <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> / <a href="https://infosec.space/tags/Vo5G" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vo5G</a> - devices *explicitly use <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> / <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> for <a href="https://infosec.space/tags/EmergencyCalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#EmergencyCalls</a>!<ul><li>Which is <a href="https://infosec.space/tags/funfuckingtastic" class="mention hashtag" rel="nofollow noopener" target="_blank">#funfuckingtastic</a> in a place like Australia where basically everything in nature conspires to hurt or kill humans!</li></ul><a href="https://infosec.space/tags/DownUnder" class="mention hashtag" rel="nofollow noopener" target="_blank">#DownUnder</a> <a href="https://infosec.space/tags/AUSpol" class="mention hashtag" rel="nofollow noopener" target="_blank">#AUSpol</a> <a href="https://infosec.space/tags/AUpol" class="mention hashtag" rel="nofollow noopener" target="_blank">#AUpol</a> <a href="https://infosec.space/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> <a href="https://infosec.space/tags/2Gshutdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#2Gshutdown</a> <a href="https://infosec.space/tags/3Gshutdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#3Gshutdown</a> <a href="https://infosec.space/tags/EmergencyCalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#EmergencyCalling</a>

Kevin Karhan :verified:[<a href="https://infosec.space/tags/TLDR" class="mention hashtag" rel="nofollow noopener" target="_blank">#TLDR</a>: JUST TELL ME IF YOUR TABLET CAN DO <a href="https://infosec.space/tags/CALLS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CALLS</a>!]<a href="https://infosec.space/tags/DearVendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#DearVendors</a> of <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a>-<a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tablets</a>:Off all the <a href="https://infosec.space/tags/Functions" class="mention hashtag" rel="nofollow noopener" target="_blank">#Functions</a> you can put into a <a href="https://infosec.space/tags/Specifications" class="mention hashtag" rel="nofollow noopener" target="_blank">#Specifications</a> Sheet of your Devices there's one you should ALWAYS answer clearly on your <a href="https://infosec.space/tags/Website" class="mention hashtag" rel="nofollow noopener" target="_blank">#Website</a>:DOES YOUR TABLET [with <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#4G</a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener" target="_blank">#5G</a> / …) SUPPORT MAKING PHONE CALLS?<ul><li>NOT "It can run <a href="https://infosec.space/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#WhatsApp</a>" (or whatever shitty <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> for <a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoIP</a> you think of)...</li><li>NOT "It can do <a href="https://infosec.space/tags/CSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSD</a> / <a href="https://infosec.space/tags/HSCSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HSCSD</a> / <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> / <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> /..."</li><li>But DOES IT SUPPORT <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GSM</a>-<a href="https://infosec.space/tags/Calls" class="mention hashtag" rel="nofollow noopener" target="_blank">#Calls</a> (and/or <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a>)??</li></ul>Like: IS IT TOO MUCH TO ASK TO HAVE THAT INFO IN THE SPECSHEETS?You're obviously able to list all the <a href="https://infosec.space/tags/Codecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Codecs</a> natively supported and the user-available storage as well as supported Frequency Bands, WWAN modes, WiFi channel width and the Display Glass vs. Panel dimensions including DPI of the latter and whether or not it has a hall effect sensor to detect your overpriced 1st party tablet covers!Now some folks may ask: "WHY does this matter?" or outright dismiss this as a problem.Listen: Not everyone is able or willing to carry two devices when 1 SHOULD BE ENOUGH and also some places (i.e. <a href="https://infosec.space/tags/Turkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Turkey</a>) have <a href="https://infosec.space/tags/ImportRestrictions" class="mention hashtag" rel="nofollow noopener" target="_blank">#ImportRestrictions</a> re: <a href="https://infosec.space/tags/MobileDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#MobileDevices</a>, so having more than 1 <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a> is already a "NOPE!" by the authorities.<ul><li>Also this isn't something one can "fix" post-purchase like installing <a href="https://infosec.space/tags/VLC" class="mention hashtag" rel="nofollow noopener" target="_blank">#VLC</a> to decode some obscure file format in Software: Either the <a href="https://infosec.space/tags/Baseband" class="mention hashtag" rel="nofollow noopener" target="_blank">#Baseband</a> and <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ROM</a> support <a href="https://infosec.space/tags/PhoneCalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneCalls</a> or they don't!</li></ul>So why do NONE of the <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tablet</a> manufacturers allow to <a href="https://infosec.space/tags/search" class="mention hashtag" rel="nofollow noopener" target="_blank">#search</a> or <a href="https://infosec.space/tags/filter" class="mention hashtag" rel="nofollow noopener" target="_blank">#filter</a> for that???<ul><li>Bonus points if you have lazy fucks like <a href="https://infosec.space/tags/HMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HMD</a> (aka. <a href="https://infosec.space/tags/Nokia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nokia</a>) who literally copy the <a href="https://infosec.space/tags/Safety" class="mention hashtag" rel="nofollow noopener" target="_blank">#Safety</a> & <a href="https://infosec.space/tags/Useage" class="mention hashtag" rel="nofollow noopener" target="_blank">#Useage</a> information for all <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Smartphones</a> and <a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tablets</a> and don't even bother to change "Mobile Phone" for "Tablet".</li></ul>NO, instead one has to download an obscenely huge <a href="https://infosec.space/tags/PDF" class="mention hashtag" rel="nofollow noopener" target="_blank">#PDF</a> just to then <a href="https://downloadcenter.samsung.com/content/UM/202410/20241010132004137/SM-X11X_X21X_UM_Open_UU_Ger_Rev.1.2_240925.pdf" rel="nofollow noopener" target="_blank">read on page 34</a> that for any "<a href="https://infosec.space/tags/telephony" class="mention hashtag" rel="nofollow noopener" target="_blank">#telephony</a>" function you NEED YET ANOTHER DEVICE FROM THE SAME MANUFACTURER AND HAVE TO SIGNUP WITH AN ACCOUNT and even that level of <a href="https://infosec.space/tags/abuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#abuse</a> WON'T GUARANTEE THAT IT WORKS...<ul><li>I mean, come on, this ain't some obscure functionality like <a href="https://infosec.space/tags/OMAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMAPI</a> to do some "evil sourcery" like managing an <a href="https://infosec.space/tags/eSIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#eSIM</a> that is in a <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a>-Card form factor!</li></ul>Pretty shure A LOT of other folks have the same question and ain't willing to get yet another device & <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a> just to recieve the occasional call because <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a> can't be assed to send an <a href="https://infosec.space/tags/eMail" class="mention hashtag" rel="nofollow noopener" target="_blank">#eMail</a> or learn <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a> to message one...<ul><li>Obviously they same manufacturers are able and willing to specify f-stops of the built-in cameras and list EVERY SINGLE <a href="https://infosec.space/tags/WEARABLE" class="mention hashtag" rel="nofollow noopener" target="_blank">#WEARABLE</a> they made and certify as 'compatible' with, as if anyone is gonna take their non-<a href="https://infosec.space/tags/waterproof" class="mention hashtag" rel="nofollow noopener" target="_blank">#waterproof</a> <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tablet</a> for a marathon or god forbid triathlon...</li></ul><a href="https://infosec.space/tags/Rant" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rant</a> <a href="https://infosec.space/tags/TechSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechSupport</a> <a href="https://infosec.space/tags/Technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technology</a> <a href="https://infosec.space/tags/Support" class="mention hashtag" rel="nofollow noopener" target="_blank">#Support</a> <a href="https://infosec.space/tags/Sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sysadmin</a> <a href="https://infosec.space/tags/Procurement" class="mention hashtag" rel="nofollow noopener" target="_blank">#Procurement</a> <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://infosec.space/tags/SpecSheet" class="mention hashtag" rel="nofollow noopener" target="_blank">#SpecSheet</a> <a href="https://infosec.space/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a>

Kevin Karhan :verified:<a href="https://infosec.space/@ada" class="u-url mention" rel="nofollow noopener" target="_blank">@ada</a> yeah, but then again Oz is ruled by <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterate</a> <a href="https://infosec.space/tags/Wankers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wankers</a> who decided to not only shutdown both <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> & <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> but <a href="https://www.youtube.com/watch?v=RPlTz-3estM" rel="nofollow noopener" target="_blank">literally</a> <a href="https://infosec.space/tags/ban" class="mention hashtag" rel="nofollow noopener" target="_blank">#ban</a> <a href="https://infosec.space/tags/importPhones" class="mention hashtag" rel="nofollow noopener" target="_blank">#importPhones</a> and basically lock-out any device that desn't do <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> their way...And yes, they enforce that like <a href="https://infosec.space/tags/Turkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Turkey</a> enforces people to register imported devices 30 days after import:<ul><li><a href="https://www.youtube.com/watch?v=zIJavqEzEIw" rel="nofollow noopener" target="_blank">With</a> an <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a> - <a href="https://infosec.space/tags/BanList" class="mention hashtag" rel="nofollow noopener" target="_blank">#BanList</a>!</li></ul>So if you are i.e. a <a href="https://infosec.space/tags/Tourist" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tourist</a> in <a href="https://infosec.space/tags/DownUnder" class="mention hashtag" rel="nofollow noopener" target="_blank">#DownUnder</a> and you got some serious issue, you can't even call their emergency services on 000 cuz your devices got yeeted off the network through no fault of your own!

Kevin Karhan :verified:Seriously, <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a>'s <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> & <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> <a href="https://infosec.space/tags/Shutdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shutdown</a> <a href="https://www.youtube.com/watch?v=zIJavqEzEIw" rel="nofollow noopener" target="_blank">and</a> <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a>-based <a href="https://infosec.space/tags/Blocklisting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blocklisting</a> WILL inevitably kill people And the only "tool" there is is <a href="https://infosec.space/tags/Telstra" class="mention hashtag" rel="nofollow noopener" target="_blank">#Telstra</a>'s <a href="https://www.telstrawholesale.com.au/3G-Network-Closure-Blocked-Devices-Checker.html" rel="nofollow noopener" target="_blank">Website</a> and just <a href="https://github.com/greyhat-academy/lists.d/blob/main/imei.devices.list.tsv" rel="nofollow noopener" target="_blank">teting random IMEIs</a> only yields two possible results:<ol><li>'We don't know this device at all'</li><li>"'We've not blocklisted it'*</li></ol>Even when testing it with obvious <a href="https://infosec.space/tags/2Gonly" class="mention hashtag" rel="nofollow noopener" target="_blank">#2Gonly</a> & <a href="https://infosec.space/tags/3Gonly" class="mention hashtag" rel="nofollow noopener" target="_blank">#3Gonly</a> devices that certainly don't support <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a>... <a href="https://infosec.space/tags/GreatFirewallOfAustralia" class="mention hashtag" rel="nofollow noopener" target="_blank">#GreatFirewallOfAustralia</a>

Recent searches

Search options

Administered by:

Server stats:

#volte