Proftpd server auf lokalen debian 6 server einrichten

xzillen

Member
Hallo

Ich habe mal ne frage

Ich habe hier auf einen pc debian 6 installiert

mit apache 2 mit php5

auf den server lauft webmin

das lauft auch

nur das problem habe ich mit den FTP server

Server : proftpd

die installation des FTP server ging ohne Probleme

nur wenn ich einen Benutzer anlegen für den FTP server

dann kann der Benutzer sich nicht auf den ftp server einlogen

da kommt immer die meldung : Response: 530 Login incorrect.

obwohl die die benutzer daten richtig ins ftp progrmm eingetragen wurden

was kann das sein
 
Last edited by a moderator:
Bitte mehr Infos: wie hast du die FTP angelegt/eingetragen? Wie sieht die Proftpd Config aus?

wie hast du die FTP angelegt/eingetragen?

Die Ftp Benutzer habe ich über webmin angelegt

Wie sieht die Proftpd Config aus?
PHP:
#
# /etc/proftpd/proftpd.conf -- This is a basic ProFTPD configuration file.
# To really apply changes reload proftpd after modifications.
# 

# Includes DSO modules
Include /etc/proftpd/modules.conf

# Set off to disable IPv6 support which is annoying on IPv4 only boxes.
UseIPv6				on
# If set on you can experience a longer connection delay in many cases.
IdentLookups off

ServerName			"Debian"
ServerType			standalone
DeferWelcome off

MultilineRFC2228		on
DefaultServer on
ShowSymlinks on

TimeoutNoTransfer		600
TimeoutStalled			600
TimeoutIdle			1200

DisplayLogin welcome.msg
DisplayChdir .message true
ListOptions "-l"

DenyFilter			\*.*/

# Use this to jail all users in their homes 
# DefaultRoot 

# Users require a valid shell listed in /etc/shells to login.
# Use this directive to release that constrain.
# RequireValidShell		off

# Port 21 is the standard FTP port.

# In some cases you have to specify passive ports range to by-pass
# firewall limitations. Ephemeral ports can be used for that, but
# feel free to use a more narrow range.
# PassivePorts                  49152 65534

# If your host was NATted, this option is useful in order to
# allow passive tranfers to work. You have to use your public
# address and opening the passive ports used on your firewall as well.
# MasqueradeAddress		1.2.3.4

# This is useful for masquerading address with dynamic IPs:
# refresh any configured MasqueradeAddress directives every 8 hours
<IfModule mod_dynmasq.c>
# DynMasqRefresh 28800
</IfModule>

# 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)
MaxInstances			30

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

# Umask 022 is a good standard umask to prevent new files and dirs
# (second parm) from being group and world writable.
Umask 022 022
# Normally, we want files to be overwriteable.
AllowOverwrite			on

# Uncomment this if you are using NIS or LDAP via NSS to retrieve passwords:
# PersistentPasswd		off

# This is required to use both PAM-based authentication and local passwords
# AuthOrder			mod_auth_pam.c* mod_auth_unix.c

# Be warned: use of this directive impacts CPU average load!
# Uncomment this if you like to see progress and transfer rate with ftpwho
# in downloads. That is not needed for uploads rates.
#
# UseSendFile			off

TransferLog /var/log/proftpd/xferlog
SystemLog   /var/log/proftpd/proftpd.log
Port 21

<IfModule mod_quotatab.c>
QuotaEngine off
</IfModule>

<IfModule mod_ratio.c>
Ratios off
</IfModule>


# Delay engine reduces impact of the so-called Timing Attack described in
# http://security.lss.hr/index.php?page=details&ID=LSS-2004-10-02
# It is on by default. 
<IfModule mod_delay.c>
DelayEngine on
</IfModule>

<IfModule mod_ctrls.c>
ControlsEngine        off
ControlsMaxClients    2
ControlsLog           /var/log/proftpd/controls.log
ControlsInterval      5
ControlsSocket        /var/run/proftpd/proftpd.sock
</IfModule>

<IfModule mod_ctrls_admin.c>
AdminControlsEngine off
</IfModule>

#
# Alternative authentication frameworks
#
#Include /etc/proftpd/ldap.conf
#Include /etc/proftpd/sql.conf

#
# This is used for FTPS connections
#
#Include /etc/proftpd/tls.conf

#
# Useful to keep VirtualHost/VirtualRoot directives separated
#
#Include /etc/proftpd/virtuals.con

# A basic anonymous configuration, no upload directories.

# <Anonymous ~ftp>
#   User				ftp
#   Group				nogroup
#   # We want clients to be able to login with "anonymous" as well as "ftp"
#   UserAlias			anonymous ftp
#   # Cosmetic changes, all files belongs to ftp user
#   DirFakeUser	on ftp
#   DirFakeGroup on ftp
# 
#   RequireValidShell		off
# 
#   # Limit the maximum number of anonymous logins
#   MaxClients			10
# 
#   # We want 'welcome.msg' displayed at login, and '.message' displayed
#   # in each newly chdired directory.
#   DisplayLogin			welcome.msg
#   DisplayChdir		.message
# 
#   # Limit WRITE everywhere in the anonymous chroot
#   <Directory *>
#     <Limit WRITE>
#       DenyAll
#     </Limit>
#   </Directory>
# 
#   # Uncomment this if you're brave.
#   # <Directory incoming>
#   #   # Umask 022 is a good standard umask to prevent new files and dirs
#   #   # (second parm) from being group and world writable.
#   #   Umask				022  022
#   #            <Limit READ WRITE>
#   #            DenyAll
#   #            </Limit>
#   #            <Limit STOR>
#   #            AllowAll
#   #            </Limit>
#   # </Directory>
# 
# </Anonymous>
<Global>
</Global>
 
Hey,

ich grabe hier mal bissl ;)

Falls du das Problem immnoch haben solltest, seh mal bitte nach ob der User wirklich ganz normal erstellt wurde:
Code:
cat /etc/passwd | grep HierDer Nutzername
Und ich würde dir dazu auf jeden fall empfehlen folgende Option zu setzen (also einkommentieren):
Code:
[COLOR=#000000][COLOR=#FF8000]DefaultRoot[/COLOR][/COLOR]
Diese bewirkt, dass der User per FTP in seinem Homeverzeichnis chrooted ist, sich also nicht dor heraus bewegen kann und andere Sachen machen/sehen kann.

Und falls der User zwar eingetragen ist, aber als Shell z.B. /bin/false eingetragen hat, schenke doch einmal dieser Option deine Aufmerksamkeit:

Code:
[COLOR=#000000][COLOR=#FF8000]# Users require a valid shell listed in /etc/shells to login. 
# Use this directive to release that constrain. 
# RequireValidShell        off [/COLOR][/COLOR]
Diese würde ihn dann nämlich am Login hindern.

Und am simpelsten das Passwort einfach noch einmal neu setzen :rolleyes:
Code:
sudo passwd HierDerUsername
Grüße
 
@Xzillen

Im
Interesse
einer
besseren
Lesbarkeit
bitte
von
eigenen
Umbrüchen
nach
jedem
Satz
absehen.

Danke.:p
 
Back
Top