FTP permissies
Ik ben net klaar met het succesvol installeren van LAMP, PHPMyAdmin en VSFTPD en nu wil ik een map aanmaken via Filezilla. Verbinding maken doe ik met de gegevens die ik bij het installeren van de Ubuntu Server heb opgegeven. Het enige probleem is dat ik geen mappen / bestanden kan aanmaken, wijzigen en verwijderen, ik kan ze alleen bekijken.
Nu weet ik dat ik mezelf waarschijnlijk rechten moet geven om dit te kunnen doen, maar ik kan nergens vinden hoe ik dit precies moet doen.
Kan iemand me hiermee helpen?
Alvast bedankt!
Edit:
Dit is mijn huidige /etc/vsftpd.conf:
Code (php)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
# Example config file /etc/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
#
# Run standalone? vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=YES
#
# Run standalone with IPv6?
# Like the listen parameter, except vsftpd will listen on an IPv6 socket
# instead of an IPv4 one. This parameter and the listen parameter are mutually
# exclusive.
#listen_ipv6=YES
#
# Allow anonymous FTP? (Disabled by default)
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
# anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# If enabled, vsftpd will display directory listings with the time
# in your local time zone. The default is to display GMT. The
# times returned by the MDTM FTP command are also affected by this
# option.
use_localtime=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd.banned_emails
#
# You may restrict local users to their home directories. See the FAQ for
# the possible risks in this before using chroot_local_user or
# chroot_list_enable below.
#chroot_local_user=YES
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that
# the user does not have write access to the top level directory within the
# chroot)
#chroot_local_user=YES
#chroot_list_enable=YES
# (default follows)
#chroot_list_file=/etc/vsftpd.chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# Customization
#
# Some of vsftpd's settings don't fit the filesystem layout by
# default.
#
# This option should be the name of a directory which is empty. Also, the
# directory should not be writable by the ftp user. This directory is used
# as a secure chroot() jail at times vsftpd does not require filesystem
# access.
secure_chroot_dir=/var/run/vsftpd/empty
#
# This string is the name of the PAM service vsftpd will use.
pam_service_name=vsftpd
#
# This option specifies the location of the RSA certificate to use for SSL
# encrypted connections.
rsa_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
# This option specifies the location of the RSA key to use for SSL
# encrypted connections.
rsa_private_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
#
# Run standalone? vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=YES
#
# Run standalone with IPv6?
# Like the listen parameter, except vsftpd will listen on an IPv6 socket
# instead of an IPv4 one. This parameter and the listen parameter are mutually
# exclusive.
#listen_ipv6=YES
#
# Allow anonymous FTP? (Disabled by default)
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
# anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# If enabled, vsftpd will display directory listings with the time
# in your local time zone. The default is to display GMT. The
# times returned by the MDTM FTP command are also affected by this
# option.
use_localtime=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd.banned_emails
#
# You may restrict local users to their home directories. See the FAQ for
# the possible risks in this before using chroot_local_user or
# chroot_list_enable below.
#chroot_local_user=YES
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that
# the user does not have write access to the top level directory within the
# chroot)
#chroot_local_user=YES
#chroot_list_enable=YES
# (default follows)
#chroot_list_file=/etc/vsftpd.chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# Customization
#
# Some of vsftpd's settings don't fit the filesystem layout by
# default.
#
# This option should be the name of a directory which is empty. Also, the
# directory should not be writable by the ftp user. This directory is used
# as a secure chroot() jail at times vsftpd does not require filesystem
# access.
secure_chroot_dir=/var/run/vsftpd/empty
#
# This string is the name of the PAM service vsftpd will use.
pam_service_name=vsftpd
#
# This option specifies the location of the RSA certificate to use for SSL
# encrypted connections.
rsa_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
# This option specifies the location of the RSA key to use for SSL
# encrypted connections.
rsa_private_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
Gewijzigd op 23/10/2014 21:40:03 door Lord Gaga
De map waar je in zit (root map) moet wel de rechten 775 hebben en zowel user als group moeten overeenkomen als de user die inlogd.
Het beste is om de, in jou geval, gehele www map de rechten te geven.
Code (php)
1
chmod -R 775 /var/www/
Daarnaast moet je kijken welke user er inlogd. De user en usergroup kan je wijzigen met het commando "chown".
Code (php)
1
chown -R user:usergroup /var/www/
Stel dat ik inlog met de gebruikersnaam "test", hoe weet ik dan onder welke usergroup dat account valt?
Code (php)
1
groups userName-Here
Dit zal de groepen weergeven waar de gebruiker in zit.
Wat wel van belang is is dat de ftp client (deamon) toegang heeft tot de groep.
Voorbeeld;
test:ftp
De user is dan test en de groep is ftp, dit zal je aan kunnen geven of opzoeken.
Hier een link waarbij er verschillende elementen worden toegelicht over mappen, users, groups en rechten.
http://codex.wordpress.org/Changing_File_Permissions
Code (php)
1
2
2
sudo usermod -a -G usergroup user
sudo chown -R user:usergroup /var/www/
sudo chown -R user:usergroup /var/www/
Edit:
Ik heb het volgende gedaan:
Code (php)
1
2
2
sudo adduser ftp test
sudo chown -R test:test /var/www
sudo chown -R test:test /var/www
Is dit de goede manier? En kan het kloppen dat de username in een usergroup zit met dezelfde naam?
Gewijzigd op 23/10/2014 22:26:12 door Lord Gaga
Als de map van owner jan is en group apache en chmod 750 gedaan is,
Dan kan user jan, die alleen in group jannen zit prima schrijven in die map.
De user apache, die ook in de griup apache zit, kan alleen lezen in die map, vanwege de group-rechten 5.
Others hebben rechten 0
Doorgaans zal user foo ook in de group foo zitten trouwens
Gewijzigd op 24/10/2014 00:03:22 door Lord Gaga
group: users
en het is een directory:
chmod 770
de user jan kan schrijven in deze dir
Piet zit ook in de group Users. Die kan dus ook alles.
chmod 750
Jan kan nog steeds alles
Piet kan nog wel lezen, maar niet meer schrijven.
chmod 570
Jan kan nog steeds alles, op basis van zijn group-lidmaatschap.
Piet zit ook in die group, en kan ook weer alles.
chgrp root
Piet kan niets meer, want hij is geen lid van de group Root.
Jan is ook geen lid van de group root, en moet dus kijken naar alleen zijn eigen rechten: 5
chmod 750
Piet nog steeds buiten de boot.
Jan heeft nu 7 en kan weer alles.
chown Kees
De map is nu van Kees.
Jan is niet kees, en hij is nog steeds niet lid van de group Root. Kan dus niets
Piet idem
chmod 775
Kees alles
Jan en Piet vallen beide onder others: dus daarmee 5
Je kijkt dus naar de mogelijkheid waarmee een user wel iets kan doen.
Zo kun je ook opzetten:
mkdir pdf
chown me:apache pdf
chmod 770 pdf
daarmee heb je een map waar je zelf nog steeds van alles mee kunt, maar ook apache (= php) aangenomen dat apache onder de group Apache draait. (is ook wel httpd of wwwrun, afhankelijk van de voorkeur van je systeembeheerder of je linux distro)
Danku Ivo
Ivo P op 24/10/2014 13:12:58:
Inderdaad, handig. Met name ook voor inbraakpogingen. 95% van de inbraakmogelijkheden wordt veroorzaakt door beheerders en developers die dingen wel 'handig' vinden.voor een file wel, maar om in een map te kunnen schrijven is 7 --voor die user/group-- wel handig...
Code (php)
1
2
3
4
5
2
3
4
5
-rw-r--r-- 1 htk htk 2528 Oct 3 09:32 alter.sql
drw-rw---- 2 htk apache 4096 Oct 24 13:00 invoices
drwxrwx--- 2 htk apache 4096 Oct 9 14:47 logs
[htk@server6 htdocs]$ cp alter.sql invoices/
cp: cannot stat invoices/alter.sql: Permission denied
drw-rw---- 2 htk apache 4096 Oct 24 13:00 invoices
drwxrwx--- 2 htk apache 4096 Oct 9 14:47 logs
[htk@server6 htdocs]$ cp alter.sql invoices/
cp: cannot stat invoices/alter.sql: Permission denied
user htk kan dus niet een file kopieren naar invoices, want geen rechten
Code (php)
1
2
3
2
3
[htk@server6 htdocs]$ chmod 770 invoices/
[htk@server6 htdocs]$ cp alter.sql invoices/
[htk@server6 htdocs]$
[htk@server6 htdocs]$ cp alter.sql invoices/
[htk@server6 htdocs]$
Ik heb webmin geïnstalleerd en zag dat alle rechten van de mappen al goed staan ingesteld;
- de mappen in /var/www/ staan op 755
- de bestanden in /var/www/ staan op 644
Tevens heb ik een group aangemaakt genaamd "site", met daarin:
- mijn eigen account
- www-data
De eigenaar van /var/www/ is:
- root
De groep van /var/www/ is:
- site
Ik twijfel alleen nog of ik de eigenaar van /var/www/ ook moet veranderen naar site.
Edit:
Deze manier leek me toch niet zo handig dus op dit moment heb ik de map /var/www/ gewoon toegekend aan mijn eigen account en de groep met dezelfde naam als mijn account. (En aan deze groep heb ik het account www-data toegevoegd.)
Edit 2:
Er zit me toch nog 1 ding dwars. Ik heb de volgende mappenstructuur:
Bijna alle mappen staan op 0755, de laatste 5 betekent dus dat iedereen die mappen kan lezen en uitvoeren? Dat moet toch juist niet kunnen?
Gewijzigd op 24/10/2014 16:46:19 door Lord Gaga
het is uiteraard nodig dat user foo in /bin kan lezen. Al is het maar om /bin/ls uit te voeren.
Idem voor de andere mappen. Voor je het weet kun je niet meer inloggen omdat alles opslot zit..
Echter wil ik nog wel proberen om elke gebruiker een eigen www map te geven.
Is het mogelijk dat ik meerdere www mappen heb? Dus op de volgende manier:
/home/user1/domains/website1_1.nl/public_html
/home/user1/domains/website1_2.nl/public_html
/home/user2/domains/website2_1.nl/public_html
/home/user3/domains/website3_1.nl/public_html
enzovoort...
Gewijzigd op 25/10/2014 02:06:36 door Lord Gaga
Zelf heb ik in /var/www/ alle sites:
/var/www/foo.com/
/var/bar.nl/
/var/example.com/
Die hebben bij mij dan vaak de user foo, bar en example, of ivo als het alleen voor mezelf is.
Vergeet ook niet dat apache erin moet kunnen, dus /home/foo is dan niet heel handig