Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion Content Security Policy - final call for comments
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Sid Stamm  
View profile  
 More options Apr 7 2009, 11:28 am
Newsgroups: mozilla.dev.security
From: Sid Stamm <s...@mozilla.com>
Date: Tue, 07 Apr 2009 08:28:03 -0700
Local: Tues, Apr 7 2009 11:28 am
Subject: Re: Content Security Policy - final call for comments
On 4/7/09 4:01 AM, Gervase Markham wrote:
> Surely not? If Site Angelic redirects to Site Be-Evil, We don't send
> Angelic's cookies to Be-Evil, do we? Or have I missed something? You may
> need to describe the attack scenario in more detail for my small brain.

Since the user's entire request header is in the report, any cookies
sent with the request header to Angelic get forwarded on.  While Be-Evil
doesn't actually get forwarded cookies, the cookies are buried in the
content of the report that is forwarded under the <request-headers> field.

>> I think the intention for requiring the allow directive was to force the
>> policy-writer into writing out the default case to minimize possibility
>> for false assumptions. I'm not sure though.

> Fair enough. As long as the JS console/error report says something
> sensible if it's missing.

Of course.   Any forgivable but bad policy syntax is going to be spat
into the error console.  Terminal ("can't parse") errors will cause CSP
to fail closed ("allow self") and still raise an error.

-Sid


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.