From ad678bf89f8c1174058bb6d16e5a458e9c290bc0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nikola=20Forr=C3=B3?= <nforro@redhat.com>
Date: Tue, 28 Nov 2017 11:44:40 +0100
Subject: [PATCH] vsftpd.conf.5: extend description of ascii_download_enable
 and ascii_upload_enable

---
 vsftpd/man5/vsftpd.conf.5 | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/vsftpd/man5/vsftpd.conf.5 b/vsftpd/man5/vsftpd.conf.5
index f50c9c7..6aef05e 100644
--- a/vsftpd/man5/vsftpd.conf.5
+++ b/vsftpd/man5/vsftpd.conf.5
@@ -113,11 +113,31 @@ Default: YES
 .TP
 .B ascii_download_enable
 When enabled, ASCII mode data transfers will be honoured on downloads.
+When disabled, the server will pretend to allow ASCII mode but in fact
+ignore requests to activate it. So the client will think the ASCII mode
+is active and therefore may still translate any
+.BR <CRLF>
+character sequences in the received file. See the following article for
+a detailed explanation of the behaviour:
+https://access.redhat.com/articles/3250241.
+
+Turn this option on to have the server actually do
+ASCII mangling on files when in ASCII mode.
 
 Default: NO
 .TP
 .B ascii_upload_enable
 When enabled, ASCII mode data transfers will be honoured on uploads.
+When disabled, the server will pretend to allow ASCII mode but in fact
+ignore requests to activate it. So the client will think the ASCII mode
+is active and will translate native line terminators to the standard
+.BR <CRLF>
+line terminators for transmission, but the server will not do
+any translation. See the following article for a detailed explanation
+of the behaviour: https://access.redhat.com/articles/3250241.
+
+Turn this option on to have the server actually do
+ASCII mangling on files when in ASCII mode.
 
 Default: NO
 .TP
-- 
2.13.6