Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of alcosholik@gmail.com
 designates 209.85.223.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <E7CD508B-FAF5-44D7-B724-A76CDC728872@apache.org>
References: <980F839E3DB1465287B1FFE3FF665DEB@chriskeele.com>
 <CAJ_m3YCH_1+3EqZnBVCo1sN8Vffuh1JhgCgkLW=4SsXL1Uiqiw@mail.gmail.com>
 <B24D1215-ED30-4720-9523-0B6E40352EEA@apache.org>
 <878ABCFE-A3E9-4FA8-84F7-C58729570834@programmazione.it>
 <CAJNb-9pgCU6XDhz+xS6SDrn7ez8+sRg_fK=xFsZk0wSW9k_q6w@mail.gmail.com>
 <E7CD508B-FAF5-44D7-B724-A76CDC728872@apache.org>
From: Alexei Sholik <alcosholik@gmail.com>
Date: Tue, 12 Nov 2013 09:58:22 +0200
Message-ID: 
 <CAAPY6eNUUW7DSS9BPh1s74esT9uBYjWd9cuGv-0oUvianbXBTQ@mail.gmail.com>
Subject: Re: Elixir Sandbox
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=047d7bd76b009cabd604eaf6379f

--047d7bd76b009cabd604eaf6379f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> So yes, Elixir please! :) And if we get a sandbox as well, we can even
enable it by default :)

I tried to add a .beam produced by Elixir to my CouchDB installation (I
didn't want to rebuild the whole project), but Couch can't find it. I
posted a question on this ML[1]. Any hints?

[1]:
http://mail-archives.apache.org/mod_mbox/couchdb-dev/201308.mbox/%3CCAAPY6e=
PTSVSTPYWvquRnnXN0pwbfWmitEE2GAWjsPhATv5iw9Q@mail.gmail.com%3E


On Thu, Oct 17, 2013 at 12:29 AM, Jan Lehnardt <jan@apache.org> wrote:

>
> On Oct 16, 2013, at 23:16 , Benoit Chesneau <bchesneau@gmail.com> wrote:
>
> > On Wed, Oct 16, 2013 at 10:54 PM, Filippo Fadda <
> > filippo.fadda@programmazione.it> wrote:
> >
> >> Sandboxing is something optional I think, you need only when you are
> >> developing a CouchApp, when you do all in JavaScript, using the _users
> >> database and running the app inside CouchDB. But if you are just using
> >> CouchDB like a database, developing a web app using PHP or Python, for
> >> example, you'll never give access to CouchDB from outside, through Fut=
on
> >> for example, so no one will be able to store a new design doc in your
> >> database to run malicious code. I'm using PHP with the ElephantOnCouch
> >> Query Server, writing ddoc in PHP, and I really don't see why I should
> >> using runkit to sandboxing the Query Server.
> >>
> >> -Filippo
> >>
> >
> > Sandboxing is not only needed for couchapps but also views. If someone
> > using a view inspect your hd  and emit the result or send  your docs
> using
> > a tcp connections to an unknown remote target it can be a risk. That's
> why
> > it's needed. Even allowed users can be a possible risk.
>
> I think Filippo used =E2=80=9CCouchApps=E2=80=9D as a synonym for =E2=80=
=9Cyou may receive code
> not written by you or someone your trust=E2=80=9D in which case you absol=
utely
> want a sandbox.
>
> My point was just that there are equally scenarios where that trust exist=
s
> and Filippo illustrated them a bit better than I did originally.
>
> So yes, Elixir please! :) And if we get a sandbox as well, we can even
> enable it by default :)
>
> Best
> Jan
> --
>
>
>
>
> >
> >
> >
> >>
> >> On Oct 16, 2013, at 10:27 PM, Jan Lehnardt wrote:
> >>
> >>> Another option would be to start with treating the Elexir Query Serve=
r
> >>> like the Erlang Query Server and keep it off by default and with full
> >>> access to the internals, so people could opt into it, if their
> >> environment
> >>> allows for it.
> >>>
> >>> Sandboxing could be a step on top or later.
> >>>
> >>> I for one would like to see native Elexir support for Views et.al in
> >> CouchDB :)
> >>>
> >>> Best
> >>> Jan
> >>> --
> >>>
> >>> On Oct 16, 2013, at 20:48 , Paul Davis <paul.joseph.davis@gmail.com>
> >> wrote:
> >>>
> >>>> There have been discussions on figuring out how to sandbox Erlang. T=
he
> >>>> biggest thing on that front was that we'd want it to be a whitelist =
as
> >>>> opposed to a blacklist of modules and/or module/function pairs. The
> >>>> second is that with dynamic invocation its not immediately apparent =
if
> >>>> that's entirely possible to do.
> >>>>
> >>>> On Wed, Oct 16, 2013 at 10:39 AM, Chris Keele <email@chriskeele.com>
> >> wrote:
> >>>>> Hey everyone! I'm trying to develop a sandbox for Elixir, and I
> wanted
> >> to see how such a library might prove useful to the CouchDB dev
> community.
> >>>>>
> >>>>> My initial goal is just to be able to run string of code in a
> >> predefined environment with configurable modules disabled, returning a=
ll
> >> output. But I'd like to design it for bigger things from the ground up=
,
> so
> >> I was wondering what sorts of requirements you might have of a sandbox
> >> library if you wanted to, say, implement a secure view processor.
> >>>>>
> >>>>> I've started a discussion thread here:
> >> https://groups.google.com/forum/#!topic/elixir-lang-talk/wA1l74HCZmI,
> but
> >> I'm particularly interested in your opinions!
> >>>>> --
> >>>>> Chris Keele
> >>>>>
> >>>
> >>
> >>
>
>


--=20
Best regards
Alexei Sholik

--047d7bd76b009cabd604eaf6379f--