Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of feeder.of.the.bears@gmail.com
 designates 209.85.217.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=untkBKQbohhrpW1yac+mrFIwtBY/LYBP8dYc3vuQ/MTeXv+B/u+Q71+qTKllGfvN8l
         OXoCszXZVjpoi3h0DlS5wdvhhsTYChZ9VSXjyldb2yXn+/6DAii/N4mscp20lF3ed1Bn
         mWAeNkqeL6QMY+Fl0CbvtTNkOwmSVGENLtOM8=
MIME-Version: 1.0
In-Reply-To: <fa2d9f450907060143i7d2ce37asf446b75107b65d9f@mail.gmail.com>
References: <c7fc82820907050545v46debeb7i6d3f49be0be86cae@mail.gmail.com>
	 <cdbebedf0907051306r797084aagb883824167ad47ae@mail.gmail.com>
	 <fa2d9f450907060003w7abf4b36h9faa47010b59bc4b@mail.gmail.com>
	 <c7fc82820907060124k7b6ea0e3h3442af1930ae5e7d@mail.gmail.com>
	 <fa2d9f450907060143i7d2ce37asf446b75107b65d9f@mail.gmail.com>
Date: Mon, 6 Jul 2009 07:08:23 -0700
Message-ID: <cdbebedf0907060708x4c47388fne6ae08a7603e706c@mail.gmail.com>
Subject: Re: Scala interpreter action
From: David Pollak <feeder.of.the.bears@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=00163630f5c90271e2046e0a0a07

--00163630f5c90271e2046e0a0a07
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Mon, Jul 6, 2009 at 1:43 AM, Richard Hirsch <hirsch.dick@gmail.com>wrote:

> Should I deploy with this functionality active or not?


I wouldn't.  It's kinda like taping a "Hack Me" sticker onto the site. :-)


>
>
> I just did a stax deplyoment with the
> actions.scala_interpreter.enable=false
>
> D.
>
> On Mon, Jul 6, 2009 at 10:24 AM, Vassil Dichev<vdichev@apache.org> wrote:
> >> Should we remove it completely from the source or should we just
> >> deactivate it by default?
> >>
> >> I agree that I wouldn't activate it in a producticve setting but it
> >> might be useful while developing.
> >
> > Granted, this might not be the best way to monitor/debug ESME (e.g. if
> > memory is so tight the JVM won't be able to create a new interpreter
> > instance or send a new message). When I implemented the feature I was
> > actually thinking of Dick's request for making it easier for ESME
> > newcomers to learn Scala. I've also spent some time thinking about
> > using ESME in a university and this feature makes a lot of sense in a
> > classroom.
> >
> > My point is, I still think it could be made secure with a careful
> > java.policy file (which a conscientious administrator should use
> > anyway). David, do you think the Scala interpreter is impossible to
> > secure or just not worth the effort? Also, what difference would it
> > make to use Rhino, but not Scala in terms of a secure interpreter? The
> > Scala interpreter implementation does use a new classloader and even
> > allows you to override it and implement your own one. Try e.g. "import
> > org.apache.esme.model.Message" or "import net.liftweb.util.Box".
> >
> > If the primary concern is trust in a federation, we could make it so a
> > server is not allowed to participate in a federation if the Scala
> > interpreter action is enabled.
> >
> > Cheers,
> > Vassil
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

--00163630f5c90271e2046e0a0a07--