Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
2724 connectés 

  FORUM HardWare.fr
  Linux et OS Alternatifs
  réseaux et sécurité

  Configuration pour un répertoire d'upload avec Pure-Ftp

 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

Configuration pour un répertoire d'upload avec Pure-Ftp

n°751598
youmoussa
Ecrou-vis
Posté le 12-11-2005 à 20:31:32  profilanswer
 

J'ai monté un serveur sous linux (Mdk LE 2005) pour débuter, et je me suis installé pure-ftp comme serveur ftp.
 
Tout fonctionne comme je le souhaite, mais je n'arrive pas à créer/configurer le tout pour avoir un répertoire d'upload.
 
Mon répertoire Upload appartient à l'utilisateur 500 et au groupe 501, avec les droits drwxrwxr-x
 
Mon ftp fonctionne avec des utilisateurs virtuels basés sur l'utilisateur 501/501.
 
Quand j'upload dans mon répertoire avec kBear, ca me marque que le transfert a réussi, mais que chmod rate car le fichier n'existe pas..
 
Si une ame charitable était à même de m'aider..
 
Voilà mon pure-ftpd.conf
 


############################################################
#                                                          #
#         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 /etc/pure-ftpd/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  yes
 
 
 
# Maximum number of simultaneous users
 
MaxClientsNumber            4
 
 
 
# Fork in background
 
Daemonize                   yes
 
# Maximum clients
Clients                     4
 
# Maximum number of sim clients with the same IP address
 
MaxClientsPerIP             2
 
 
 
# If you want to log all client commands, set this to "yes".
# This directive can be duplicated to also log server responses.
 
VerboseLog                  yes
 
 
 
# 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                 no
 
# Maximum idle time in minutes (default = 15 minutes)
 
MaxIdleTime                 5
 
 
 
# 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             no
 
 
 
# 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              2000 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 50000
 
 
 
# 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            8
 
 
 
# 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                       133:022
 Umask                       777:000
 
 
 
# Minimum UID for an authenticated user to log in.
 
MinUID                      500
 
 
 
# 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        yes
 
 
 
# Never overwrite files. When a file whoose name already exist is uploaded,
# it get automatically renamed to file.1, file.2, file.3, ...
 
AutoRename                  yes
 
 
 
# Disallow anonymous users to upload new files (no = upload is allowed)
 
AnonymousCantUpload         yes
 
 
 
# 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                  yes
 
 
 
# 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            3:20
 
 
 
# 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


Message édité par youmoussa le 14-11-2005 à 11:02:53

---------------
L'humain est celui « qui agit puis qui pense : ce n’est pas parce qu’il soutient telle position qu’il agit de telle manière, mais parce qu’il a agi (comme il a été amené à le faire) qu’il va adopter telle position
mood
Publicité
Posté le 12-11-2005 à 20:31:32  profilanswer
 

n°752037
youmoussa
Ecrou-vis
Posté le 14-11-2005 à 11:02:35  profilanswer
 

Petit up du lundi matin..


---------------
L'humain est celui « qui agit puis qui pense : ce n’est pas parce qu’il soutient telle position qu’il agit de telle manière, mais parce qu’il a agi (comme il a été amené à le faire) qu’il va adopter telle position
n°752750
youmoussa
Ecrou-vis
Posté le 16-11-2005 à 09:28:20  profilanswer
 

Petit up du mercredi  :sweat:


---------------
L'humain est celui « qui agit puis qui pense : ce n’est pas parce qu’il soutient telle position qu’il agit de telle manière, mais parce qu’il a agi (comme il a été amené à le faire) qu’il va adopter telle position

Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Linux et OS Alternatifs
  réseaux et sécurité

  Configuration pour un répertoire d'upload avec Pure-Ftp

 

Sujets relatifs
configuration parfeu shorewall et squidQuel configuration réseau me conseillez vous ?
[CONFIGURATION freebox usb Debian ]problème de configuration de samba
Configuration Apache et virtual hosting HELPconfiguration modem sous linux ?
chmod 777 sur tous nouveau fichier d'un répertoirerepertoire ou fichier ? pas supprimable [vfat]
configuration de touches "multimédia" sur un clavier ?problème configuration fstab
Plus de sujets relatifs à : Configuration pour un répertoire d'upload avec Pure-Ftp


Copyright © 1997-2022 Hardware.fr SARL (Signaler un contenu illicite / Données personnelles) / Groupe LDLC / Shop HFR