Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Pure-FTP ... Windows Umlaute Problem.

Hybrid View

  1. #1

    Default Pure-FTP ... Windows Umlaute Problem.

    Hi,

    ich suche schon länger nach einer lösung...


    Ich habe drei rechner local stehen...

    PC1: Linux Opensuse 11.3 als Pure-FTP server

    PC2: Windows XP und Windows 7 mit z.B. Filezilla

    PC3: und Opensuse 11.4 mit auch z.B. Filezilla


    Jedoch werden mir nur auf den Windowssystemen keine Umlaute angezeigt....
    auf PC3 aber schon


    Ich habe (auf PC1) auch die pureftpd config mehr mals versucht zu bearbeiten...
    sprich ClientCharset und FileCharset abwechseln und in vielen varianten verstellt...

    z.B. ClienCharset Windows-1252 oder auch UTF8 und co...

    doch bei einem Restart des FTP servers bekomme ich folgenden fehler:
    Shutting down pure-ftpd
    Starting pure-ftpd/usr/sbin/pure-ftpd: invalid option -- '9'
    startproc: exit status of parent of /usr/sbin/pure-ftpd: 252


    wen ich ClientCharset wieder auskommentiere kommt kein fehler mehr... grrr




    die config welche ich bearbeite liegt in /etc/pure-ftpd........





    HILFE

  2. #2
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    suseinlove wrote:

    > ClientCharset

    Kannst du die config Datei mal posten. Ich kenne pureftp jetzt nicht
    wirklich gut. Aber vielleicht ist es was furchtbar Banales wie ein
    Tippfehler, falsche Groß- oder Kleinschreibung in der config.

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.1 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | Gnome 2.32 | nVidia
    ION | 3GB Ram

  3. #3

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    hier noch mal die ausgabe der aktuellen config
    PHP Code:
    root:~ # rcpure-ftpd stop
    Shutting down pure-ftpd                                                                                 done
    root
    :~ # rcpure-ftpd start
    Starting pure-ftpd/usr/sbin/pure-ftpdinvalid option -- '9'
                                                                                                            
    done 

    Hier meine Config,
    ganz unten findet ihr das mit charset.
    Code:
    ############################################################
    #                                                          #
    #         Configuration file for pure-ftpd wrappers        #
    #                                                          #
    ############################################################
    
    # If you want to run Pure-FTPd with this configuration   
    # instead of command-line options, please run the
    # following command :
    #
    # /usr/sbin/pure-config.pl /usr/etc/pure-ftpd.conf
    #
    # Please don't forget to have a look at documentation at
    # http://www.pureftpd.org/documentation.shtml for a complete list of
    # options.
    
    # Cage in every user in his home directory
    
    ChrootEveryone              yes
    
    
    # If the previous option is set to "no", members of the following group
    # won't be caged. Others will be. If you don't want chroot()ing anyone,
    # just comment out ChrootEveryone and TrustedGID.
    
    # TrustedGID                    100
    
    
    # Turn on compatibility hacks for broken clients
    
    BrokenClientsCompatibility  no
    
    
    
    # Maximum number of simultaneous users
    
    MaxClientsNumber            10
    
    
    
    # Fork in background
    
    Daemonize                   yes
    
    
    
    # Maximum number of sim clients with the same IP address
    
    MaxClientsPerIP             4
    
    
    
    # If you want to log all client commands, set this to "yes".
    # This directive can be duplicated to also log server responses.
    
    VerboseLog                  no
    
    
    # Allow dot-files
    AllowDotFiles               no
    
    
    # List dot-files even when the client doesn't send "-a".
    
    DisplayDotFiles             no
    
    
    
    # Don't allow authenticated users - have a public anonymous FTP only.
    
    AnonymousOnly               no
    
    
    
    # Disallow anonymous connections. Only allow authenticated users.
    
    NoAnonymous                 yes
    
    
    
    # Syslog facility (auth, authpriv, daemon, ftp, security, user, local*)
    # The default facility is "ftp". "none" disables logging.
    
    SyslogFacility              ftp
    
    
    
    # Display fortune cookies
    
    # FortunesFile              /usr/share/fortune/zippy
    
    
    
    # Don't resolve host names in log files. Logs are less verbose, but 
    # it uses less bandwidth. Set this to "yes" on very busy servers or
    # if you don't have a working DNS.
    
    DontResolve                 yes
    
    
    
    # Maximum idle time in minutes (default = 15 minutes)
    
    MaxIdleTime                 15
    
    
    
    # LDAP configuration file (see README.LDAP)
    
    # LDAPConfigFile                /etc/pure-ftpd/pureftpd-ldap.conf
    
    
    
    # MySQL configuration file (see README.MySQL)
    
    # MySQLConfigFile               /etc/pure-ftpd/pureftpd-mysql.conf
    
    
    # Postgres configuration file (see README.PGSQL)
    
    # PGSQLConfigFile               /etc/pure-ftpd/pureftpd-pgsql.conf
    
    
    # PureDB user database (see README.Virtual-Users)
    
    # PureDB                        /etc/pure-ftpd/pureftpd.pdb
    
    
    # Path to pure-authd socket (see README.Authentication-Modules)
    
    # ExtAuth                       /var/run/ftpd.sock
    
    
    
    # If you want to enable PAM authentication, uncomment the following line
    
    PAMAuthentication             yes
    
    
    
    # If you want simple Unix (/etc/passwd) authentication, uncomment this
    
    # UnixAuthentication            yes
    
    
    
    # Please note that LDAPConfigFile, MySQLConfigFile, PAMAuthentication and
    # UnixAuthentication can be used only once, but they can be combined
    # together. For instance, if you use MySQLConfigFile, then UnixAuthentication,
    # the SQL server will be asked. If the SQL authentication fails because the
    # user wasn't found, another try # will be done with /etc/passwd and
    # /etc/shadow. If the SQL authentication fails because the password was wrong,
    # the authentication chain stops here. Authentication methods are chained in
    # the order they are given. 
    
    
    
    # 'ls' recursion limits. The first argument is the maximum number of
    # files to be displayed. The second one is the max subdirectories depth
    
    LimitRecursion              10000 8
    
    
    
    # Are anonymous users allowed to create new directories ?
    
    AnonymousCanCreateDirs      no
    
    
    
    # If the system is more loaded than the following value,
    # anonymous users aren't allowed to download.
    
    MaxLoad                     4
    
    
    
    # Port range for passive connections replies. - for firewalling.
    
    PassivePortRange                30000 30100
    
    
    
    # Force an IP address in PASV/EPSV/SPSV replies. - for NAT.
    # Symbolic host names are also accepted for gateways with dynamic IP
    # addresses.
    
    # ForcePassiveIP                192.168.0.1
    
    
    
    # Upload/download ratio for anonymous users.
    
    # AnonymousRatio                1 10
    
    
    
    # Upload/download ratio for all users.
    # This directive superscedes the previous one.
    
    # UserRatio                 1 10
    
    
    
    # Disallow downloading of files owned by "ftp", ie.
    # files that were uploaded but not validated by a local admin.
    
    AntiWarez                   yes
    
    
    
    # IP address/port to listen to (default=all IP and port 21).
    
    # Bind                      127.0.0.1,21
    
    
    
    # Maximum bandwidth for anonymous users in KB/s
    
    AnonymousBandwidth            1
    
    
    
    # Maximum bandwidth for *all* users (including anonymous) in KB/s
    # Use AnonymousBandwidth *or* UserBandwidth, both makes no sense.
    
    # UserBandwidth             8
    
    
    
    # File creation mask. <umask for files>:<umask for dirs> .
    # 177:077 if you feel paranoid.
    
    Umask                       177:077
    
    
    
    # Minimum UID for an authenticated user to log in.
    
    MinUID                      40
    
    
    
    # Allow FXP transfers for authenticated users.
    
    AllowUserFXP                no
    
    
    
    # Allow anonymous FXP for anonymous and non-anonymous users.
    
    AllowAnonymousFXP           no
    
    
    
    # Users can't delete/write files beginning with a dot ('.')
    # even if they own them. If TrustedGID is enabled, this group
    # will have access to dot-files, though.
    
    ProhibitDotFilesWrite       yes
    
    
    
    # Prohibit *reading* of files beginning with a dot (.history, .ssh...)
    
    ProhibitDotFilesRead        no
    
    
    
    # Never overwrite files. When a file whoose name already exist is uploaded,
    # it get automatically renamed to file.1, file.2, file.3, ...
    
    AutoRename                  no
    
    
    
    # Disallow anonymous users to upload new files (no = upload is allowed)
    
    AnonymousCantUpload         no
    
    
    
    # Only connections to this specific IP address are allowed to be
    # non-anonymous. You can use this directive to open several public IPs for
    # anonymous FTP, and keep a private firewalled IP for remote administration.
    # You can also only allow a non-routable local IP (like 10.x.x.x) to
    # authenticate, and keep a public anon-only FTP server on another IP.
    
    #TrustedIP                  10.1.1.1
    
    
    
    # If you want to add the PID to every logged line, uncomment the following
    # line.
    
    #LogPID                     yes
    
    
    
    # Create an additional log file with transfers logged in a Apache-like format :
    # fw.c9x.org - jedi [13/Dec/1975:19:36:39] "GET /ftp/linux.tar.bz2" 200 21809338
    # This log file can then be processed by www traffic analyzers.
    
    # AltLog                     clf:/var/log/pureftpd.log
    
    
    
    # Create an additional log file with transfers logged in a format optimized
    # for statistic reports.
    
    # AltLog                     stats:/var/log/pureftpd.log
    
    
    
    # Create an additional log file with transfers logged in the standard W3C
    # format (compatible with most commercial log analyzers)
    
    # AltLog                     w3c:/var/log/pureftpd.log
    
    
    
    # Disallow the CHMOD command. Users can't change perms of their files.
    
    # NoChmod                     yes
    
    
    
    # Allow users to resume and upload files, but *NOT* to delete them.
    
    #KeepAllFiles                yes
    
    
    
    # Automatically create home directories if they are missing
    
    #CreateHomeDir               yes
    
    
    
    # Enable virtual quotas. The first number is the max number of files.
    # The second number is the max size of megabytes.
    # So 1000:10 limits every user to 1000 files and 10 Mb.
    
    #Quota                       1000:10
    
    
    
    # If your pure-ftpd has been compiled with standalone support, you can change
    # the location of the pid file. The default is /var/run/pure-ftpd.pid
    
    #PIDFile                     /var/run/pure-ftpd.pid
    
    
    
    # If your pure-ftpd has been compiled with pure-uploadscript support,
    # this will make pure-ftpd write info about new uploads to
    # /var/run/pure-ftpd.upload.pipe so pure-uploadscript can read it and
    # spawn a script to handle the upload.
    
    #CallUploadScript yes
    
    
    
    # This option is useful with servers where anonymous upload is 
    # allowed. As /var/ftp is in /var, it save some space and protect 
    # the log files. When the partition is more that X percent full,
    # new uploads are disallowed.
    
    MaxDiskUsage               99
    
    
    
    # Set to 'yes' if you don't want your users to rename files.
    
    NoRename                  no
    
    
    
    # Be 'customer proof' : workaround against common customer mistakes like
    # 'chmod 0 public_html', that are valid, but that could cause ignorant
    # customers to lock their files, and then keep your technical support busy
    # with silly issues. If you're sure all your users have some basic Unix
    # knowledge, this feature is useless. If you're a hosting service, enable it.
    
    CustomerProof              yes
    
    
    
    # Per-user concurrency limits. It will only work if the FTP server has
    # been compiled with --with-peruserlimits (and this is the case on
    # most binary distributions) .
    # The format is : <max sessions per user>:<max anonymous sessions>
    # For instance, 3:20 means that the same authenticated user can have 3 active
    # sessions max. And there are 20 anonymous sessions max.
    
    PerUserLimits            40:0
    
    
    
    # When a file is uploaded and there is already a previous version of the file
    # with the same name, the old file will neither get removed nor truncated.
    # Upload will take place in a temporary file and once the upload is complete,
    # the switch to the new version will be atomic. For instance, when a large PHP
    # script is being uploaded, the web server will still serve the old version and
    # immediatly switch to the new one as soon as the full file will have been
    # transfered. This option is incompatible with virtual quotas.
    
    # NoTruncate               yes
    
    
    
    # This option can accept three values :
    # 0 : disable SSL/TLS encryption layer (default).
    # 1 : accept both traditional and encrypted sessions.
    # 2 : refuse connections that don't use SSL/TLS security mechanisms,
    #     including anonymous sessions.
    # Do _not_ uncomment this blindly. Be sure that :
    # 1) Your server has been compiled with SSL/TLS support (--with-tls),
    # 2) A valid certificate is in place,
    # 3) Only compatible clients will log in.
    
    # TLS                      1
    
    
    
    # Listen only to IPv4 addresses in standalone mode (ie. disable IPv6)
    # By default, both IPv4 and IPv6 are enabled.
    
    # IPV4Only                 yes
    
    
    
    # Listen only to IPv6 addresses in standalone mode (ie. disable IPv4)
    # By default, both IPv4 and IPv6 are enabled.
    
    # IPV6Only                 yes
    
    # UTF-8 support for file names (RFC 2640)
    # Define charset of the server filesystem and optionnally the default charset
    # for remote clients if they don't use UTF-8.
    # Works only if pure-ftpd has been compiled with --with-rfc2640
    
    #FileSystemCharset        UTF8
    ClientCharset            big5
    rcpure-ftpd start --with-rfc2640

    habe ich mal ausprobiert... aberdas gab keine änderung.



    thx vor help
    Last edited by pistazienfresser; 04-Apr-2011 at 07:31. Reason: Lesbarkeit: Habe die config Datei in CODE tags (-> oben #) gesetzt

  4. #4

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    ps: der fehler taucht nicht mehr auf wen ich das charset auskomentiere

  5. #5
    Join Date
    Sep 2008
    Location
    Sulzbach (Taunus), Hessen [Hesse], Deutschland [Germany]
    Posts
    2,178

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    Hallo suseinlove,

    danke für die (wenn ich es richtig verstehe) Erfolgsmeldung.

    Quote Originally Posted by suseinlove View Post
    ps: der fehler taucht nicht mehr auf wen ich das charset auskomentiere
    Nur damit ich (und andere von ähnlich begrenzter Auffassungsgabe) das auch verstehen:

    Also das Problem tritt nicht auf, nachdem Du statt
    Code:
    [...]
    # UTF-8 support for file names (RFC 2640)
    # Define charset of the server filesystem and optionnally the default charset
    # for remote clients if they don't use UTF-8.
    # Works only if pure-ftpd has been compiled with --with-rfc2640
    
    #FileSystemCharset        UTF8
    ClientCharset            big5
    (# von mir rot gemacht)
    Folgendes konfiguriert hast:
    Code:
    [...]
    # UTF-8 support for file names (RFC 2640)
    # Define charset of the server filesystem and optionnally the default charset
    # for remote clients if they don't use UTF-8.
    # Works only if pure-ftpd has been compiled with --with-rfc2640
    
    FileSystemCharset        UTF8
    ClientCharset            big5
    ?

    Have a lot of fun!
    Martin
    (pistazienfresser)
    [Hatte das eigentlich eine besondere Bedeutung, dass auf das # kein Leerzeichen folgte?]

  6. #6
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    suseinlove wrote:

    >
    > ps: der fehler taucht nicht mehr auf wen ich das charset auskomentiere
    >

    Wieso eigentlich big5, ich dachte es geht um Umlaute nicht um chinesische
    Schriftzeichen. Kriegst du auch einen Fehler, wenn du das ClientCharset auch
    mal testweise auf UTF8 setzt?

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.1 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | Gnome 2.32 | nVidia
    ION | 3GB Ram

  7. #7

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    also das problem besteht weiterhin...

    PHP Code:
    THP-Prester-FTP:~ # rcpure-ftpd restart
    Shutting down pure-ftpd                                                                                 done
    Starting pure
    -ftpd/usr/sbin/pure-ftpdinvalid option -- '9'
                                                                                                            
    done 
    habe jetzt UTF8 verwenden
    PHP Code:
    ClientCharset            UTF8 

    BIG5 war nur mein letzter verzweifelter versuch... ich habe auch schon diverse ISO codes durch :/

    sprich ich hab keine ahnung was ich machen soll...

  8. #8
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    suseinlove wrote:

    >
    > also das problem besteht weiterhin...
    >
    >

    Sonderbar ich konnte heute dein Problem reproduzieren indem ich big5 gesetzt
    hatte (gleiche Fehlermeldung), beim Testen mit utf8 ist der Daemon
    problemlos gestartet.

    Code:
    /etc/pure-ftpd/pure-ftpd.conf
    
    FileSystemCharset       UTF8
    ClientCharset           UTF8
    
    martinh@sirius:~> sudo /usr/sbin/rcpure-ftpd start
    Starting pure-ftpd
    done
    Dann muss noch irgendwas anderes sein, nur was?

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.1 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | Gnome 2.32 | nVidia
    ION | 3GB Ram

  9. #9

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    grml....

    ich finds cool von dir das du dir die mühe gemacht hast den fehler zu reproduzieren DANKE!


    Aber wen du den server nochmal restartest kann es sein das der fehler erst auftritt... (ich hab es auch schon auf meiner anderen Linux kiste versuch selber fehler)
    wen der fehler bei dir dennoch nicht auftritt, änder bitte noch mal die config und versuch ihn dann noch mal zu starten... kommt dann ein fehler mit UTF8 ?
    Alternativ kannst du mal... windows-1252 bzw. Windows-1252 ausprobieren... bei mir kamm lediglich der selbe fehler :7

    kannst du evtl mal testen ob bei dir mit Filezilla oder Netzlaufwerkverbinden unter Windows XP oder Win 7 die umlaute angezeigt werden?



    Ich bemühe mich weiterhin nach einer lösung... sollte ich was finden hört ihr aufjedenfall von mir.

    ein umstieg auf ein anderes FTP programm möchte ich gerne vermeiden, aber ich denke schon langsam in die richtung ^^


    aber der umlaute fehler muss doch zu beseitigen sein...


    gruß

  10. #10
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Pure-FTP ... Windows Umlaute Problem.

    Das sieht ziemlich sonderbar aus, ich habe jetzt den Dienst nochmal
    gestartet (mit unveränderter Einstellung, also jeweils UTF8) und dann kommt
    der Fehler und es startet nicht. Starte ich dann gleich nochmal ohne etwas
    zu ändern geht es plötzlich beim zweiten mal (sieht ein wenig nach einem Bug
    aus).

    Mit Windows testen kann ich erst heute abend nach der Arbeit, habe nur einen
    Rechner den ich mit Dualboot laufen lasse (win 7), für Windows wird man dann
    wohl als ClientCharset 8859-1 bzw. cp1252 brauchen.

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.1 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | Gnome 2.32 | nVidia
    ION | 3GB Ram

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •