Open Source Telephony
 help / color / mirror / Atom feed
From: James Prestwood <james.prestwood@linux.intel.com>
To: ofono@ofono.org
Subject: Proposal: New SimAuth interface
Date: Wed, 23 Aug 2017 15:40:21 -0700	[thread overview]
Message-ID: <eca28f35-c527-b86c-b641-96f96d640cfd@linux.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]

Hello,

     The IWD project now has a need for SIM card access in order to 
authenticate to EAP-SIM/AKA WiFi networks, and will be using ofono for 
this functionality. In order to do this, the GSM/3G "authenticate" 
algorithm needs to be run on the (U)SIM. For this I am proposing a new 
interface: "org.ofono.SimAuth". I do have a few questions about what 
method(s)/interfaces would be preferred. Since 2G/3G take different 
inputs/outputs there are few possibilities:

1. Two different methods on org.ofono.SimAuth:

     AuthenticateSim()

         Input: "ay" RAND

         Output: "ay" SRES, "ay" KC

     AuthenticateUSim()

         Input: "ay" RAND, "ay" AUTN

         Output: "ay" RES, "ay" IK, "ay" CK, "ay" AUTS

2. One method on org.ofono.SimAuth, with more complex arguments e.g.

     Authenticate()

         Input: "s" type, a{ay} args

         Output: a{ay}

     This would return take in and return the correct arguments for 
2G/3G based on the "type" argument.

3. Separate interfaces for SIM/USIM (e.g. org.ofono.SimAuth and 
org.ofono.USimAuth). This would also allow the client to see if either 
SIM or USIM are supported before making any method calls.

If anyone has input on what would option would be preferred, or maybe a 
different way of doing it, that would be great!

Thanks,

James


                 reply	other threads:[~2017-08-23 22:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eca28f35-c527-b86c-b641-96f96d640cfd@linux.intel.com \
    --to=james.prestwood@linux.intel.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox