freedom-privacy-security-issues: Improve OsmocomBB's description

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>

1 files changed, 2 insertions, 1 deletions

diff --git a/freedom-privacy-security-issues.php b/freedom-privacy-security-issues.php
index dbf1ebf..b7364dc 100644
--- a/freedom-privacy-security-issues.php
+++ b/freedom-privacy-security-issues.php
@@ -60,7 +60,8 @@
 			<p>
 				<a href="images/freedom-privacy-security-issues/bad-modem-isolation.png" data-lightbox="current-situation" data-title="Bad modem isolation"><img src="images/freedom-privacy-security-issues/bad-modem-isolation.png" alt="Bad modem isolation" style="width: 250px; float: left;"/></a>
 				The modem system on telephony-enabled mobile devices is always proprietary.
-				While <a href="//bb.osmocom.org/">OsmocomBB</a>, a free software GSM stack exists, it only runs on old feature phones, currently requires a host computer to operate and is not certified to run on public networks.
+				While <a href="//bb.osmocom.org/">OsmocomBB</a>, a free software GSM stack exists, it only runs on some old feature phones, or on the modem used in the Openmoko phones.
+				It currently requires a host computer to operate and is not certified to run on public networks.
 				Despite this situation, the modem remains a crucial part for privacy/security: it is nearly always connected to the GSM network, allowing for <a href="//www.gnu.org/philosophy/malware-mobiles.html">remote control</a>.
 				The modem can be more or less damaging to privacy/security depending on what hardware it has access to and can control.
 				That is to say, how isolated it is from the rest of the device.<br /><br />