edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] zip and security
Date: Mon, 5 Mar 2018 15:35:18 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.03.1803051502430.11373@carhart.net> (raw)
In-Reply-To: <20180305223246.GA20658@nautica>

On Mon, 5 Mar 2018, Dominique Martinet wrote:

> Karl Dahlke wrote on Mon, Mar 05, 2018:
>> He writes a web page with javascript that does an xhr request to
>> zipxd://foo.zip@:@top
> I think it's a matter of priority, but now we have javascript working a
> bit better we might soon find time to make it more restricted somehow.
> I still think allowing any site to do xhr requests anywhere is not
> something we will want.

I completely agree.  For a long time we've been in a pocket.  It didn't 
matter that much because we didn't have a lot of pages that were getting 
all the way through the several steps of retrieving responseText, going to 
a callback, processing the content, and innerHTML side effects take it 
back to EBML.  (!)  It's very exciting that we started to get this, so 
congratulations, our prize for breaking through is a new tier of robust 

I could write the same-origin restriction into javascript.  Not that this 
covers it entirely, but at least the default would be strict and we would 
block some opportunists.  Suppose I have just loaded abc.com, and I 
instantiate a new XHRHttpRequest object.  I try to retrieve a page from 
def.com.  Should I intercept this in javascript before it gets to 
fetchHTTP, and fail silently?  Or throw something?

> I started writing a mail about this ages ago (August last year!) and it

      reply	other threads:[~2018-03-05 23:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 22:17 Karl Dahlke
2018-03-05 22:32 ` Dominique Martinet
2018-03-05 23:35   ` Kevin Carhart [this message]

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:

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

  git send-email \
    --in-reply-to=alpine.LRH.2.03.1803051502430.11373@carhart.net \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* 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;
as well as URLs for NNTP newsgroup(s).