E_CHANNEL = 122;
> > this.REQUEST_SIM_ACCESS_CHANNEL = 123;
> >
> > any suggestions?
> >
> > Best Regards,
> > S.H. Kao
> > Software Engineer, Mozilla Taiwan
> >
> > - Original Message -
> > From: "Shao-Hang Kao"
> > To: de
0 Ext.303
Mobile:+886-952-391521
- Original Message -
> From: "Masashi Honma"
> To: "Shao-Hang Kao"
> Cc: mvi...@quicinc.com, "dev-b2g"
> Sent: Wednesday, December 18, 2013 8:14:57 PM
> Subject: Re: [b2g] EAP-SIM Architecture proposal
>
&
sorry for previous double post.
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
> From: "Shao-Hang Kao"
> To: dev-b2g@lists.mozilla.org
> Sent: Monday, September 30, 2013 6:26:24 PM
> Subject: Re: [b2g] EAP-SIM Architecture proposal
>
> Just tried SIM_ACCESS_CHANNEL on Inari and looks like it's not supported:
>
> I/Gecko ( 369): -*- RadioI
> From: "Shao-Hang Kao"
> To: dev-b2g@lists.mozilla.org
> Sent: Monday, September 30, 2013 6:26:24 PM
> Subject: Re: [b2g] EAP-SIM Architecture proposal
>
> Just tried SIM_ACCESS_CHANNEL on Inari and looks like it's not supported:
>
> I/Gecko ( 369): -*- Rad
?
Best Regards,
S.H. Kao
Software Engineer, Mozilla Taiwan
- Original Message -
From: "Shao-Hang Kao"
To: dev-b2g@lists.mozilla.org
Sent: Monday, September 30, 2013 6:26:24 PM
Subject: Re: [b2g] EAP-SIM Architecture proposal
Just tried SIM_ACCESS_CHANNEL on Inari and looks lik
may be almost impossible to implement EAP-SIM without a patch of
wpa_supplicant.
Best Regards,
S.H. Kao
Software Engineer, Mozilla Taiwan
- Original Message -
From: s...@mozilla.com
To: dev-b2g@lists.mozilla.org
Sent: Friday, September 27, 2013 5:32:10 PM
Subject: Re: [b2g] EAP-SIM Architect
Hi,
I'm proposing an alternative architecture without maintaining a patch over
wpa_supplicant.
Using a similar architecture to the project seek-for-android[1], we need a pcsc
daemon (pcscd) from pcsc-lite running on B2G as a fake card reader so
wpa_supplicant can communicate with it when EAP-S
e:+886-952-391521
>
>
> - 原始郵件 -
> > 寄件者: "Thomas Ho"
> > 收件者: "Vincent Chang"
> > 副本: "Jonas Sicking" , "Kyle Machulis" <
> kmachu...@mozilla.com>, "Blake Kaplan" ,
> > "Blake Kaplan"
Chang"
> 副本: "Jonas Sicking" , "Kyle Machulis"
> , "Blake Kaplan" ,
> "Blake Kaplan" , "Michael Vines" ,
> "Dimi Lee" , "dev-b2g"
>
> 寄件備份: 2013 8 月 15 星期四 下午 3:20:07
> 主旨: Re: [b2g] EAP-SIM Architecture prop
Vincent and All,
It does seem that Android (Google) doesn't natively support EAP-SIM, but
there are clients available to have EAP-SIM enabled. Vincent, you may
want to try to understand how CHT in Taiwan provides EAP-SIM support to
Samsung, HTC and other brand Android phones. Thank you very mu
AOSP seems not support this feature yet, see the link below.
https://code.google.com/p/android/issues/detail?id=9329&cnum=500&cstart=1231
Many Thanks,
Vincent Chang,
Software Engineer of Mozilla Taiwan
2013/8/15 Michael Vines
> Yes we could certainly consider patching the wpa_supplicant distr
Yes we could certainly consider patching the wpa_supplicant distributed on
codeaurora if necessary. I'm unfamiliar with this feature though, do you
know if/how Android supports it?
Thanks,
Michael
On 8/14/13 10:31 AM, "Blake Kaplan" wrote:
>On Wed, Aug 14, 2013 at 8:55 AM, Vincent Chang wr
On Wed, Aug 14, 2013 at 8:55 AM, Vincent Chang wrote:
> Does it make sense that partners modify their own wpa_supplicant and obtain
> the necessary SIM information
> from card reader driver or directly from radio driver ? In this cause, we
> don't need to modify wpa_supplicant or
> create a new wo
Hi Blake,
Does it make sense that partners modify their own wpa_supplicant and obtain
the necessary SIM information
from card reader driver or directly from radio driver ? In this cause, we
don't need to modify wpa_supplicant or
create a new worker thread to listen and wait there. In this case, we
Hello everybody,
I have to admit that I don't know very much about EAP-SIM, but
maintaining a patch on top of wpa_supplicant seems like a really bad
idea. Even going through Qualcomm is a risky proposition because
actual OEMs have a tendency of shipping their own versions of various
libraries/prog
gt; - Original Message -
> From: "Masashi Honma"
> To: "Dimi Lee"
> Cc: "Jonas Sicking" , "Kyle Machulis"
> , "dev-b2g"
> Sent: Friday, August 2, 2013 10:12:49 PM
> Subject: Re: [b2g] EAP-SIM Architecture proposal
: "Masashi Honma"
To: "Dimi Lee"
Cc: "Jonas Sicking" , "Kyle Machulis"
, "dev-b2g"
Sent: Friday, August 2, 2013 10:12:49 PM
Subject: Re: [b2g] EAP-SIM Architecture proposal
> But after tracing wpa_supplicant code, we found that we cannot retrieve the
Please let me know your suggestion, thanks
>
> Best regards
> Dimi
>
> - Original Message -
> From: "Jonas Sicking"
> To: "Dimi Lee"
> Cc: "Kyle Machulis" , "dev-b2g"
>
> Sent: Friday, August 2, 2013 12:37:5
Le 07/08/2013 16:29, Stefan Arentz a écrit :
>
> On Jul 3, 2013, at 3:58 AM, Dimi Lee wrote:
>
>> Hi all,
>> Currently taipei team are implementing the EAP-SIM WIFI authentication
>> protocol for B2G device.
>> We want to share current architecture to know if there are any problem or
>> sugg
On Jul 3, 2013, at 3:58 AM, Dimi Lee wrote:
> Hi all,
> Currently taipei team are implementing the EAP-SIM WIFI authentication
> protocol for B2G device.
> We want to share current architecture to know if there are any problem or
> suggestion of this design.
> So any suggestion or question
; own wpa_supplicant in our repository, but
> i think its a pretty bad idea to maintain our own wpa_supplicant.
>
> Please let me know your suggestion, thanks
>
> Best regards
> Dimi
>
> - Original Message -
> From: "Jonas Sicking"
> To: "Dimi L
d how to test it. This is something we should do for
the other wifi functionality too.
/ Jonas
>
> Please let me know if you still have any concern or question.
>
> BR
> Dimi
>
> ----- Original Message -
> From: "Jonas Sicking"
> To: "Dimi
Jonas
>
> Please let me know if you still have any concern or question.
>
> BR
> Dimi
>
> - Original Message -
> From: "Jonas Sicking"
> To: "Dimi Lee" , "Kyle Machulis"
> Cc: "dev-b2g"
> Sent: Thursday, August 1, 20
-
From: "Jonas Sicking"
To: "Dimi Lee" , "Kyle Machulis"
Cc: "dev-b2g"
Sent: Thursday, August 1, 2013 3:30:18 PM
Subject: Re: [b2g] EAP-SIM Architecture proposal
Hi Dimi,
I have a couple of concerns here.
First off, my understanding is that this doe
Hi Dimi,
I have a couple of concerns here.
First off, my understanding is that this doesn't create any new
workers, right? This only adds additional code to the already existing
worker that we are using to communicate with the wpasupplicant. Is
this correct? If so that's fine. We need to avoid ad
access SIM
directly, so we don't need to know if SIM API is different.
Best regards
Dimi
- Original Message -
From: "Masashi Honma"
To: "Dimi Lee"
Cc: "dev-b2g"
Sent: Thursday, July 4, 2013 8:03:16 AM
Subject: Re: [b2g] EAP-SIM Architecture proposal
Grea
Great!
I'm doing same project.
Now I can connect with EAP-SIM/AKA/AKA' by using SIM emulator in wpa_supplicant.
Because I don't have SIM reader.
If you want, I can upload the patch.
But I have concern about the approach using pcsc funcs.
I guess each SIM vendor has own SIM API.
So I think we need
Hi all,
Currently taipei team are implementing the EAP-SIM WIFI authentication protocol
for B2G device.
We want to share current architecture to know if there are any problem or
suggestion of this design.
So any suggestion or question is welcome.
I will briefly describe what is EAP-SIM first
29 matches
Mail list logo
