Subj : Re: [SpiderMonkey]Export/import statements bug in new release of
To   : netscape.public.mozilla.jseng
From : Martin Honnen
Date : Thu Jul 08 2004 01:21 pm



David wrote:


> I found a bug in the new javascript 1.5 version of SpiderMonkey. If you 
> try to use the export/import statements (which are very usefull if you 
> using security scripts in dynamic page generation context), the new 
> version of mozilla (1.7) does not reconize anymore thoses statements 
> whereas the version 1.6 does.
> 
> I saw in http://lxr.mozilla.org/mozilla/source/js/src/jsconfig.h#457 
> that this functionnality seems to be desactivated in new 1.5 javascript 
> version, is this normal ?
> 
> Is there a another way to call a signed javascript function in a 
> non-signed html page ?
> 
> I've signal a bug http://bugzilla.mozilla.org/show_bug.cgi?id=249211 at 
> the end of last month, but I haven't got any reply for the moment...
> 
> For thoses who are interested in writing signed Javascript functions : 
> http://developer.netscape.com/docs/manuals/communicator/jssec/contents.html

I can't really answer that but as far as I understand from
   http://www.mozilla.org/projects/security/components/jssec.html
and
  http://www.mozilla.org/projects/security/components/signed-scripts.html
the whole way of using signed scripts is very different in Mozilla 
compared to Netscape 4, in Netscape 4 you signed a script in a script 
archive while with Mozilla you sign a complete HTML page and serve it 
from a jar: URL.

As for the import/export change, bonsai
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=&branchtype=match&dir=&file=jsconfig.h&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2003-01-01&maxdate=2004-07-08&cvsroot=%2Fcvsroot
tells me that Brendan did that on 2003-12-21, his comment there is

   Footprint wins: disable export/import from js1.5

so I am sure Brendan will give you an answer on those import/export problem.

-- 

	Martin Honnen
	http://JavaScript.FAQTs.com/

.