<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Goran,<div><br></div><div>Without any exact details, like error messages and commands that you tried we cannot give you much help sadly.</div><div><br></div><div>Please provide all details possible in text format, and I’m sure someone will help.</div><div><br></div><div>Regards,</div><div>Domi<br><br><div><br>2017. szept. 28. dátummal, 11:18 időpontban Popovic Goran <<a href="mailto:Goran.Popovic@kapsch.net">Goran.Popovic@kapsch.net</a>> írta:<br><br></div><blockquote type="cite"><div><span>HI,</span><br><span>My name is Goran, I have femto cell would like test osmo iuh. Installed libosmocore on debian server, but got lot of problems with osmo IuH compiling. Curenlty I am stucked with osmo-sccp library.</span><br><span>Also tried Vagrant IuH image, but there is issue with permisions,</span><br><span>Is there a way to get some help for solving this issues,</span><br><span>Thanks</span><br><span>Goran</span><br><span></span><br><span></span><br><span></span><br><span></span><br><span>-----Original Message-----</span><br><span>From: OpenBSC [<a href="mailto:openbsc-bounces@lists.osmocom.org">mailto:openbsc-bounces@lists.osmocom.org</a>] On Behalf Of <a href="mailto:openbsc-request@lists.osmocom.org">openbsc-request@lists.osmocom.org</a></span><br><span>Sent: Thursday, September 28, 2017 4:36 AM</span><br><span>To: <a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a></span><br><span>Subject: OpenBSC Digest, Vol 35, Issue 30</span><br><span></span><br><span>Send OpenBSC mailing list submissions to</span><br><span> <a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a></span><br><span></span><br><span>To subscribe or unsubscribe via the World Wide Web, visit</span><br><span> <a href="https://lists.osmocom.org/mailman/listinfo/openbsc">https://lists.osmocom.org/mailman/listinfo/openbsc</a></span><br><span>or, via email, send a message with subject or body 'help' to</span><br><span> <a href="mailto:openbsc-request@lists.osmocom.org">openbsc-request@lists.osmocom.org</a></span><br><span></span><br><span>You can reach the person managing the list at</span><br><span> <a href="mailto:openbsc-owner@lists.osmocom.org">openbsc-owner@lists.osmocom.org</a></span><br><span></span><br><span>When replying, please edit your Subject line so it is more specific than "Re: Contents of OpenBSC digest..."</span><br><span></span><br><span></span><br><span>Today's Topics:</span><br><span></span><br><span> 1. Re: branches in openbsc.git (Harald Welte)</span><br><span> 2. Re: randomness of identifiers (Harald Welte)</span><br><span> 3. Re: Retrieve OP from OPc and Ki (Harald Welte)</span><br><span> 4. Re: ctrl interface: GET a variable with parameter (Harald Welte)</span><br><span> 5. Re: Retrieve OP from OPc and Ki (Kathryn Heckman)</span><br><span> 6. Re: Retrieve OP from OPc and Ki (Mychaela Falconia)</span><br><span> 7. Re: Retrieve OP from OPc and Ki (Tomcs?nyi)</span><br><span></span><br><span></span><br><span>----------------------------------------------------------------------</span><br><span></span><br><span>Message: 1</span><br><span>Date: Thu, 28 Sep 2017 07:05:09 +0800</span><br><span>From: Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>></span><br><span>To: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de">nhofmeyr@sysmocom.de</a>></span><br><span>Cc: <a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a></span><br><span>Subject: Re: branches in openbsc.git</span><br><span>Message-ID: <20170927230509.pw4xug7jntrfvts2@nataraja></span><br><span>Content-Type: text/plain; charset=us-ascii</span><br><span></span><br><span>On Thu, Sep 28, 2017 at 12:22:31AM +0200, Neels Hofmeyr wrote:</span><br><blockquote type="cite"><span>another call for anyone aware of important branches on openbsc.git to </span><br></blockquote><blockquote type="cite"><span>please name them, so that they can be migrated to the new repositories.</span><br></blockquote><blockquote type="cite"><span>But foremost, please name them, thanks!</span><br></blockquote><span></span><br><blockquote type="cite"><span>From "my" branches, I can see the following:</span><br></blockquote><span>* laforge/bssgp_fc -> osmo-sgsn</span><br><span>* laforge/gprs-suspend -> osmo-bsc</span><br><span>* laforge/power_control -> osmo-bsc</span><br><span></span><br><span>-- </span><br><span>- Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a></span><br><span>============================================================================</span><br><span>"Privacy in residential applications is a desirable marketing option."</span><br><span> (ETSI EN 300 175-7 Ch. A6)</span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 2</span><br><span>Date: Thu, 28 Sep 2017 07:15:01 +0800</span><br><span>From: Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>></span><br><span>To: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de">nhofmeyr@sysmocom.de</a>></span><br><span>Cc: <a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a></span><br><span>Subject: Re: randomness of identifiers</span><br><span>Message-ID: <20170927231501.zyqrali3onodi4iw@nataraja></span><br><span>Content-Type: text/plain; charset=us-ascii</span><br><span></span><br><span>Hi Neels,</span><br><span></span><br><span>On Wed, Sep 27, 2017 at 06:06:48PM +0200, Neels Hofmeyr wrote:</span><br><blockquote type="cite"><span>On Wed, Sep 27, 2017 at 07:57:43PM +0800, Harald Welte wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>For TMSI allocation, my "cryptographic gut feeling"[tm] is that </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>something like rand() or any other pseudo-random generator of </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>significantly large period is sufficient *if* it is seeded by a </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>non-predictable value. So something like seeding with getrandom() result should be fine?</span><br></blockquote></blockquote><span></span><br><blockquote type="cite"><span>Might also make sense to periodically re-seed from /dev/urandom / </span><br></blockquote><blockquote type="cite"><span>getrandom(), like every 100 TMSIs, or based on a timeout might be </span><br></blockquote><blockquote type="cite"><span>easier to implement.</span><br></blockquote><span></span><br><span>I would try to avoid any predictability here. Having a fixed time interval would be known to an attackers. So if he was somehow able to reduce/exhaust the entropy at the known time for re-seeding, it would be bad.</span><br><span></span><br><span>Similar for "every 100 TMSIs", which is something under control of any attacker as he can control the number of location updates via the public radio interface [to some extent] and thus control the time at whcih re-seeding is done.</span><br><span></span><br><span>Maybe I'm going overboard here, but I think if you want to re-seed, you want to ideally do it at a non-predictable and non-controllable point in time. Like a random time interval ;)</span><br><span></span><br><blockquote type="cite"><blockquote type="cite"><span>For long-term stable key (Ki/Op) generation for provisioning SIM </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>cards + populating a HLR, I would certainly opt for using stronger </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>randomness sources. However, I don't think we actually implement </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>that anywhere, do we?</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>what does openssh use for public/private keypair generation?</span><br></blockquote><span></span><br><span>I'm not sure you can compare the requirements for generation of RSA public/private keys with those for generation of symmetric keys. You can find different recommendations in the literature. But I guess that's mainly due to the fact that people usually assume you have long-term stable public/private keys and short-lived symmetric session keys. In our case, it's long-lived symmetric keys.</span><br><span></span><br><span>But as indicated, I think our focus is to find a proper solution for generation of TMSIs and for random numbers used in authentication challenges. K/OPc pair generation is not supported in current Osmocom tools anyway, as we presume the SIM cards already have sufficiently random key material and those keys are entered into the HLR.</span><br><span></span><br><span>Regards,</span><br><span> Harald</span><br><span></span><br><span>-- </span><br><span>- Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a></span><br><span>============================================================================</span><br><span>"Privacy in residential applications is a desirable marketing option."</span><br><span> (ETSI EN 300 175-7 Ch. A6)</span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 3</span><br><span>Date: Thu, 28 Sep 2017 06:52:28 +0800</span><br><span>From: Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>></span><br><span>To: Kathryn Heckman <<a href="mailto:exuberant.kathryn.heckman@gmail.com">exuberant.kathryn.heckman@gmail.com</a>></span><br><span>Cc: "<a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a>" <<a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a>></span><br><span>Subject: Re: Retrieve OP from OPc and Ki</span><br><span>Message-ID: <20170927225228.u4udbuhk2fyebrl5@nataraja></span><br><span>Content-Type: text/plain; charset=us-ascii</span><br><span></span><br><span>Hi Kathryn,</span><br><span></span><br><span>On Wed, Sep 27, 2017 at 05:37:36PM -0400, Kathryn Heckman wrote:</span><br><blockquote type="cite"><span>Is there any way to retrieve the value of OP from OPc and Ki?</span><br></blockquote><span></span><br><span>No, that defeats the entire purpose of having card-individual OPc values.</span><br><span></span><br><span>If you could just revert that operation, there would be no [security] advantage of card-individual OPc values over a global OP value, and hence that entire option could be dropped from the specifications altogether.</span><br><span></span><br><span>Regards,</span><br><span> Harald</span><br><span>-- </span><br><span>- Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a></span><br><span>============================================================================</span><br><span>"Privacy in residential applications is a desirable marketing option."</span><br><span> (ETSI EN 300 175-7 Ch. A6)</span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 4</span><br><span>Date: Thu, 28 Sep 2017 06:50:03 +0800</span><br><span>From: Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>></span><br><span>To: Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de">nhofmeyr@sysmocom.de</a>></span><br><span>Cc: Holger Freyther <<a href="mailto:holger@freyther.de">holger@freyther.de</a>>, <a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a></span><br><span>Subject: Re: ctrl interface: GET a variable with parameter</span><br><span>Message-ID: <20170927225003.ix4qgulake4gugyu@nataraja></span><br><span>Content-Type: text/plain; charset="us-ascii"</span><br><span></span><br><span>Hi Neels,</span><br><span></span><br><span>On Wed, Sep 27, 2017 at 05:27:38PM +0200, Neels Hofmeyr wrote:</span><br><blockquote type="cite"><span>Also we do have a concept of nesting CTRL nodes separated by dots in </span><br></blockquote><blockquote type="cite"><span>the variable name, looking at bsc_ctrl_node_lookup() and fsm_ctrl_node_lookup().</span><br></blockquote><span></span><br><span>correct.</span><br><span></span><br><blockquote type="cite"><span>I notice though that we do still have open doors for a lot of nonsense </span><br></blockquote><blockquote type="cite"><span>being sent to it without proper validation or error messages.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> GET 42 existing-variable.trailing.names.ignored more nonsense </span><br></blockquote><blockquote type="cite"><span>following being ignored</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>in effect is identical to:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> GET 42 existing-variable</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>So we should probably enforce that there is no ignored nonsense...</span><br></blockquote><span></span><br><span>I agree.</span><br><span></span><br><blockquote type="cite"><span>Should we also enforce a numeric command ID?</span><br></blockquote><span></span><br><span>I'm not following here. Where would that numeric command ID comning from?</span><br><span></span><br><blockquote type="cite"><span> GET currently-any-id-is-possible-even-\t-\n-is-accepted my-command</span><br></blockquote><span></span><br><span>this is also not intended, I'm quite sure.</span><br><span></span><br><blockquote type="cite"><span>Going back to the OsmoHLR CTRL commands -- they are implemented in a </span><br></blockquote><blockquote type="cite"><span>way that doesn't match the CTRL interface ways. Let's collapse them.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> SET enable-ps <IMSI></span><br></blockquote><blockquote type="cite"><span> SET disable-ps <IMSI></span><br></blockquote><blockquote type="cite"><span> SET status-ps <IMSI></span><br></blockquote><span></span><br><span>indeed, this is not proper.</span><br><span></span><br><blockquote type="cite"><span> SET subscriber.by-imsi.123456789098765.ps-enabled 1</span><br></blockquote><blockquote type="cite"><span> SET subscriber.by-imsi.123456789098765.ps-enabled 0</span><br></blockquote><blockquote type="cite"><span> GET subscriber.by-imsi.123456789098765.ps-enabled</span><br></blockquote><span></span><br><span>makes a lot of sense to me.</span><br><span></span><br><blockquote type="cite"><span>We can also expand this later to things like</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> GET subscriber.by-imsi.123456789098765.status</span><br></blockquote><blockquote type="cite"><span> SET subscriber.by-imsi.123456789098765.msisdn 2345</span><br></blockquote><blockquote type="cite"><span> GET subscriber.by-msisdn.2342.status</span><br></blockquote><blockquote type="cite"><span> SET subscriber.by-msisdn.2342.ps-enabled 0</span><br></blockquote><blockquote type="cite"><span> GET subscriber.by-imei.987654321234565.imsi</span><br></blockquote><span></span><br><span>looks good!</span><br><span></span><br><blockquote type="cite"><span>We could leave the enable-ps, disable-ps, status-ps commands in place </span><br></blockquote><blockquote type="cite"><span>in case anyone is using it yet. I assume no-one is though.</span><br></blockquote><span></span><br><span>I don't think we need to keep compatibility at this point.</span><br><span></span><br><span>-- </span><br><span>- Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a></span><br><span>============================================================================</span><br><span>"Privacy in residential applications is a desirable marketing option."</span><br><span> (ETSI EN 300 175-7 Ch. A6)</span><br><span>-------------- next part --------------</span><br><span>A non-text attachment was scrubbed...</span><br><span>Name: signature.asc</span><br><span>Type: application/pgp-signature</span><br><span>Size: 833 bytes</span><br><span>Desc: not available</span><br><span>URL: <<a href="http://lists.osmocom.org/pipermail/openbsc/attachments/20170928/d568b5f9/attachment-0001.bin">http://lists.osmocom.org/pipermail/openbsc/attachments/20170928/d568b5f9/attachment-0001.bin</a>></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 5</span><br><span>Date: Wed, 27 Sep 2017 21:46:27 -0400</span><br><span>From: Kathryn Heckman <<a href="mailto:exuberant.kathryn.heckman@gmail.com">exuberant.kathryn.heckman@gmail.com</a>></span><br><span>To: Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>></span><br><span>Cc: "<a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a>" <<a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a>></span><br><span>Subject: Re: Retrieve OP from OPc and Ki</span><br><span>Message-ID:</span><br><span> <<a href="mailto:CAHmN-qT=5x=5XZnwhjYBSByw2ZJpWtCRMiWHu3iWxDysBQT6cA@mail.gmail.com">CAHmN-qT=5x=5XZnwhjYBSByw2ZJpWtCRMiWHu3iWxDysBQT6cA@mail.gmail.com</a>></span><br><span>Content-Type: text/plain; charset="utf-8"</span><br><span></span><br><span>I really appreciate your quick replies.</span><br><span></span><br><span>I have a USIM that I wanted to program. However, I am getting the runtime error for exceeding the number of attempts to enter the ADM1 key. Is there any fix for it?</span><br><span></span><br><span>--</span><br><span>Kathryn</span><br><span></span><br><span>On Wed, Sep 27, 2017 at 6:52 PM, Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> wrote:</span><br><span></span><br><blockquote type="cite"><span>Hi Kathryn,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Wed, Sep 27, 2017 at 05:37:36PM -0400, Kathryn Heckman wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Is there any way to retrieve the value of OP from OPc and Ki?</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>No, that defeats the entire purpose of having card-individual OPc </span><br></blockquote><blockquote type="cite"><span>values.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>If you could just revert that operation, there would be no [security] </span><br></blockquote><blockquote type="cite"><span>advantage of card-individual OPc values over a global OP value, and </span><br></blockquote><blockquote type="cite"><span>hence that entire option could be dropped from the specifications </span><br></blockquote><blockquote type="cite"><span>altogether.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Regards,</span><br></blockquote><blockquote type="cite"><span> Harald</span><br></blockquote><blockquote type="cite"><span>--</span><br></blockquote><blockquote type="cite"><span>- Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>></span><br></blockquote><blockquote type="cite"><span><a href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a></span><br></blockquote><blockquote type="cite"><span>============================================================</span><br></blockquote><blockquote type="cite"><span>================</span><br></blockquote><blockquote type="cite"><span>"Privacy in residential applications is a desirable marketing option."</span><br></blockquote><blockquote type="cite"><span> (ETSI EN 300 175-7 Ch.</span><br></blockquote><blockquote type="cite"><span>A6)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span>-------------- next part --------------</span><br><span>An HTML attachment was scrubbed...</span><br><span>URL: <<a href="http://lists.osmocom.org/pipermail/openbsc/attachments/20170927/620a2963/attachment-0001.html">http://lists.osmocom.org/pipermail/openbsc/attachments/20170927/620a2963/attachment-0001.html</a>></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 6</span><br><span>Date: Wed, 27 Sep 2017 18:04:35 -0800</span><br><span>From: Mychaela Falconia <<a href="mailto:mychaela.falconia@gmail.com">mychaela.falconia@gmail.com</a>></span><br><span>To: Kathryn Heckman <<a href="mailto:exuberant.kathryn.heckman@gmail.com">exuberant.kathryn.heckman@gmail.com</a>></span><br><span>Cc: openbsc <<a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a>></span><br><span>Subject: Re: Retrieve OP from OPc and Ki</span><br><span>Message-ID:</span><br><span> <<a href="mailto:CA+uuBqbtTfsrADC-ENCfGt2RY=XYUYN0d466=ZR3Mrn_up-L8A@mail.gmail.com">CA+uuBqbtTfsrADC-ENCfGt2RY=XYUYN0d466=ZR3Mrn_up-L8A@mail.gmail.com</a>></span><br><span>Content-Type: text/plain; charset="UTF-8"</span><br><span></span><br><span>On 9/27/17, Kathryn Heckman <<a href="mailto:exuberant.kathryn.heckman@gmail.com">exuberant.kathryn.heckman@gmail.com</a>> wrote:</span><br><blockquote type="cite"><span>I have a USIM that I wanted to program. However, I am getting the </span><br></blockquote><blockquote type="cite"><span>runtime error for exceeding the number of attempts to enter the ADM1 </span><br></blockquote><blockquote type="cite"><span>key. Is there any fix for it?</span><br></blockquote><span></span><br><span>Someone please correct me if I am wrong, but I would assume that having exceeded the number of attempts to enter the ADM1 key means that the USIM is bricked beyond recovery.</span><br><span></span><br><span>But the sysmoUSIM cards sold at <a href="http://shop.sysmocom.de">shop.sysmocom.de</a> are fairly inexpensive for a pack of 10, so a bricked (U)SIM shouldn't be too big of a tragedy - or is there another dimension to this problem which I am missing?</span><br><span></span><br><span>If you are anywhere near local to me (California, USA) I could give you one of my sysmoUSIM cards, but I am guessing it probably won't help you as I bought the cheaper version without the ADM1 keys - for my application (production testing of my GSM MS hardware) it doesn't matter what the programming of the (U)SIM happens to be.</span><br><span></span><br><span>M~</span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 7</span><br><span>Date: Thu, 28 Sep 2017 04:35:24 +0200 (CEST)</span><br><span>From: Tomcs?nyi, Domonkos <<a href="mailto:domi@tomcsanyi.net">domi@tomcsanyi.net</a>></span><br><span>To: Mychaela Falconia <<a href="mailto:mychaela.falconia@gmail.com">mychaela.falconia@gmail.com</a>></span><br><span>Cc: Kathryn Heckman <<a href="mailto:exuberant.kathryn.heckman@gmail.com">exuberant.kathryn.heckman@gmail.com</a>>, openbsc</span><br><span> <<a href="mailto:openbsc@lists.osmocom.org">openbsc@lists.osmocom.org</a>></span><br><span>Subject: Re: Retrieve OP from OPc and Ki</span><br><span>Message-ID: <<a href="mailto:1A1DD58D-617B-4FBE-B363-21A25EBCFA83@tomcsanyi.net">1A1DD58D-617B-4FBE-B363-21A25EBCFA83@tomcsanyi.net</a>></span><br><span>Content-Type: text/plain; charset="utf-8"</span><br><span></span><br><span>Hi Kathryn and Mychaela,</span><br><span></span><br><span>2017. szept. 28. d?tummal, 4:04 id?pontban Mychaela Falconia <<a href="mailto:mychaela.falconia@gmail.com">mychaela.falconia@gmail.com</a>> ?rta:</span><br><blockquote type="cite"><span>Someone please correct me if I am wrong, but I would assume that </span><br></blockquote><blockquote type="cite"><span>having exceeded the number of attempts to enter the ADM1 key means </span><br></blockquote><blockquote type="cite"><span>that the USIM is bricked beyond recovery.</span><br></blockquote><span></span><br><span>This is my understanding as well.</span><br><span></span><br><span>Cheers,</span><br><span></span><br><span>Domi</span><br><span>-------------- next part --------------</span><br><span>An HTML attachment was scrubbed...</span><br><span>URL: <<a href="http://lists.osmocom.org/pipermail/openbsc/attachments/20170928/c99fe291/attachment.html">http://lists.osmocom.org/pipermail/openbsc/attachments/20170928/c99fe291/attachment.html</a>></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Subject: Digest Footer</span><br><span></span><br><span>_______________________________________________</span><br><span>OpenBSC mailing list</span><br><span><a href="mailto:OpenBSC@lists.osmocom.org">OpenBSC@lists.osmocom.org</a></span><br><span><a href="https://lists.osmocom.org/mailman/listinfo/openbsc">https://lists.osmocom.org/mailman/listinfo/openbsc</a></span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>End of OpenBSC Digest, Vol 35, Issue 30</span><br><span>***************************************</span><br><span></span><br><span></span><br><span></span><br><span>The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.</span><br><span></span><br></div></blockquote></div></body></html>