www.ProFTPD.de
13. März 2007, 21:23:58 *
Willkommen Gast. Bitte einloggen oder registrieren.
Haben Sie Ihre Aktivierungs E-Mail übersehen?

Einloggen mit Benutzername, Passwort und Sitzungslänge
News: SMF - Neu installiert!
 
  Übersicht Hilfe Suche Login Registrieren  
  Zeige Beiträge
Seiten: [1]
1  ProFTPD / ProFTPD - Deutsch / ProFTPD 1.2.9 - Kein Login möglich am: 10. Februar 2004, 13:40:25
Blöder beknackter Fehler !

Die Rechte des Verzeichnisses /etc waren falsch !
Nun ist alles in bester Ordnung
2  ProFTPD / ProFTPD - Deutsch / ProFTPD 1.2.9 - Kein Login möglich am: 10. Februar 2004, 10:31:58
Hat sich erledigt ! Hab mir mit ftpasswd eine eigene passwd datei gemacht und aus /etc rausgeholt !

Danke trotzdem
3  ProFTPD / ProFTPD - Deutsch / ProFTPD 1.2.9 - Kein Login möglich am: 10. Februar 2004, 10:01:15
Alright,

hier noch ein paar Infos.

Die Rechte der passwd

Code:
-rw-r--r--    1 root     root         1384 Feb 10 01:35 passwd


und meine proftpd.conf
Code:
# This is a basic ProFTPD configuration file (rename it to
# 'proftpd.conf' for actual use.  It establishes a single server
# and a single anonymous login.  It assumes that you have a user/group
# "nobody/nogroup" and "ftp" for normal operation and anon.

ServerName                      "FTP Server"
ServerType                      standalone
DeferWelcome                    off

MultilineRFC2228                on
DefaultServer                   on
ShowSymlinks                    on
AllowOverwrite                  on

TimeoutNoTransfer               600
TimeoutStalled                  600
TimeoutIdle                     1200

DisplayLogin                    welcome.msg
DisplayFirstChdir               .message
ListOptions                     "-l"

DenyFilter                      \*.*/

#
# Do a chroot for web-users (i.e. public or www group), but
# do not change root if the user is also in the users group...
#








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

# Uncomment this if you would use TLS module:
#TLSEngine                      on

# Uncomment this if you would use quota module:
#Quotas                         on

# Uncomment this if you would use ratio module:
#Ratios                         on

# Port 21 is the standard FTP port.
Port                            21

# 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                            nobody
Group                           nogroup

<Directory /*>
# 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
</Directory>

# 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
#
#   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
#   DisplayFirstChdir           .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>


Ich hoffe das hilft weiter.
Dankeschön
4  ProFTPD / ProFTPD - Deutsch / ProFTPD 1.2.9 - Kein Login möglich am: 10. Februar 2004, 09:38:51
Moin Stonki,

danke für Deine sehr hilfreiche Antwort !
Aber wie kann es sein das der Proftpd keinen Zugriff auf die passwd hat ?

Ich führe den proftpd als root aus.

Linux ist für mich eben noch relatives Neuland, ich wußte nicht das ich das im Thread gleich zu Beginn hätte schreiben müssen !
5  ProFTPD / ProFTPD - Deutsch / ProFTPD 1.2.9 - Kein Login möglich am: 10. Februar 2004, 00:48:32
Hi zusammen,

habe hier auf meinem DEBIAN PC Proftpd 1.2.9 laufen.

User sind unter Linux angelegt, allerdings ist kein Login möglich.

das gibt mir der gute proftpd aus :
Code:

wachtelserver (192.168.0.94[192.168.0.94]) - connected - local  : 192.168.0.1:21
wachtelserver (192.168.0.94[192.168.0.94]) - connected - remote : 192.168.0.94:1185
wachtelserver (192.168.0.94[192.168.0.94]) - FTP session opened.
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'USER matze' to mod_rewrite
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'USER matze' to mod_tls
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'USER matze' to mod_core
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'USER matze' to mod_core
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'USER matze' to mod_auth
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching CMD command 'USER matze' to mod_ratio
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching CMD command 'USER matze' to mod_auth
wachtelserver (192.168.0.94[192.168.0.94]) - Unable to open password file /etc/passwd for reading: Permission denied
wachtelserver (192.168.0.94[192.168.0.94]) - Unable to open password file /etc/passwd for reading: Permission denied
wachtelserver (192.168.0.94[192.168.0.94]) - no supplemental groups found for user 'matze'
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching LOG_CMD command 'USER matze' to mod_log
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_rewrite
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_tls
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_core
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_core
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_wrap
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_radius
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_auth
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching CMD command 'PASS (hidden)' to mod_auth
wachtelserver (192.168.0.94[192.168.0.94]) - Unable to open password file /etc/passwd for reading: Permission denied
wachtelserver (192.168.0.94[192.168.0.94]) - Unable to open password file /etc/passwd for reading: Permission denied
wachtelserver (192.168.0.94[192.168.0.94]) - no supplemental groups found for user 'matze'
wachtelserver (192.168.0.94[192.168.0.94]) - Unable to open password file /etc/passwd for reading: Permission denied
wachtelserver (192.168.0.94[192.168.0.94]) - Unable to open password file /etc/passwd for reading: Permission denied
wachtelserver (192.168.0.94[192.168.0.94]) - no such user 'matze'
wachtelserver (192.168.0.94[192.168.0.94]) - USER matze: no such user found from 192.168.0.94 [192.168.0.94] to 192.168.0.1:21
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_log
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_auth
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'QUIT' to mod_rewrite
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'QUIT' to mod_tls
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'QUIT' to mod_core
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'QUIT' to mod_core
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching PRE_CMD command 'QUIT' to mod_log
wachtelserver (192.168.0.94[192.168.0.94]) - dispatching CMD command 'QUIT' to mod_core
wachtelserver (192.168.0.94[192.168.0.94]) - FTP session closed.


Es gibt diesen User aber definitiv !
Woran kann es liegen ? Welche Infos braucht ihr noch ?

Vielen Dank im Voraus
Seiten: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Prüfe XHTML 1.0 Prüfe CSS
Seite erstellt in 0.087 Sekunden mit 16 Zugriffen.