Well, it could be modified to never return a value back to the
interface after being set. Would that be sufficient?
On Mon, Apr 4, 2011 at 11:46 AM, Daniel Schmidt <danielschmid...@gmx.net> wrote:
> Hello all!
> Thanks alot K! Although I have to admit, that it seems too insecure, at
> least for the tool I am currently working on. The password field is needed
> to connect to a database, which contains (sensitive) patient data. Revealing
> the password to someone else by accident when re-running a job could give
> him or her access to data he or she should have never access to.
> In spite of everything, thank you again!
> Am 04.04.2011 17:17, schrieb Kanwei Li:
>> Hi Daniel,
>> I have attached a patch that does this below. You can use it by
>> setting<param type="password"> However the security is lacking as you
>> can see the string when you try to re-run the job and view source. Is
>> this sufficient for your purposes?
>> On Sat, Apr 2, 2011 at 11:01 AM, Daniel Schmidt<danielschmid...@gmx.net>
>>> Hi all!
>>> Is there any way to use password input fields ("<input
>>> with tools? A tools XML definition file only seems to support text and
>>> textarea fields. I already tried setting a tools parameter type to
>>> "password", which unfortunately results in an "Unknown tool parameter
>>> 'password'". Trying "password="True"" (like "area="True"") does not
>>> in an error, but the text field is still just a normal text field.
>>> I may be mistaken, as I am new to Python and Galaxy, but there already
>>> to be a PasswordField class and a TextField class, which both can be
>>> in several files. Was the PasswordField class for tool parameters maybe
>>> disabled for a reason?
>>> Please keep all replies on the list by using "reply all"
>>> in your mail client. To manage your subscriptions to this
>>> and other Galaxy lists, please use the interface at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at: