Re: Updated version of possible solution for Korean banking use case

I read the minutes of last meeting and the slides. I am not sure to
understand what the use case has to do with SOP, you can exchange
keys/certificate between the origins using postMessage, and then signing
from one origin or another contains the same risk, so I don't get what
SOP has to do with this.

If I understand correctly the issue is more about authenticating the
client and using the certificates with TLS, which can not be performed
because we don't control the TLS sessions.

Then we are back to secondary features again : exposing certificates +
TLS sessions

Some time ago I sent [1] which is an example of authentication on top of
TLS.

[1] http://archives.seul.org/or/dev/Jan-2011/msg00052.html

Regards,

Aymeric

Le 19/07/2013 10:50, 조상래 a e'crit :
>
> Hi all,
>
> The attached document is the updated version of possible solution for
> Korean banking use case using Trusted CA List.
>
> I hope that the document helps you understand Korean use case and
> proposed solution for SOP restriction.
>
> Moreover, I would like to discuss issues related to Korean banking use
> case in the concall on next Monday if possible.
>
> Have a nice weekend
>
> Sangrae Cho
>
> ===========================================================
>
> *Sangrae Cho*
>
> *Authentication Research Team*
>
> *ETRI*(Electronics and Telecommunications Research Institute)
>
> 218 Gajeongro, Yuseong-Gu, Daejeon, 305-700, KOREA
>
> Phone : +82-42-860-6939 Fax : +82-42-860-1471
>
> ===========================================================
>

-- 
jCore
Email :  avitte@jcore.fr
iAnonym : http://www.ianonym.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
Web :    www.jcore.fr
Extract Widget Mobile : www.extractwidget.com
BlimpMe! : www.blimpme.com