This repository has been archived by the owner on Sep 25, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
/
Copy pathvsftpd.conf.html
1297 lines (1092 loc) · 108 KB
/
vsftpd.conf.html
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
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!-- saved from url=(0052)https://security.appspot.com/vsftpd/vsftpd_conf.html -->
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Manpage of VSFTPD.CONF</title>
</head><body>
<h1>VSFTPD.CONF</h1>
Section: File Formats (5)<br><a href="https://security.appspot.com/vsftpd/vsftpd_conf.html#index">Index</a>
<a href="http://localhost/cgi-bin/man/man2html">Return to Main Contents</a><hr>
<a name="lbAB"> </a>
<h2>NAME</h2>
vsftpd.conf - config file for vsftpd
<a name="lbAC"> </a>
<h2>DESCRIPTION</h2>
vsftpd.conf may be used to control various aspects of vsftpd's behaviour. By
default, vsftpd looks for this file at the location
<b>/etc/vsftpd.conf</b>.
However, you may override this by specifying a command line argument to
vsftpd. The command line argument is the pathname of the configuration file
for vsftpd. This behaviour is useful because you may wish to use an advanced
inetd such as
<b>xinetd</b>
to launch vsftpd with different configuration files on a per virtual host
basis.
<p>
<a name="lbAD"> </a>
</p><h2>FORMAT</h2>
The format of vsftpd.conf is very simple. Each line is either a comment or
a directive. Comment lines start with a # and are ignored. A directive line
has the format:
<p>
option=value
</p><p>
It is important to note that it is an error to put any space between the
option, = and value.
</p><p>
Each setting has a compiled in default which may be modified in the
configuration file.
</p><p>
<a name="lbAE"> </a>
</p><h2>BOOLEAN OPTIONS</h2>
Below is a list of boolean options. The value for a boolean option may be set
to
<b>YES</b>
or
<b>NO</b>.
<p>
</p><dl compact="">
<dt><b>allow_anon_ssl</b>
</dt><dd>
Only applies if
<b>ssl_enable</b>
is active. If set to YES, anonymous users will be allowed to use secured SSL
connections.
<p>
Default: NO
</p></dd><dt><b>anon_mkdir_write_enable</b>
</dt><dd>
If set to YES, anonymous users will be permitted to create new directories
under certain conditions. For this to work, the option
<b>write_enable</b>
must be activated, and the anonymous ftp user must have write permission on
the parent directory.
<p>
Default: NO
</p></dd><dt><b>anon_other_write_enable</b>
</dt><dd>
If set to YES, anonymous users will be permitted to perform write operations
other than upload and create directory, such as deletion and renaming. This
is generally not recommended but included for completeness.
<p>
Default: NO
</p></dd><dt><b>anon_upload_enable</b>
</dt><dd>
If set to YES, anonymous users will be permitted to upload files under certain
conditions. For this to work, the option
<b>write_enable</b>
must be activated, and the anonymous ftp user must have write permission on
desired upload locations. This setting is also required for virtual users to
upload; by default, virtual users are treated with anonymous (i.e. maximally
restricted) privilege.
<p>
Default: NO
</p></dd><dt><b>anon_world_readable_only</b>
</dt><dd>
When enabled, anonymous users will only be allowed to download files which
are world readable. This is recognising that the ftp user may own files,
especially in the presence of uploads.
<p>
Default: YES
</p></dd><dt><b>anonymous_enable</b>
</dt><dd>
Controls whether anonymous logins are permitted or not. If enabled,
both the usernames
<b>ftp</b>
and
<b>anonymous</b>
are recognised as anonymous logins.
<p>
Default: YES
</p></dd><dt><b>ascii_download_enable</b>
</dt><dd>
When enabled, ASCII mode data transfers will be honoured on downloads.
<p>
Default: NO
</p></dd><dt><b>ascii_upload_enable</b>
</dt><dd>
When enabled, ASCII mode data transfers will be honoured on uploads.
<p>
Default: NO
</p></dd><dt><b>async_abor_enable</b>
</dt><dd>
When enabled, a special FTP command known as "async ABOR" will be enabled.
Only ill advised FTP clients will use this feature. Additionally, this feature
is awkward to handle, so it is disabled by default. Unfortunately, some FTP
clients will hang when cancelling a transfer unless this feature is available,
so you may wish to enable it.
<p>
Default: NO
</p></dd><dt><b>background</b>
</dt><dd>
When enabled, and vsftpd is started in "listen" mode, vsftpd will background
the listener process. i.e. control will immediately be returned to the shell
which launched vsftpd.
<p>
Default: NO
</p></dd><dt><b>check_shell</b>
</dt><dd>
Note! This option only has an effect for non-PAM builds of vsftpd. If disabled,
vsftpd will not check /etc/shells for a valid user shell for local logins.
<p>
Default: YES
</p></dd><dt><b>chmod_enable</b>
</dt><dd>
When enabled, allows use of the SITE CHMOD command. NOTE! This only applies
to local users. Anonymous users never get to use SITE CHMOD.
<p>
Default: YES
</p></dd><dt><b>chown_uploads</b>
</dt><dd>
If enabled, all anonymously uploaded files will have the ownership changed
to the user specified in the setting
<b>chown_username</b>.
This is useful from an administrative, and perhaps security, standpoint.
<p>
Default: NO
</p></dd><dt><b>chroot_list_enable</b>
</dt><dd>
If activated, you may provide a list of local users who are placed in a
chroot() jail in their home directory upon login. The meaning is slightly
different if chroot_local_user is set to YES. In this case, the list becomes
a list of users which are NOT to be placed in a chroot() jail.
By default, the file containing this list is
/etc/vsftpd.chroot_list, but you may override this with the
<b>chroot_list_file</b>
setting.
<p>
Default: NO
</p></dd><dt><b>chroot_local_user</b>
</dt><dd>
If set to YES, local users will be (by default) placed in a chroot() jail in
their home directory after login.
<b>Warning:</b>
This option has security implications, especially if the users have upload
permission, or shell access. Only enable if you know what you are doing.
Note that these security implications are not vsftpd specific. They apply to
all FTP daemons which offer to put local users in chroot() jails.
<p>
Default: NO
</p></dd><dt><b>connect_from_port_20</b>
</dt><dd>
This controls whether PORT style data connections use port 20 (ftp-data) on
the server machine. For security reasons, some clients may insist that this
is the case. Conversely, disabling this option enables vsftpd to run with
slightly less privilege.
<p>
Default: NO (but the sample config file enables it)
</p></dd><dt><b>debug_ssl</b>
</dt><dd>
If true, OpenSSL connection diagnostics are dumped to the vsftpd log file.
(Added in v2.0.6).
<p>
Default: NO
</p></dd><dt><b>delete_failed_uploads</b>
</dt><dd>
If true, any failed upload files are deleted. (Added in v2.0.7).
<p>
Default: NO
</p></dd><dt><b>deny_email_enable</b>
</dt><dd>
If activated, you may provide a list of anonymous password e-mail responses
which cause login to be denied. By default, the file containing this list is
/etc/vsftpd.banned_emails, but you may override this with the
<b>banned_email_file</b>
setting.
<p>
Default: NO
</p></dd><dt><b>dirlist_enable</b>
</dt><dd>
If set to NO, all directory list commands will give permission denied.
<p>
Default: YES
</p></dd><dt><b>dirmessage_enable</b>
</dt><dd>
If enabled, users of the FTP server can be shown messages when they first
enter a new directory. By default, a directory is scanned for the
file .message, but that may be overridden with the configuration setting
<b>message_file</b>.
<p>
Default: NO (but the sample config file enables it)
</p></dd><dt><b>download_enable</b>
</dt><dd>
If set to NO, all download requests will give permission denied.
<p>
Default: YES
</p></dd><dt><b>dual_log_enable</b>
</dt><dd>
If enabled, two log files are generated in parallel, going by default to
<b>/var/log/xferlog</b>
and
<b>/var/log/vsftpd.log</b>.
The former is a wu-ftpd style transfer log, parseable by standard tools. The
latter is vsftpd's own style log.
<p>
Default: NO
</p></dd><dt><b>force_dot_files</b>
</dt><dd>
If activated, files and directories starting with . will be shown in directory
listings even if the "a" flag was not used by the client. This override
excludes the "." and ".." entries.
<p>
Default: NO
</p></dd><dt><b>force_anon_data_ssl</b>
</dt><dd>
Only applies if
<b>ssl_enable</b>
is activated. If activated, all anonymous logins are forced to use a secure
SSL connection in order to send and receive data on data connections.
<p>
Default: NO
</p></dd><dt><b>force_anon_logins_ssl</b>
</dt><dd>
Only applies if
<b>ssl_enable</b>
is activated. If activated, all anonymous logins are forced to use a secure
SSL connection in order to send the password.
<p>
Default: NO
</p></dd><dt><b>force_local_data_ssl</b>
</dt><dd>
Only applies if
<b>ssl_enable</b>
is activated. If activated, all non-anonymous logins are forced to use a secure
SSL connection in order to send and receive data on data connections.
<p>
Default: YES
</p></dd><dt><b>force_local_logins_ssl</b>
</dt><dd>
Only applies if
<b>ssl_enable</b>
is activated. If activated, all non-anonymous logins are forced to use a secure
SSL connection in order to send the password.
<p>
Default: YES
</p></dd><dt><b>guest_enable</b>
</dt><dd>
If enabled, all non-anonymous logins are classed as "guest" logins. A guest
login is remapped to the user specified in the
<b>guest_username</b>
setting.
<p>
Default: NO
</p></dd><dt><b>hide_ids</b>
</dt><dd>
If enabled, all user and group information in directory listings will be
displayed as "ftp".
<p>
Default: NO
</p></dd><dt><b>implicit_ssl</b>
</dt><dd>
If enabled, an SSL handshake is the first thing expect on all connections
(the FTPS protocol). To support explicit SSL and/or plain text too, a
separate vsftpd listener process should be run.
<p>
Default: NO
</p></dd><dt><b>listen</b>
</dt><dd>
If enabled, vsftpd will run in standalone mode. This means that vsftpd must
not be run from an inetd of some kind. Instead, the vsftpd executable is
run once directly. vsftpd itself will then take care of listening for and
handling incoming connections.
<p>
Default: YES
</p></dd><dt><b>listen_ipv6</b>
</dt><dd>
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.
<p>
Default: NO
</p></dd><dt><b>local_enable</b>
</dt><dd>
Controls whether local logins are permitted or not. If enabled, normal
user accounts in /etc/passwd (or wherever your PAM config references) may be
used to log in. This must be enable for any non-anonymous login to work,
including virtual users.
<p>
Default: NO
</p></dd><dt><b>lock_upload_files</b>
</dt><dd>
When enabled, all uploads proceed with a write lock on the upload file. All
downloads proceed with a shared read lock on the download file. WARNING!
Before enabling this, be aware that malicious readers could starve a writer
wanting to e.g. append a file.
<p>
Default: YES
</p></dd><dt><b>log_ftp_protocol</b>
</dt><dd>
When enabled, all FTP requests and responses are logged, providing the option
xferlog_std_format is not enabled. Useful for debugging.
<p>
Default: NO
</p></dd><dt><b>ls_recurse_enable</b>
</dt><dd>
When enabled, this setting will allow the use of "ls -R". This is a minor
security risk, because a ls -R at the top level of a large site may consume
a lot of resources.
<p>
Default: NO
</p></dd><dt><b>mdtm_write</b>
</dt><dd>
When enabled, this setting will allow MDTM to set file modification times
(subject to the usual access checks).
<p>
Default: YES
</p></dd><dt><b>no_anon_password</b>
</dt><dd>
When enabled, this prevents vsftpd from asking for an anonymous password -
the anonymous user will log straight in.
<p>
Default: NO
</p></dd><dt><b>no_log_lock</b>
</dt><dd>
When enabled, this prevents vsftpd from taking a file lock when writing to log
files. This option should generally not be enabled. It exists to workaround
operating system bugs such as the Solaris / Veritas filesystem combination
which has been observed to sometimes exhibit hangs trying to lock log files.
<p>
Default: NO
</p></dd><dt><b>one_process_model</b>
</dt><dd>
If you have a Linux 2.4 kernel, it is possible to use a different security
model which only uses one process per connection. It is a less pure security
model, but gains you performance. You really don't want to enable this unless
you know what you are doing, and your site supports huge numbers of
simultaneously connected users.
<p>
Default: NO
</p></dd><dt><b>passwd_chroot_enable</b>
</dt><dd>
If enabled, along with
<b>chroot_local_user</b>
, then a chroot() jail location may be specified on a per-user basis. Each
user's jail is derived from their home directory string in /etc/passwd. The
occurrence of /./ in the home directory string denotes that the jail is at that
particular location in the path.
<p>
Default: NO
</p></dd><dt><b>pasv_addr_resolve</b>
</dt><dd>
Set to YES if you want to use a hostname (as opposed to IP address) in the
<b>pasv_address</b>
option.
<p>
Default: NO
</p></dd><dt><b>pasv_enable</b>
</dt><dd>
Set to NO if you want to disallow the PASV method of obtaining a data
connection.
<p>
Default: YES
</p></dd><dt><b>pasv_promiscuous</b>
</dt><dd>
Set to YES if you want to disable the PASV security check that ensures the
data connection originates from the same IP address as the control connection.
Only enable if you know what you are doing! The only legitimate use for this
is in some form of secure tunnelling scheme, or perhaps to facilitate FXP
support.
<p>
Default: NO
</p></dd><dt><b>port_enable</b>
</dt><dd>
Set to NO if you want to disallow the PORT method of obtaining a data
connection.
<p>
Default: YES
</p></dd><dt><b>port_promiscuous</b>
</dt><dd>
Set to YES if you want to disable the PORT security check that ensures that
outgoing data connections can only connect to the client. Only enable if
you know what you are doing!
<p>
Default: NO
</p></dd><dt><b>require_cert</b>
</dt><dd>
If set to yes, all SSL client connections are required to present a client
certificate. The degree of validation applied to this certificate is
controlled by
<b>validate_cert</b>
(Added in v2.0.6).
<p>
Default: NO
</p></dd><dt><b>require_ssl_reuse</b>
</dt><dd>
If set to yes, all SSL data connections are required to exhibit SSL session
reuse (which proves that they know the same master secret as the control
channel). Although this is a secure default, it may break many FTP clients,
so you may want to disable it. For a discussion of the consequences, see
<a href="http://scarybeastsecurity.blogspot.com/2009/02/vsftpd-210-released.html">http://scarybeastsecurity.blogspot.com/2009/02/vsftpd-210-released.html</a>
(Added in v2.1.0).
<p>
Default: YES
</p></dd><dt><b>run_as_launching_user</b>
</dt><dd>
Set to YES if you want vsftpd to run as the user which launched vsftpd. This is
useful where root access is not available. MASSIVE WARNING! Do NOT enable this
option unless you totally know what you are doing, as naive use of this option
can create massive security problems. Specifically, vsftpd does not / cannot
use chroot technology to restrict file access when this option is set (even if
launched by root). A poor substitute could be to use a
<b>deny_file</b>
setting such as {/*,*..*}, but the reliability of this cannot compare to
chroot, and should not be relied on.
If using this option, many restrictions on other options
apply. For example, options requiring privilege such as non-anonymous logins,
upload ownership changing, connecting from port 20 and listen ports less than
1024 are not expected to work. Other options may be impacted.
<p>
Default: NO
</p></dd><dt><b>secure_email_list_enable</b>
</dt><dd>
Set to YES if you want only a specified list of e-mail passwords for anonymous
logins to be accepted. This is useful as a low-hassle way of restricting
access to low-security content without needing virtual users. When enabled,
anonymous logins are prevented unless the password provided is listed in the
file specified by the
<b>email_password_file</b>
setting. The file format is one password per line, no extra whitespace. The
default filename is /etc/vsftpd.email_passwords.
<p>
Default: NO
</p></dd><dt><b>session_support</b>
</dt><dd>
This controls whether vsftpd attempts to maintain sessions for logins. If
vsftpd is maintaining sessions, it will try and update utmp and wtmp. It
will also open a pam_session if using PAM to authenticate, and only close
this upon logout. You may wish to disable this if you do not need session
logging, and you wish to give vsftpd more opportunity to run with less
processes and / or less privilege. NOTE - utmp and wtmp support is only
provided with PAM enabled builds.
<p>
Default: NO
</p></dd><dt><b>setproctitle_enable</b>
</dt><dd>
If enabled, vsftpd will try and show session status information in the system
process listing. In other words, the reported name of the process will change
to reflect what a vsftpd session is doing (idle, downloading etc). You
probably want to leave this off for security purposes.
<p>
Default: NO
</p></dd><dt><b>ssl_enable</b>
</dt><dd>
If enabled, and vsftpd was compiled against OpenSSL, vsftpd will support secure
connections via SSL. This applies to the control connection (including login)
and also data connections. You'll need a client with SSL support too. NOTE!!
Beware enabling this option. Only enable it if you need it. vsftpd can make no
guarantees about the security of the OpenSSL libraries. By enabling this
option, you are declaring that you trust the security of your installed
OpenSSL library.
<p>
Default: NO
</p></dd><dt><b>ssl_request_cert</b>
</dt><dd>
If enabled, vsftpd will request (but not necessarily require; see
<b>require_cert)</b>a<b>certificate</b>on<b>incoming</b>SSL<b>connections.</b>Normally<b>this</b>
should not cause any trouble at all, but IBM zOS seems to have issues.
(New in v2.0.7).
<p>
Default: YES
</p></dd><dt><b>ssl_sslv2</b>
</dt><dd>
Only applies if
<b>ssl_enable</b>
is activated. If enabled, this option will permit SSL v2 protocol connections.
TLS v1 connections are preferred.
<p>
Default: NO
</p></dd><dt><b>ssl_sslv3</b>
</dt><dd>
Only applies if
<b>ssl_enable</b>
is activated. If enabled, this option will permit SSL v3 protocol connections.
TLS v1 connections are preferred.
<p>
Default: NO
</p></dd><dt><b>ssl_tlsv1</b>
</dt><dd>
Only applies if
<b>ssl_enable</b>
is activated. If enabled, this option will permit TLS v1 protocol connections.
TLS v1 connections are preferred.
<p>
Default: YES
</p></dd><dt><b>strict_ssl_read_eof</b>
</dt><dd>
If enabled, SSL data uploads are required to terminate via SSL, not an
EOF on the socket. This option is required to be sure that an attacker did
not terminate an upload prematurely with a faked TCP FIN. Unfortunately, it
is not enabled by default because so few clients get it right. (New in v2.0.7).
<p>
Default: NO
</p></dd><dt><b>strict_ssl_write_shutdown</b>
</dt><dd>
If enabled, SSL data downloads are required to terminate via SSL, not an
EOF on the socket. This is off by default as I was unable to find a single
FTP client that does this. It is minor. All it affects is our ability to tell
whether the client confirmed full receipt of the file. Even without this option,
the client is able to check the integrity of the download. (New in v2.0.7).
<p>
Default: NO
</p></dd><dt><b>syslog_enable</b>
</dt><dd>
If enabled, then any log output which would have gone to /var/log/vsftpd.log
goes to the system log instead. Logging is done under the FTPD facility.
<p>
Default: NO
</p></dd><dt><b>tcp_wrappers</b>
</dt><dd>
If enabled, and vsftpd was compiled with tcp_wrappers support, incoming
connections will be fed through tcp_wrappers access control. Furthermore,
there is a mechanism for per-IP based configuration. If tcp_wrappers sets
the VSFTPD_LOAD_CONF environment variable, then the vsftpd session will try
and load the vsftpd configuration file specified in this variable.
<p>
Default: NO
</p></dd><dt><b>text_userdb_names</b>
</dt><dd>
By default, numeric IDs are shown in the user and group fields of directory
listings. You can get textual names by enabling this parameter. It is off
by default for performance reasons.
<p>
Default: NO
</p></dd><dt><b>tilde_user_enable</b>
</dt><dd>
If enabled, vsftpd will try and resolve pathnames such as ~chris/pics, i.e. a
tilde followed by a username. Note that vsftpd will always resolve the
pathnames ~ and ~/something (in this case the ~ resolves to the initial
login directory). Note that ~user paths will only resolve if the file
<b>/etc/passwd</b>
may be found within the _current_ chroot() jail.
<p>
Default: NO
</p></dd><dt><b>use_localtime</b>
</dt><dd>
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.
<p>
Default: NO
</p></dd><dt><b>use_sendfile</b>
</dt><dd>
An internal setting used for testing the relative benefit of using the
sendfile() system call on your platform.
<p>
Default: YES
</p></dd><dt><b>userlist_deny</b>
</dt><dd>
This option is examined if
<b>userlist_enable</b>
is activated. If you set this setting to NO, then users will be denied login
unless they are explicitly listed in the file specified by
<b>userlist_file</b>.
When login is denied, the denial is issued before the user is asked for a
password.
<p>
Default: YES
</p></dd><dt><b>userlist_enable</b>
</dt><dd>
If enabled, vsftpd will load a list of usernames, from the filename given by
<b>userlist_file</b>.
If a user tries to log in using a name in this file, they will be denied
before they are asked for a password. This may be useful in preventing
cleartext passwords being transmitted. See also
<b>userlist_deny</b>.
<p>
Default: NO
</p></dd><dt><b>validate_cert</b>
</dt><dd>
If set to yes, all SSL client certificates received must validate OK.
Self-signed certs do not constitute OK validation. (New in v2.0.6).
<p>
Default: NO
</p></dd><dt><b>virtual_use_local_privs</b>
</dt><dd>
If enabled, virtual users will use the same privileges as local users. By
default, virtual users will use the same privileges as anonymous users, which
tends to be more restrictive (especially in terms of write access).
<p>
Default: NO
</p></dd><dt><b>write_enable</b>
</dt><dd>
This controls whether any FTP commands which change the filesystem are allowed
or not. These commands are: STOR, DELE, RNFR, RNTO, MKD, RMD, APPE and SITE.
<p>
Default: NO
</p></dd><dt><b>xferlog_enable</b>
</dt><dd>
If enabled, a log file will be maintained detailling uploads and downloads.
By default, this file will be placed at /var/log/vsftpd.log, but this location
may be overridden using the configuration setting
<b>vsftpd_log_file</b>.
<p>
Default: NO (but the sample config file enables it)
</p></dd><dt><b>xferlog_std_format</b>
</dt><dd>
If enabled, the transfer log file will be written in standard xferlog format,
as used by wu-ftpd. This is useful because you can reuse existing transfer
statistics generators. The default format is more readable, however. The
default location for this style of log file is /var/log/xferlog, but you may
change it with the setting
<b>xferlog_file</b>.
<p>
Default: NO
</p><p>
</p></dd></dl>
<a name="lbAF"> </a>
<h2>NUMERIC OPTIONS</h2>
Below is a list of numeric options. A numeric option must be set to a non
negative integer. Octal numbers are supported, for convenience of the umask
options. To specify an octal number, use 0 as the first digit of the number.
<p>
</p><dl compact="">
<dt><b>accept_timeout</b>
</dt><dd>
The timeout, in seconds, for a remote client to establish connection with
a PASV style data connection.
<p>
Default: 60
</p></dd><dt><b>anon_max_rate</b>
</dt><dd>
The maximum data transfer rate permitted, in bytes per second, for anonymous
clients.
<p>
Default: 0 (unlimited)
</p></dd><dt><b>anon_umask</b>
</dt><dd>
The value that the umask for file creation is set to for anonymous users. NOTE! If you want to specify octal values, remember the "0" prefix otherwise the
value will be treated as a base 10 integer!
<p>
Default: 077
</p></dd><dt><b>chown_upload_mode</b>
</dt><dd>
The file mode to force for chown()ed anonymous uploads. (Added in v2.0.6).
<p>
Default: 0600
</p></dd><dt><b>connect_timeout</b>
</dt><dd>
The timeout, in seconds, for a remote client to respond to our PORT style
data connection.
<p>
Default: 60
</p></dd><dt><b>data_connection_timeout</b>
</dt><dd>
The timeout, in seconds, which is roughly the maximum time we permit data
transfers to stall for with no progress. If the timeout triggers, the remote
client is kicked off.
<p>
Default: 300
</p></dd><dt><b>delay_failed_login</b>
</dt><dd>
The number of seconds to pause prior to reporting a failed login.
<p>
Default: 1
</p></dd><dt><b>delay_successful_login</b>
</dt><dd>
The number of seconds to pause prior to allowing a successful login.
<p>
Default: 0
</p></dd><dt><b>file_open_mode</b>
</dt><dd>
The permissions with which uploaded files are created. Umasks are applied
on top of this value. You may wish to change to 0777 if you want uploaded
files to be executable.
<p>
Default: 0666
</p></dd><dt><b>ftp_data_port</b>
</dt><dd>
The port from which PORT style connections originate (as long as the poorly
named
<b>connect_from_port_20</b>
is enabled).
<p>
Default: 20
</p></dd><dt><b>idle_session_timeout</b>
</dt><dd>
The timeout, in seconds, which is the maximum time a remote client may spend
between FTP commands. If the timeout triggers, the remote client is kicked
off.
<p>
Default: 300
</p></dd><dt><b>listen_port</b>
</dt><dd>
If vsftpd is in standalone mode, this is the port it will listen on for
incoming FTP connections.
<p>
Default: 21
</p></dd><dt><b>local_max_rate</b>
</dt><dd>
The maximum data transfer rate permitted, in bytes per second, for local
authenticated users.
<p>
Default: 0 (unlimited)
</p></dd><dt><b>local_umask</b>
</dt><dd>
The value that the umask for file creation is set to for local users. NOTE! If
you want to specify octal values, remember the "0" prefix otherwise the value
will be treated as a base 10 integer!
<p>
Default: 077
</p></dd><dt><b>max_clients</b>
</dt><dd>
If vsftpd is in standalone mode, this is the maximum number of clients which
may be connected. Any additional clients connecting will get an error message.
<p>
Default: 0 (unlimited)
</p></dd><dt><b>max_login_fails</b>
</dt><dd>
After this many login failures, the session is killed.
<p>
Default: 3
</p></dd><dt><b>max_per_ip</b>
</dt><dd>
If vsftpd is in standalone mode, this is the maximum number of clients which
may be connected from the same source internet address. A client will get an
error message if they go over this limit.
<p>
Default: 0 (unlimited)
</p></dd><dt><b>pasv_max_port</b>
</dt><dd>
The maximum port to allocate for PASV style data connections. Can be used to
specify a narrow port range to assist firewalling.
<p>
Default: 0 (use any port)
</p></dd><dt><b>pasv_min_port</b>
</dt><dd>
The minimum port to allocate for PASV style data connections. Can be used to
specify a narrow port range to assist firewalling.
<p>
Default: 0 (use any port)
</p></dd><dt><b>trans_chunk_size</b>
</dt><dd>
You probably don't want to change this, but try setting it to something like
8192 for a much smoother bandwidth limiter.
<p>
Default: 0 (let vsftpd pick a sensible setting)
</p><p>
</p></dd></dl>
<a name="lbAG"> </a>
<h2>STRING OPTIONS</h2>
Below is a list of string options.
<p>
</p><dl compact="">
<dt><b>anon_root</b>
</dt><dd>
This option represents a directory which vsftpd will try to change into
after an anonymous login. Failure is silently ignored.
<p>
Default: (none)
</p></dd><dt><b>banned_email_file</b>
</dt><dd>
This option is the name of a file containing a list of anonymous e-mail
passwords which are not permitted. This file is consulted if the option
<b>deny_email_enable</b>
is enabled.
<p>
Default: /etc/vsftpd.banned_emails
</p></dd><dt><b>banner_file</b>
</dt><dd>
This option is the name of a file containing text to display when someone
connects to the server. If set, it overrides the banner string provided by
the
<b>ftpd_banner</b>
option.
<p>
Default: (none)
</p></dd><dt><b>ca_certs_file</b>
</dt><dd>
This option is the name of a file to load Certificate Authority certs from, for
the purpose of validating client certs. Regrettably, the default SSL CA cert
paths are not used, because of vsftpd's use of restricted filesystem spaces
(chroot). (Added in v2.0.6).
<p>
Default: (none)
</p></dd><dt><b>chown_username</b>
</dt><dd>
This is the name of the user who is given ownership of anonymously uploaded
files. This option is only relevant if another option,
<b>chown_uploads</b>,
is set.
<p>
Default: root
</p></dd><dt><b>chroot_list_file</b>
</dt><dd>
The option is the name of a file containing a list of local users which
will be placed in a chroot() jail in their home directory. This option is
only relevant if the option
<b>chroot_list_enable</b>
is enabled. If the option
<b>chroot_local_user</b>
is enabled, then the list file becomes a list of users to NOT place in a
chroot() jail.
<p>
Default: /etc/vsftpd.chroot_list
</p></dd><dt><b>cmds_allowed</b>
</dt><dd>
This options specifies a comma separated list of allowed FTP commands (post
login. USER, PASS and QUIT and others are always allowed pre-login). Other
commands are rejected. This is a powerful method of really locking down an
FTP server. Example: cmds_allowed=PASV,RETR,QUIT
<p>
Default: (none)
</p></dd><dt><b>cmds_denied</b>
</dt><dd>
This options specifies a comma separated list of denied FTP commands (post
login. USER, PASS, QUIT and others are always allowed pre-login). If a command
appears on both this and
<b>cmds_allowed</b>
then the denial takes precedence. (Added in v2.1.0).
<p>
Default: (none)
</p></dd><dt><b>deny_file</b>
</dt><dd>
This option can be used to set a pattern for filenames (and directory names
etc.) which should not be accessible in any way. The affected items are not
hidden, but any attempt to do anything to them (download, change into
directory, affect something within directory etc.) will be denied. This option
is very simple, and should not be used for serious access control - the
filesystem's permissions should be used in preference. However, this option
may be useful in certain virtual user setups. In particular aware that if