Hi Nate,
Thanks for the suggestion! Unfortunately, it still failed :(
I got the following error message in proftp log:
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: enteringpostgres
cmd_escapestring
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: enteringpostgres cmd_open
2013-08-09
On Aug 9, 2013, at 2:38 AM, Leon Mei wrote:
Hi Nate,
Thanks for the suggestion! Unfortunately, it still failed :(
I got the following error message in proftp log:
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: enteringpostgres
cmd_escapestring
2013-08-09 08:32:41,777
For the moment, the best solution is to disable PBKDF2 in Galaxy if
you are also using FTP. That is how Galaxy main is currently
configured.
--
James Taylor, Assistant Professor, Biology/CS, Emory University
On Fri, Aug 9, 2013 at 10:01 AM, Nate Coraor n...@bx.psu.edu wrote:
On Aug 9, 2013, at
Hi Nate/James,
Thanks! Where should I look into to disable PBKDF2 in the Galaxy code?
Cheers,
Leon
On Fri, Aug 9, 2013 at 4:28 PM, James Taylor ja...@jamestaylor.org wrote:
For the moment, the best solution is to disable PBKDF2 in Galaxy if
you are also using FTP. That is how Galaxy main
I previously tried to get this to work, too. After a lot of trial-and-error, I
gave up because proFTPd always calculated a different string after salting and
hashing the password with PBKDF2 than what is stored in the database. I'm sure
that it extracted the correct salt and password, but
On Jul 26, 2013, at 3:51 PM, Leon Mei wrote:
Dear galaxy developers,
We have tried today to upgrade our proftpd configuration to make uploading
for our galaxy users possible again, both for users with old as well as
new style hashed passwords. We upgraded proftpd on the server to 1.3.5rc3
Dear galaxy developers,
We have tried today to upgrade our proftpd configuration to make uploading
for our galaxy users possible again, both for users with old as well as
new style hashed passwords. We upgraded proftpd on the server to 1.3.5rc3
and have the following SQL part in our configuration
