W3C home > Mailing lists > Public > public-web-security@w3.org > September 2015

Re: SOP wiki was: A Somewhat Critical View of SOP (Same Origin Policy)

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Tue, 29 Sep 2015 06:24:47 +0200
To: GALINDO Virginie <Virginie.Galindo@gemalto.com>, Henry Story <henry.story@co-operating.systems>
Cc: Dave Raggett <dsr@w3.org>, Martin Paljak <martin.paljak@ria.ee>, "public-web-security@w3.org" <public-web-security@w3.org>
Message-ID: <560A128F.8040609@gmail.com>
On 2015-09-28 21:47, GALINDO Virginie wrote:

Dear Virginie,

I wonder if this really is meaningful when the "opponents" only interest is
proving that those who question SOP's universal applicability are imbeciles
or haven't done their homework.  Since Web Payments is in a worse condition
today than it was during its infancy some 20 years ago, there's obviously a
pretty serious impedance mismatch between the browser vendors and the market.

IF we should continue I propose that we stick to two security-related
applications that already are used by millions of people:

- eID
- Web Payments


> Henry,
> I believe that the wiki page should start by  writing use cases, and not re-explaning SOP cons and your technical vision. If you want to trigger collaborative thinking, thanks for exposing:
> - Use case,
> - What feature in your use cases can't be achieved with today's technical rules.
> And then we will be able to have technical discussions about potentiel solutions.
> Regards
> Virginie
> ---- Henry Story a écrit ----
>> On 25 Sep 2015, at 15:38, GALINDO Virginie <Virginie.GALINDO@gemalto.com> wrote:
>> Thanks for completing your use case on the wiki dedicated to that topic, guys !
>> Regards,
>> Virginie
> Thanks Virginie for the great idea of putting up this wiki. Mailing list
> discussions are very educational if one follows them with great care, but
> it is very difficult for people who jump in from the outside in mid conversation
> or who are following from the sidelines to understand what if anything has
> been gained by the discussion.
> I have brought together a lot of what I have learnt about SOP with many
> references to IETF and W3C specs, pointers to new evolutions in the webapp(sec)
> groups, and discussion with community members on the wiki
> https://www.w3.org/Security/wiki/IG/a_view_on_SOP
> This weekend I re-arranged the wiki into three pieces
> 1. Conceptual map : just to give an idea how work from privacy, identity,
> security, logic, and other areas bear on the issue. There are still pieces
> to be filled out here.
> 2. Exceptions to SOP:
>    the more I look around the more I have found well documented and justified
> exceptions to narrow understandings of SOP. This should give us some good raw
> material for a later exploration of a theory of SOP.
> 3. Implications for Future standards.
>    A third section on who SOP is bringing up issues for future requirements such as
> WebPayments.
> 4. Theory of SOP
>    Here I think we'll be able to bring together an extended theory of SOP
> that makes sense of the exceptions, whilst showing how these tie into other elements of the conceptual spaces. My feeling is that a bit of work  in some very initial modal logic of belief contexts would help give a secure logical foundation.
> I think this is taking shape. Of course there will be errors, improvements. It is not
> complete, so feedback is welcome.
> Henry
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Received on Tuesday, 29 September 2015 04:25:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:09:38 UTC