Social 📸 Photography

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/@sysmocom" class="u-url mention" rel="nofollow noopener" target="_blank">@sysmocom</a> granted, I do trust the GSMA more than Beijing, but that's more due to the fact that conflicting desires if GSMA members tend to be harder to steer.<ul><li>Similarly GAFAMs conflicting ideas prevented them from enshittifying Linux.</li></ul>Still, I think that end users and device integrators should have full control over the certificates and root of trust, including the ability to add alternative Root-CAs and even removing GSMA's Root-CA (similar to how "Secure Boot" should've been done instead of <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a>!) <ul><li>Whether it would be a wise decision to yeet the GSMA cert is a different story, but given what I know in terms of "security" I'd certainly not trust <a href="https://infosec.space/tags/Bundesdruckerei" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bundesdruckerei</a> and it's subsidiaries to be competent.</li></ul>Certainly being able to exercise full control would make a lot of <a href="https://infosec.space/tags/osmocom" class="mention hashtag" rel="nofollow noopener" target="_blank">#osmocom</a>'s development easier.

PhoshAs part of or work on <a href="https://fosstodon.org/tags/Cellbroadcast" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cellbroadcast</a> we've documented our current test setup: <a href="https://codeberg.org/Phosh/gsm-cell-testing" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/Phosh/gsm-cell-testing</a> using <a href="https://fosstodon.org/tags/osmocom" class="mention hashtag" rel="nofollow noopener" target="_blank">#osmocom</a> for the mobile network parts and <a href="https://fosstodon.org/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a> for deploying <a href="https://fosstodon.org/tags/ModemManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#ModemManager</a> on the devices, performing the tests and checking the results. Thanks to <a href="https://mastodon.xyz/@NGIZero" class="u-url mention" rel="nofollow noopener" target="_blank">@NGIZero</a> for supporting our work on this.<a href="https://fosstodon.org/tags/phosh" class="mention hashtag" rel="nofollow noopener" target="_blank">#phosh</a> <a href="https://fosstodon.org/tags/LinuxMobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxMobile</a>

Guido GüntherSuccessfully tested receiving <a href="https://ruhr.social/tags/cellbroadcast" class="mention hashtag" rel="nofollow noopener" target="_blank">#cellbroadcast</a> messages on the <a href="https://ruhr.social/tags/PinePhone" class="mention hashtag" rel="nofollow noopener" target="_blank">#PinePhone</a> as well:# _build/test/mmcbmmonitor [/org/freedesktop/ModemManager1/CBM/0] new cbm: received 4371: Hallo, this is a CBS test messageSo hopefully all devices supporting `+CSCB` on an AT port should now be able to show these messages in <a href="https://fosstodon.org/@phosh" class="u-url mention" rel="nofollow noopener" target="_blank">@phosh</a> (if the MR makes it into the next <a href="https://ruhr.social/tags/ModemManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#ModemManager</a> release).The <a href="https://ruhr.social/tags/osmocom" class="mention hashtag" rel="nofollow noopener" target="_blank">#osmocom</a> stack is such a great help for testing these things.Thanks to <a href="https://mastodon.xyz/@NGIZero" class="u-url mention" rel="nofollow noopener" target="_blank">@NGIZero</a> for supporting this.<a href="https://ruhr.social/tags/LinuxMobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxMobile</a>

charlySpionsuche.<a href="https://chaos.social/@cbase" class="u-url mention" rel="nofollow noopener" target="_blank">@cbase</a> <a href="https://chaos.social/tags/cbase" class="mention hashtag" rel="nofollow noopener" target="_blank">#cbase</a> <a href="https://chaos.social/tags/37c3" class="mention hashtag" rel="nofollow noopener" target="_blank">#37c3</a> <a href="https://chaos.social/tags/osmocom" class="mention hashtag" rel="nofollow noopener" target="_blank">#osmocom</a> <a href="https://chaos.social/@LaF0rge" class="u-url mention" rel="nofollow noopener" target="_blank">@LaF0rge</a>

Kevin Karhan :verified:<a href="https://chaos.social/@manawyrm" class="u-url mention" rel="nofollow noopener" target="_blank">@manawyrm</a> <a href="https://glauca.space/@q" class="u-url mention" rel="nofollow noopener" target="_blank">@q</a> let me guess: Those were used for <a href="https://mstdn.social/tags/Osmocom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Osmocom</a> / <a href="https://mstdn.social/tags/OpenGSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenGSM</a> devs that tended to use <a href="https://mstdn.social/tags/ChaosCommunicationCongress" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChaosCommunicationCongress</a> as testing grounds for their Software...Sadly the bands have been allocated and AFAIK all regular multi-band <a href="https://mstdn.social/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GSM</a> bands have veen allocated and the only Sub - 700MHz bands unused are extremely uncommon (GSM-400 for example) and <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> won't issue even experimental useage licenses for events in said bands...

charly<a href="https://chaos.social/tags/osmocom" class="mention hashtag" rel="nofollow noopener" target="_blank">#osmocom</a>

Recent searches

Search options

Administered by:

Server stats:

#osmocom