Helvede

0 posts0 participants0 posts today

Kevin Karhan :verified:[<a href="https://infosec.space/tags/TLDR" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#CALLS</a>!]<a href="https://infosec.space/tags/DearVendors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DearVendors</a> of <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a>-<a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tablets</a>:Off all the <a href="https://infosec.space/tags/Functions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Functions</a> you can put into a <a href="https://infosec.space/tags/Specifications" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Website</a>:DOES YOUR TABLET [with <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#4G</a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#5G</a> / …) SUPPORT MAKE PHONE CALLS?<ul><li>NOT "It can run <a href="https://infosec.space/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatsApp</a>" (or whatever shitty <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCSS</a> for <a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#CSD</a> / <a href="https://infosec.space/tags/HSCSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HSCSD</a> / <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2G</a> / <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#3G</a> /...</li><li>But DOES IT SUPPORT <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GSM</a>-<a href="https://infosec.space/tags/Calls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Calls</a> (and/or <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#Turkey</a>) have <a href="https://infosec.space/tags/ImportRestrictions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ImportRestrictions</a> re: <a href="https://infosec.space/tags/MobileDevices" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MobileDevices</a>, so having more than 1 <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#Baseband</a> and <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ROM</a> support <a href="https://infosec.space/tags/PhoneCalls" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Tablet</a> manufacturers allow to <a href="https://infosec.space/tags/search" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#search</a> or <a href="https://infosec.space/tags/filter" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#HMD</a> (aka. <a href="https://infosec.space/tags/Nokia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nokia</a>) who literally copy the <a href="https://infosec.space/tags/Safety" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Safety</a> & <a href="https://infosec.space/tags/Useage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Useage</a> information for all <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Smartphones</a> and <a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">read on page 34</a> that for any "<a href="https://infosec.space/tags/telephony" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#eSIM</a> that is in a <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#SIM</a> just to recieve the occasional call because <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechIlliterates</a> can't be assed to send an <a href="https://infosec.space/tags/eMail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eMail</a> or learn <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#waterproof</a> <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Rant</a> <a href="https://infosec.space/tags/TechSupport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechSupport</a> <a href="https://infosec.space/tags/Technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Technology</a> <a href="https://infosec.space/tags/Support" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Support</a> <a href="https://infosec.space/tags/Sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sysadmin</a> <a href="https://infosec.space/tags/Procurement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Procurement</a> <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IT</a> <a href="https://infosec.space/tags/SpecSheet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SpecSheet</a> <a href="https://infosec.space/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tech</a>

Einstein^VaderbiltOn Mobile Phone Security <a href="https://www.kicksecure.com/wiki/Mobile_Phone_Security" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.kicksecure.com/wiki/Mobile_Phone_Security</a> <a href="https://defcon.social/tags/SS7" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SS7</a> and <a href="https://defcon.social/tags/baseband" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#baseband</a> <a href="https://defcon.social/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vulnerabilities</a> What about <a href="https://defcon.social/tags/mobian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mobian</a> hardening on a <a href="https://defcon.social/tags/MechaComet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MechaComet</a> with a cellular hat? Then there's only carrier protocol weaknesses... If ISPs use microwave relays (the hated 'air' - remember Max Headroom) and NSA access points, is domestic broadband really secure either? But the cable or fiber doesn't have 'carrier' vulns. <a href="https://www.kicksecure.com/wiki/Router_and_Local_Area_Network_Security" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.kicksecure.com/wiki/Router_and_Local_Area_Network_Security</a><a href="https://defcon.social/tags/kicksecure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kicksecure</a> <a href="https://defcon.social/tags/whonix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#whonix</a> <a href="https://defcon.social/tags/docs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#docs</a> <a href="https://defcon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a>-misc

Kevin Karhan :verified:A <a href="https://infosec.space/tags/PSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PSA</a> for anyone living, staying, entering or even travelling to/from <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Australia</a>:Apparently, <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Australia</a> <a href="https://www.youtube.com/watch?v=RPlTz-3estM" rel="nofollow noopener noreferrer" target="_blank">decided to mandate</a> it's <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GSM</a> systems to be shutdown because some <a href="https://infosec.space/tags/GalaxyBrainChair" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GalaxyBrainChair</a> wanted to yeet <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2G</a> & <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#3G</a> and demand everything to use <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#4G</a> & <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#5G</a> when in fact <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VoLTE</a> support is spotty at best and <a href="https://infosec.space/tags/EmergencyCalling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EmergencyCalling</a> oftentimes is explicitly hardcoded to not use <a href="https://infosec.space/tags/WIFIcalling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WIFIcalling</a> or VoLTE as providing <a href="https://infosec.space/tags/triangulation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#triangulation</a> and <a href="https://infosec.space/tags/LocationData" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LocationData</a> via <a href="https://infosec.space/tags/SS7" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SS7</a> is a desired feature when someone calls EMS, Fire Dept or the Police for help... <ul><li>So essentially <a href="https://infosec.space/tags/tourists" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tourists</a> and anyone who hasn't an explicitly fully VoLTE-functional device they tested and verified to also do <a href="https://infosec.space/tags/EmergencyCalls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EmergencyCalls</a> via VoLTE are fecked with no reception when they need it the most!</li><li>This WILL KILL PEOPLE!!!</li></ul> As much as we want to bitch about <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GSM</a> & <a href="https://infosec.space/tags/GPRS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPRS</a> / <a href="https://infosec.space/tags/UMTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UMTS</a> being <a href="https://infosec.space/tags/outdated" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#outdated</a> and <a href="https://infosec.space/tags/inefficient" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#inefficient</a>, there are reasons to at least keep 2G available - ranging from lower power consumption to higher resilience in emergency situations.<ul><li><a href="https://infosec.space/tags/NewZealand" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NewZealand</a> for example does shutdown non-<a href="https://infosec.space/tags/EmergencyCalls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EmergencyCalls</a> during severe <a href="https://infosec.space/tags/Earthquakes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Earthquakes</a> so that people trapped and/or in need of urgent assistance can get through to dispatch operators and everyone else has to get in line and take a number aka. use <a href="https://infosec.space/tags/SMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SMS</a> or if existing <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a> to say "I'm fine!"... </li><li>If the Ozzies really need that juicy <a href="https://infosec.space/tags/UHF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UHF</a> <a href="https://infosec.space/tags/SubGHz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SubGHz</a> <a href="https://infosec.space/tags/Spectrum" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Spectrum</a> it's totally feasible to instead change the <a href="https://infosec.space/tags/allocations" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#allocations</a> and reconfigure <a href="https://infosec.space/tags/CellularNetworks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CellularNetworks</a> to use lesser bandwith for 2G (i.e. only keeping the absolute mininum of channels available for any service) and thus clear up space...</li></ul>And to add insult to injury, Australia <a href="https://www.youtube.com/watch?v=RPlTz-3estM&t=207s" rel="nofollow noopener noreferrer" target="_blank">passed</a> a <a href="https://infosec.space/tags/NorthKorea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NorthKorea</a>|n-alike <a href="https://infosec.space/tags/CellPhone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CellPhone</a> <a href="https://infosec.space/tags/ImportBan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ImportBan</a> for any device that doesn't do i.e. the bespoke proprietary garbage that i.e. <a href="https://infosec.space/tags/Telstra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Telstra</a>, <a href="https://infosec.space/tags/Vodafone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vodafone</a> and <a href="https://infosec.space/tags/Optus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Optus</a> do with the <a href="https://infosec.space/tags/baseband" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#baseband</a> modems of their <a href="https://infosec.space/tags/branded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#branded</a> devices... Seriously, which <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechIlliterate</a> dickhead decided it's a good idea to do that <a href="https://infosec.space/tags/3Gshutdown" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#3Gshutdown</a> in Australia without even a basic 2G network up and running at all? <ul><li>At least <a href="https://infosec.space/tags/Switzerland" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Switzerland</a> [AFAIK] still has <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#3G</a> up and running (tho it would've been wiser to do it like <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Germany</a> and keep <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2G</a> as emergency fallback with it's functions like <a href="https://infosec.space/tags/CellBroadcast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CellBroadcast</a>....</li></ul>

nt!PopGetDope :coolcat::twitter: finally seems to be flat-lining, trying out this new mastodon thing...<a href="https://infosec.exchange/tags/introduction" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#introduction</a>, for peeps I've not met prior via my bird app handle <a href="https://infosec.exchange/@ntpopgetdope" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ntpopgetdope</a>. I'm a vulnerability researcher that's worked in the industry professionally for >4yrsMy background stems from an obsession with <a href="https://infosec.exchange/tags/windowsinternals" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#windowsinternals</a> & the vastly underrated 'HAL.dll'. These days I'm into baseband vuln research working on obscure hardware, architectures & attacks. Love chatting about all things: <a href="https://infosec.exchange/tags/fpga" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fpga</a> <a href="https://infosec.exchange/tags/uefi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#uefi</a> <a href="https://infosec.exchange/tags/baseband" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#baseband</a> <a href="https://infosec.exchange/tags/faultinjection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#faultinjection</a> <a href="https://infosec.exchange/tags/openhardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openhardware</a> <a href="https://infosec.exchange/tags/embeddedelectronics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embeddedelectronics</a> <a href="https://infosec.exchange/tags/pcbdesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pcbdesign</a> and <a href="https://infosec.exchange/tags/cats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cats</a> !Currently with the @InterruptLabs crew, a boutique vulnerability research & exploit development firm in the UK.

theguyHello World,in light of how everyone else is introducing themselves, here is my <a href="https://infosec.exchange/tags/introduction" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#introduction</a>. My main area of interest is low-level hardware and software security. I really enjoy <a href="https://infosec.exchange/tags/reversing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reversing</a> and discovering and learning new things in general.I'm currently researching the security of <a href="https://infosec.exchange/tags/baseband" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#baseband</a> processors, and when I have free time that I don't spend away from the keyboard, I enjoy participating in <a href="https://infosec.exchange/tags/CTF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CTF</a> competitions.

bojkotiMalbonaI’ve heard that the <a href="https://infosec.exchange/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GSM</a> standard enables carriers to push <a href="https://infosec.exchange/tags/baseband" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#baseband</a> updates to users’ devices, and that devices simply trust all towers to have this control. So my theory is that the carrier pushed an update that bricked the GSM modem. Is that possible? I heard from an unreliable source that it’s no longer possible for towers to push updates. Is there a more likely scenario?

Recent searches

Search options

Administered by:

Server stats:

#baseband