prevent tool escaping input
Hi, how can I prevent a tool escaping the input to a tool's text field? For example, if I put a [ in the text field, I see it in the console as __ob__ on the command line? thanks, James
I added the name of the option to NEVER_SANITIZE in galaxy.util:params A bit of a worry that user parameters can end up on the command line, eh? 2008/11/25 James Casbon <casbon@gmail.com>:
Hi,
how can I prevent a tool escaping the input to a tool's text field?
For example, if I put a [ in the text field, I see it in the console as __ob__ on the command line?
thanks, James
On 11/25/08 6:02 PM, "James Casbon" <casbon@gmail.com> wrote:
I added the name of the option to NEVER_SANITIZE in galaxy.util:params
A bit of a worry that user parameters can end up on the command line, eh?
Yes, I agree, 'a bit of a worry', but we are in a similar situation: We are developing a tool, where the user can provide a pattern (like:"[AC]-x-V-x-x-{ED}") which will be fed into another program. And our perl wrapper just does a simple substitution: $pattern =~ s/__ob__/[/g; $pattern =~ s/__cb__/]/g; $pattern =~ s/__oc__/{/g; $pattern =~ s/__cc__/}/g; Hans
2008/11/25 James Casbon <casbon@gmail.com>:
Hi,
how can I prevent a tool escaping the input to a tool's text field?
For example, if I put a [ in the text field, I see it in the console as __ob__ on the command line?
thanks, James
_______________________________________________ galaxy-user mailing list galaxy-user@bx.psu.edu http://mail.bx.psu.edu/cgi-bin/mailman/listinfo/galaxy-user
participants (2)
-
Hotz, Hans-Rudolf
-
James Casbon