handling private user data

[Juan Negron]

Hi Sidnei:

They both end up with the information on the target instance/computer.
 Instances can be accessed via ssh with the ssh key used to instantiate so,
there is some security involved there but, the bottom line is that anyone
with root access to the machine will be able to see all of the files.

Juju doesn't provide an extra layer of security in the way files are saved
to the instance/node.


Thanks,

Juan



On Sat, Sep 15, 2012 at 10:33 AM, Sidnei da Silva <
sidnei.da.silva at canonical.com> wrote:

> On Sat, Sep 15, 2012 at 2:12 PM, Juan Negron <negronjl at xtremeghost.com>
> wrote:
> > Hi Ricardo:
> >
> > The way you describe in your question ( having a config option that
> points
> > to a repository, file server, etc. ) seems reasonable to me.
> >
> > Another way would be to have a directory  in the charm itself where you
> can
> > put said files so the charm can use them.  This would require the
> > devops/user to download the charm before deploying it.  The latter option
> > could be considered a bit more paranoid as it would require you to
> download
> > the charm, adding the necessary files to a predetermined directory and
> > deploy ( from your local computer ).
>
> Which of them is safer, from a security standpoint? IE are the configs
> or charms protected in such a way that other charms can't fetch them?
>
> --
> Sidnei
>
> Make the most of Ubuntu with Ubuntu One
> http://one.ubuntu.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20120915/dbc904f2/attachment.html>