a security review on it shortly - but it should be sound.
>
>Hope this helps!
>
>
>
>>
>>Message: 11
>>Date: Mon, 30 Jan 2012 09:31:15 -0500
>>From: David Hoover
>>To: Sarah Maman
>>Cc: galaxy-dev@lists.bx.psu.edu
>>Subject: Re: [galaxy-dev]
om: David Hoover
>To: Sarah Maman
>Cc: galaxy-dev@lists.bx.psu.edu
>Subject: Re: [galaxy-dev] Unix user account/connection and Galaxy
> connection
>Message-ID:
>Content-Type: text/plain; charset="us-ascii"
>
>I'd love to know answers to this question as well
Yeah, there is not currently a great solution to this problem. Some have
implemented a tools just like David's. You could also get around setuid with
sudo, although the security implications are probably the same.
I think the ideal system would be to start Galaxy as root, drop privileges, and
I'd love to know answers to this question as well. So far, all I've done is
create two tools for copying files between Galaxy and a user's personal
directories using a rather dangerous setuid executable.
I have mulled over two possibilities for this problem. One is to run Galaxy as
root. The
Dear all,
There is currently no link between an user ssh connection on his own
account (own space on Unix) and the Galaxy connection.
How to run Galaxy on an Unix user account? How to link the data storage
system and the Unix user account (symlink?)?
The goal is to not need to copy or move da
