LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 07-10-2019, 12:49 PM   #1
rsmereka
Member
 
Registered: Jul 2003
Location: Southwestern Ontario, Canada
Distribution: LFS, Void, NuTyX, MX, OpenBSD, Mint, Gentoo
Posts: 48
Blog Entries: 3

Rep: Reputation: 15
NuTyX Proftpd 530 Login incorrect


Hi,

I am having issues configuring Proftpd on a NuTyX PC. I should start by saying that my objective on the proftpd server is:
1. anonymous not allowed
2. PAM not in use (authentication against local Linux accounts)
3. authenticated users should be able to read and write anywhere their user account permits

When I first installed Proftpd, I could not not log onto the ftp server getting a '530 Login incorrect' error. After searching many web pages, trying a some 'fixes' and getting nowhere, I found out how to start proftpd in forground mode. Here is a server log with two (2) of my login attempts:
Quote:
2019-07-10 13:19:01,847 nutyx proftpd[8708]: using TCP receive buffer size of 87380 bytes
2019-07-10 13:19:01,847 nutyx proftpd[8708]: using TCP send buffer size of 16384 bytes
2019-07-10 13:19:01,851 nutyx proftpd[8708]: <Directory /*>: adding section for resolved path '/*'
2019-07-10 13:19:01,934 nutyx proftpd[8708] localhost.localdomain:
2019-07-10 13:19:01,934 nutyx proftpd[8708] localhost.localdomain: Config for ProFTPD:
2019-07-10 13:19:01,934 nutyx proftpd[8708] localhost.localdomain: ~proftpd/
2019-07-10 13:19:01,934 nutyx proftpd[8708] localhost.localdomain: Limit
2019-07-10 13:19:01,934 nutyx proftpd[8708] localhost.localdomain: DenyAll
2019-07-10 13:19:01,934 nutyx proftpd[8708] localhost.localdomain: Umask
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: Limit
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: AllowAll
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: /*
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: AllowOverwrite
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: Umask
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: DefaultServer
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: Umask
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: UserID
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: UserName
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: GroupID
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: GroupName
2019-07-10 13:19:01,935 nutyx proftpd[8708] localhost.localdomain: set core resource limits for daemon
2019-07-10 13:19:01,936 nutyx proftpd[8708] localhost.localdomain: ProFTPD 1.3.6 (stable) (built Thu Apr 4 2019 16:55:27 UTC) standalone mode STARTUP
2019-07-10 13:19:13,892 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): session requested from client in unknown class
2019-07-10 13:19:13,893 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): mod_cap/1.1: adding CAP_AUDIT_WRITE capability
2019-07-10 13:19:13,893 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): mod_ident/1.0: ident lookup disabled
2019-07-10 13:19:13,893 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): mod_delay/0.7: no DelayOnEvent rules configured with "DelayTable none" in effect, disabling module
2019-07-10 13:19:13,894 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): connected - local : ::ffff:192.168.1.61:21
2019-07-10 13:19:13,894 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): connected - remote : 192.168.1.74:65350
2019-07-10 13:19:13,894 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): FTP session opened.
2019-07-10 13:19:17,835 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'USER rick' to mod_core
2019-07-10 13:19:17,835 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'USER rick' to mod_core
2019-07-10 13:19:17,835 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'USER rick' to mod_delay
2019-07-10 13:19:17,835 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'USER rick' to mod_auth
2019-07-10 13:19:17,836 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching CMD command 'USER rick' to mod_auth
2019-07-10 13:19:17,836 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching POST_CMD command 'USER rick' to mod_delay
2019-07-10 13:19:17,836 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD command 'USER rick' to mod_log
2019-07-10 13:19:17,836 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD command 'USER rick' to mod_delay
2019-07-10 13:19:21,187 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'PASS (hidden)' to mod_core
2019-07-10 13:19:21,187 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'PASS (hidden)' to mod_core
2019-07-10 13:19:21,187 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'PASS (hidden)' to mod_delay
2019-07-10 13:19:21,187 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'PASS (hidden)' to mod_auth
2019-07-10 13:19:21,187 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching CMD command 'PASS (hidden)' to mod_auth
2019-07-10 13:19:21,192 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): crypt(3) failed: Invalid argument
2019-07-10 13:19:21,192 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): USER rick (Login failed): Incorrect password
2019-07-10 13:19:21,192 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching POST_CMD_ERR command 'PASS (hidden)' to mod_delay
2019-07-10 13:19:21,192 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_log
2019-07-10 13:19:21,192 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_delay
2019-07-10 13:19:21,192 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_auth
2019-07-10 13:19:28,251 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'QUIT' to mod_core
2019-07-10 13:19:28,251 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'QUIT' to mod_core
2019-07-10 13:19:28,251 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching CMD command 'QUIT' to mod_core
2019-07-10 13:19:28,251 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD command 'QUIT' to mod_log
2019-07-10 13:19:28,251 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD command 'QUIT' to mod_core
2019-07-10 13:19:28,252 nutyx proftpd[8725] localhost.localdomain (192.168.1.74[192.168.1.74]): FTP session closed.
2019-07-10 13:19:30,003 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): session requested from client in unknown class
2019-07-10 13:19:30,003 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): mod_cap/1.1: adding CAP_AUDIT_WRITE capability
2019-07-10 13:19:30,003 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): mod_ident/1.0: ident lookup disabled
2019-07-10 13:19:30,003 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): mod_delay/0.7: no DelayOnEvent rules configured with "DelayTable none" in effect, disabling module
2019-07-10 13:19:30,004 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): connected - local : ::ffff:192.168.1.61:21
2019-07-10 13:19:30,004 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): connected - remote : 192.168.1.74:65352
2019-07-10 13:19:30,004 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): FTP session opened.
2019-07-10 13:19:33,226 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'USER rick' to mod_core
2019-07-10 13:19:33,226 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'USER rick' to mod_core
2019-07-10 13:19:33,226 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'USER rick' to mod_delay
2019-07-10 13:19:33,226 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'USER rick' to mod_auth
2019-07-10 13:19:33,227 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching CMD command 'USER rick' to mod_auth
2019-07-10 13:19:33,227 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching POST_CMD command 'USER rick' to mod_delay
2019-07-10 13:19:33,227 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD command 'USER rick' to mod_log
2019-07-10 13:19:33,227 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD command 'USER rick' to mod_delay
2019-07-10 13:19:36,562 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'PASS (hidden)' to mod_core
2019-07-10 13:19:36,562 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'PASS (hidden)' to mod_core
2019-07-10 13:19:36,562 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'PASS (hidden)' to mod_delay
2019-07-10 13:19:36,562 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'PASS (hidden)' to mod_auth
2019-07-10 13:19:36,562 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching CMD command 'PASS (hidden)' to mod_auth
2019-07-10 13:19:36,567 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): crypt(3) failed: Invalid argument
2019-07-10 13:19:36,567 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): USER rick (Login failed): Incorrect password
2019-07-10 13:19:36,567 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching POST_CMD_ERR command 'PASS (hidden)' to mod_delay
2019-07-10 13:19:36,567 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_log
2019-07-10 13:19:36,567 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_delay
2019-07-10 13:19:36,567 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_auth
2019-07-10 13:19:39,250 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'QUIT' to mod_core
2019-07-10 13:19:39,250 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching PRE_CMD command 'QUIT' to mod_core
2019-07-10 13:19:39,250 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching CMD command 'QUIT' to mod_core
2019-07-10 13:19:39,250 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD command 'QUIT' to mod_log
2019-07-10 13:19:39,250 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): dispatching LOG_CMD command 'QUIT' to mod_core
2019-07-10 13:19:39,251 nutyx proftpd[8774] localhost.localdomain (192.168.1.74[192.168.1.74]): FTP session closed.
2019-07-10 13:19:44,012 nutyx proftpd[8708] localhost.localdomain: ProFTPD terminating (signal 2)
2019-07-10 13:19:44,212 nutyx proftpd[8708] localhost.localdomain: ProFTPD killed (signal 2)
2019-07-10 13:19:44,212 nutyx proftpd[8708] localhost.localdomain: ProFTPD 1.3.6 standalone mode SHUTDOWN
2019-07-10 13:19:44,212 nutyx proftpd[8708] localhost.localdomain: deleting existing scoreboard '/var/run/proftpd.scoreboard'
The two relevant lines (IMHO) are:
Quote:
(192.168.1.74[192.168.1.74]): crypt(3) failed: Invalid argument
One line for each login attempt.

At this point I am stuck. Anyone know why crypt fails? It this an auth module incompatibility?

The proftpd config file is as follows:
Code:
# This is a basic ProFTPD configuration file
# It establishes a single server and a single anonymous login.

ServerName                      "ProFTPD"
ServerType                      standalone
DefaultServer                   on

# Port 21 is the standard FTP port.
Port                            21
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
Umask                           022

# 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

MaxInstances                    30

# Set the user and group that the server normally runs at.
User                            proftpd
Group                           proftpd

# To cause every FTP user to be "jailed" (chrooted) into their home
# directory, uncomment this line.
#DefaultRoot ~


# Normally, files should be overwritable.
<Directory /*>
  AllowOverwrite                on
</Directory>

<Limit LOGIN>
   AllowAll
</Limit>

<Anonymous ~proftpd>
   <Limit LOGIN>
   DenyAll
   </Limit>
</Anonymous>

# A basic anonymous configuration, no upload directories.
#<Anonymous ~proftpd>
#  User                          proftpd
#  Group                         proftpd
  # Clients should be able to login with "anonymous" as well as "proftpd"
#  UserAlias                     anonymous proftpd

  # Limit the maximum number of anonymous logins
#  MaxClients                    10

  # 'welcome.msg' should be displayed at login, and '.message' displayed
  # in each newly chdired directory.
#  DisplayLogin                  welcome.msg
#  DisplayChdir                  .message

  # Limit WRITE everywhere in the anonymous chroot
#  <Limit WRITE>
#    DenyAll
#  </Limit>
#</Anonymous>
TIA
 
Old 07-12-2019, 04:02 PM   #2
scasey
Senior Member
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.6
Posts: 3,451

Rep: Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157
There are several possibilities for this.

Please post what "fixes" you've tried...

Last edited by scasey; 07-12-2019 at 04:05 PM.
 
Old 07-15-2019, 12:08 PM   #3
rsmereka
Member
 
Registered: Jul 2003
Location: Southwestern Ontario, Canada
Distribution: LFS, Void, NuTyX, MX, OpenBSD, Mint, Gentoo
Posts: 48

Original Poster
Blog Entries: 3

Rep: Reputation: 15
Sean,

I tried every 'fix' listed and not one of them did anything.

I knew going in that those suggestions would not work. Not one of them is on point. Let me explain.

Quote:
What does proftpd debug logging show, when you attempt to log in? The reason that ProFTPD only ever shows "530 Login incorrect", despite the real underlying cause of the problem, is to prevent leaking useful information to potential attackers. Unfortunately, while good for security, this is bad for debugging. The server-side debug logging will provide more information about what might be going on.
From https://superuser.com/questions/7066...ogin-incorrect

Not one hit discussed the actual error I am getting, they all discuss the 530 error but, in all cases, there is an underlying reason for the 530 error.

Rick
 
Old 07-15-2019, 01:11 PM   #4
scasey
Senior Member
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.6
Posts: 3,451

Rep: Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157
In the config file you posted we don't see evidence of at least two of the suggestions tried:
To comment out the user and group settings
To set UseFtpUsers off

It might be helpful to document every attempted fix. Not saying you need to post them, just that you need to try each one, one at a time, and write down what did (or didn't) happen.

Have you set up logging when running in daemon mode so you can confirm that the logged error is the same?

Some other troubleshooting ideas:
Can you log in at the console with the user and password?
Where are you connecting from?
What ftp client are you using to try to connect?

And, of course, are you sure you're using the correct password?
 
Old 07-15-2019, 03:10 PM   #5
rsmereka
Member
 
Registered: Jul 2003
Location: Southwestern Ontario, Canada
Distribution: LFS, Void, NuTyX, MX, OpenBSD, Mint, Gentoo
Posts: 48

Original Poster
Blog Entries: 3

Rep: Reputation: 15
Sean,

The proftpd.conf I posted here is OOTB. It does not reflect any modifications.

I have documented every attempt:

1. comment out 'User', 'Group' and add 'UseFtpUsers'
2. make sure 'DefaultRoot ~' is uncommented
3. comment out the lines 'AuthPAMConfig' and 'AuthOrder' (not present in file)
4. add 'UseFtpUsers'

Logging in daemon mode is not the same as in debug mode and does not supply all the information.

Attempting to log onto the ftp server from the console results in exactly the same error.

This is a lan-based ftp server, connection is only from within the same subnet. The ftp server is not on the internet.

I am using the standard, no-frills, command line ftp client.

Rick
 
Old 07-15-2019, 03:42 PM   #6
scasey
Senior Member
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.6
Posts: 3,451

Rep: Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157
Quote:
Originally Posted by rsmereka View Post
Sean,

The proftpd.conf I posted here is OOTB. It does not reflect any modifications.

I have documented every attempt:

1. comment out 'User', 'Group' and add 'UseFtpUsers'
2. make sure 'DefaultRoot ~' is uncommented
3. comment out the lines 'AuthPAMConfig' and 'AuthOrder' (not present in file)
4. add 'UseFtpUsers'

Logging in daemon mode is not the same as in debug mode and does not supply all the information.

Attempting to log onto the ftp server from the console results in exactly the same error.

This is a lan-based ftp server, connection is only from within the same subnet. The ftp server is not on the internet.

I am using the standard, no-frills, command line ftp client.

Rick
OK.
I'm not sure there's value in posting an OOTB config. We need to see the config you're using to help best.
That said:
Did you add UseFtpUser off? As I understand it, the ftpusers file is a list of user that are NOT allowed to ftp.
And can you log in at the console (not via ftp) with the user and password that's failing?

Another question: Why are you trying to run ftp at all? It's very insecure and pretty much obsolete. What is your need for ftp?
The recommended current tool to use for file transfer is sftp, which is built in to sshd and uses the same protocols as ssh login.
 
Old 07-16-2019, 11:37 AM   #7
rsmereka
Member
 
Registered: Jul 2003
Location: Southwestern Ontario, Canada
Distribution: LFS, Void, NuTyX, MX, OpenBSD, Mint, Gentoo
Posts: 48

Original Poster
Blog Entries: 3

Rep: Reputation: 15
Sean,

The alleged fix #1, third line to modify, I added the line:
Code:
UseFtpUsers off
I can log onto the console of the PC in question using the same user ID (not root) as I am using with ftp.

As previously mentioned, this is used inside a lan so (IMHO) there is no need for encryption or all that fancy stuff that would be required if the ftp server was internet facing. IMHO, ftp is still very essential.

Rick
 
Old 07-16-2019, 01:24 PM   #8
scasey
Senior Member
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.6
Posts: 3,451

Rep: Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157
I'm stumped then. Sorry.
 
Old 07-17-2019, 08:16 AM   #9
rsmereka
Member
 
Registered: Jul 2003
Location: Southwestern Ontario, Canada
Distribution: LFS, Void, NuTyX, MX, OpenBSD, Mint, Gentoo
Posts: 48

Original Poster
Blog Entries: 3

Rep: Reputation: 15
Sean,

Ok.

Thanks for trying.

Rick
 
Old 07-17-2019, 10:34 AM   #10
scasey
Senior Member
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.6
Posts: 3,451

Rep: Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157Reputation: 1157
Quote:
Originally Posted by rsmereka View Post
As previously mentioned, this is used inside a lan so (IMHO) there is no need for encryption or all that fancy stuff that would be required if the ftp server was internet facing. IMHO, ftp is still very essential.

Rick
One more thought: File Transfer is definitely essential, but ftp is not.

Are you using ssh to get to the server now? PuTTY from Windows?

If so, then there's no additional configuration to do. If now using ssh from another Linux box, just type sftp instead(see man sftp for how to specify server, user, and password) I have passwordless ssh configured to my server, so sftp servername just connects me...)

From Windows, you'd want to install WinSCP, which runs over the PuTTY engine, but again, you'd need to make no changes on the server side if you're already using PuTTY.

Just sayin'
 
Old 07-17-2019, 10:55 AM   #11
rsmereka
Member
 
Registered: Jul 2003
Location: Southwestern Ontario, Canada
Distribution: LFS, Void, NuTyX, MX, OpenBSD, Mint, Gentoo
Posts: 48

Original Poster
Blog Entries: 3

Rep: Reputation: 15
Sean,

None of the servers have ssh enabled,

So no, to get to the server command line, I walk over to the physical server and log on.

In regards to an ftp server for this NuTyX box, I am going to uninstall proftpd and compile vsftpd from source which all the other servers use (this should be very easy since NuTyX is based on LFS/BLFS, I will use BLFS to compile). Unfortunately, the developer of NuTyX does not have vsftpd in the repository. IMHO, vsftpd has almost zero config problems compared to proftpd.

Rick
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ProFTPD [530 Login incorrect] dmjendor Linux - General 0 11-11-2008 04:15 PM
Proftpd 1.3.0 under ubuntu : "530 Login incorrect" displayed on ftp client Hanzo Linux - Networking 3 07-24-2008 08:02 PM
Proftpd 530 Login Incorrect error besides correct password imagineers7 Linux - Networking 9 01-07-2008 02:13 AM
yum update proftpd 530 login incorrect westdoor Linux - Networking 1 10-29-2006 06:25 AM
ProFTPd on SuSE 9.1:Error 530 (Login Incorrect) bmctee Linux - Software 0 08-10-2004 12:21 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 08:28 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration