We're having problems setting up ftp and authenticating against the postgres
We've reviewed these pages and a few others:
Peter Briggs Blog Post:
Ricardo Perez's Galaxy Developers thread that Peter referenced:
When we run proftpd in debug mode we get similar output to the one in Ricardo's
Ricardo's command line output:
login002 proftpd login002 (10.28.56.101[10.28.56.101]):
2016-04-20 10:53:42,597 pcegalaxy proftpd pcegalaxy.ci.northwestern.edu
expected 'NMmACzgvs8Oh+BCnSw+2GFxpYl7cLiQu', got
>From looking at the galaxy_user table, it seems like proftpd is finding the
>correct password information (password in table:
The last post from that thread mentions back-channel advice that was helpful.
Maybe we need the same advice ?
In case it's important we're using LDAP for our general user authentication.
Here is our proftpd.conf:
ServerName "Galaxy FTP
# Port 21 is the standard FTP port.
# Don't use IPv6 support by default.
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
# To prevent DoS attacks, set the maximum number of child processes
# to 30. If you need to allow more than 30 concurrent connections
# at once, simply increase this value. Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd).
# Set the user and group under which the server will run.
# To cause every FTP user to be "jailed" (chrooted) into their home
# directory, uncomment this line.
# Automatically create home directory if it doesn't exist
CreateHome on dirmode 700
# Allow users to overwrite their files
# Allow users to resume interrupted uploads
# Bar use of SITE CHMOD by default
# Bar use of RETR (download) since this is not a public file drop
# Do not authenticate against real (system) users
## Set up mod_sql_password - Galaxy passwords are stored as hex-encoded SHA1
## Set this if Galaxy user UID and/or GID are less than 999
## Configuration that handles PBKDF2 encryption
## Set up mod_sql to authenticate against the Galaxy database
SQLConnectInfo galaxy_db@localhost:5432 <USERNAME>
SQLPasswordPBKDF2 SHA256 10000 24
## For PBKDF2 authentication
## Define a custom query for lookup that returns a passwd-like entry for PBKFD2
## UID and GID should match your Galaxy user.
SQLNamedQuery LookupGalaxyUser SELECT "email, (CASE
WHEN substring(password from 1 for 6) = 'PBKDF2' THEN substring(password from
38 for 69) ELSE password END) AS
galaxy_user WHERE email='%U'"
## Define custom query to fetch the password salt
SQLNamedQuery GetUserSalt SELECT "(CASE WHEN SUBSTRING (password from 1 for 6)
= 'PBKDF2' THEN SUBSTRING (password from 21 for 16) END) AS salt FROM
galaxy_user WHERE email='%U'"
Any advice would be great.
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:
To search Galaxy mailing lists use the unified search at: