Re: Custom welcome message

[Faseela Mohamed]

Log Level 1 - Warning also , the custom message shows up with fewer
messages. Thanks alot for all your input Gary. It really helped.

On Fri, Feb 17, 2017 at 10:39 AM, Faseela Mohamed  wrote:

> Thanks again Gary. It worked . It showed my message , but it is showing
> all the info ... that is too much info for the user :( ..It lists all the
> commands and trace and response.
>
>
> Response: *220 Custom welcome message by Faseela.*
> Command:AUTH TLS
> Response: 234 Command AUTH okay; starting TLS connection.
> Status:  Initializing TLS...
> Trace:   TLS Handshake successful
> Trace:   Protocol: TLS1.2, Key exchange: ECDHE-RSA, Cipher:
> AES-128-GCM, MAC: AEAD
> Status:  Verifying certificate...
> Status:  TLS connection established.
> Command:USER x...@123.com
> Response: 331 User name okay, need password for x...@123.com
> Command:PASS ***
> Response: 230 User logged in, proceed.
> Command:OPTS UTF8 ON
> Response: 200 Command OPTS okay.
> Command:PBSZ 0
> Response: 200 Command PBSZ okay.
> Command:PROT P
> Response: 200 Command PROT okay.
> Command:OPTS MLST size;modify;type;
> Response: 200 Command OPTS okay.
>
>
> On Fri, Feb 17, 2017 at 1:48 AM, Gary Bell 
> wrote:
>
>> Hi Faseela, it looks like Filezilla is hiding the response string
>> returned from ftpserver unless an error occurs (in which case it shows the
>> full log in the log window). On filezilla 3.14.1, I got it to show the
>> custom response message all the time by setting the debug level in the
>> preferences to "2 - Info". Not sure if this is an option for you?
>>
>>
>>
>

Re: Custom welcome message

[Faseela Mohamed]

Thanks again Gary. It worked . It showed my message , but it is showing all
the info ... that is too much info for the user :( ..It lists all the
commands and trace and response.


Response: *220 Custom welcome message by Faseela.*
Command:AUTH TLS
Response: 234 Command AUTH okay; starting TLS connection.
Status:  Initializing TLS...
Trace:   TLS Handshake successful
Trace:   Protocol: TLS1.2, Key exchange: ECDHE-RSA, Cipher:
AES-128-GCM, MAC: AEAD
Status:  Verifying certificate...
Status:  TLS connection established.
Command:USER x...@123.com
Response: 331 User name okay, need password for x...@123.com
Command:PASS ***
Response: 230 User logged in, proceed.
Command:OPTS UTF8 ON
Response: 200 Command OPTS okay.
Command:PBSZ 0
Response: 200 Command PBSZ okay.
Command:PROT P
Response: 200 Command PROT okay.
Command:OPTS MLST size;modify;type;
Response: 200 Command OPTS okay.


On Fri, Feb 17, 2017 at 1:48 AM, Gary Bell 
wrote:

> Hi Faseela, it looks like Filezilla is hiding the response string returned
> from ftpserver unless an error occurs (in which case it shows the full log
> in the log window). On filezilla 3.14.1, I got it to show the custom
> response message all the time by setting the debug level in the preferences
> to "2 - Info". Not sure if this is an option for you?
>
>
>

RE: Custom welcome message

[Gary Bell]

Hi Faseela, it looks like Filezilla is hiding the response string returned from 
ftpserver unless an error occurs (in which case it shows the full log in the 
log window). On filezilla 3.14.1, I got it to show the custom response message 
all the time by setting the debug level in the preferences to "2 - Info". Not 
sure if this is an option for you?

Re: Custom welcome message

[Faseela Mohamed]

Thanks Gary for the response. I did the same (steps 1 t0 6) , but I
mentioned the whole path, 
wrote:

> Hi, I just tried that out and it worked form me on FtpServer-1.1.0. This
> is what I did:
>
> 0. Downloaded the latest FtpServer zip file and extracted it.
> 1. Created a new folder called \res\messages
> 2. Added a new file called FtpStatus.gen
> 3. Added my custom message for login like so:
>
> 220=JESTER ready for connection. WARNING! All activity on this site is
> monitored and tracked. Authorised personnel only.
>
> 4. Edited the res\conf\ftpd-typical.xml file to add the following element
> under the  tag:
>
> 
>
> 5. Started ftpserver under a cmd shell, passing in the config file to use:
>
> Bin\ftpd.bat \res\conf\ftpd-typical.xml
>
> 6. Connected to it using ftp client built into Windows 7 via the command
> prompt on port 2121
>
> Observed that the 220 greeting showed my new message.
>
> In production, I actually set the custome messages using a message factory
> when I am setting up the ftp server instance.
>
>  -- cut 
>
> FtpServerFactory factory = new FtpServerFactory();
>
> //Customised server messages (optional)
> String customMessageFile = config.getPropertyAsString("
> server.customMessages");
> if ( customMessageFile != null) {
> LOG.debug("Custom message resource specified: " +
> customMessageFile);
> File f = new File(customMessageFile);
> if (f.exists()) {
> LOG.debug("Message file exists,
> configuring.");
> MessageResourceFactory messageFactory =
> new MessageResourceFactory();
> messageFactory.
> setCustomMessageDirectory(f);
> factory.setMessageResource(messageFactory.
> createMessageResource());
> } else {
> LOG.error("Custom message bundle
> \""+customMessageFile + "\" specified, but does not exist. Not loaded.");
> }
> }
>  cut ---
>
>
>
>
> Best Regards,
> Gary.
>

RE: Custom welcome message

[Gary Bell]

Hi, I just tried that out and it worked form me on FtpServer-1.1.0. This is 
what I did:

0. Downloaded the latest FtpServer zip file and extracted it.
1. Created a new folder called \res\messages
2. Added a new file called FtpStatus.gen
3. Added my custom message for login like so:

220=JESTER ready for connection. WARNING! All activity on this site is 
monitored and tracked. Authorised personnel only.

4. Edited the res\conf\ftpd-typical.xml file to add the following element under 
the  tag:



5. Started ftpserver under a cmd shell, passing in the config file to use:

Bin\ftpd.bat \res\conf\ftpd-typical.xml

6. Connected to it using ftp client built into Windows 7 via the command prompt 
on port 2121

Observed that the 220 greeting showed my new message.

In production, I actually set the custome messages using a message factory when 
I am setting up the ftp server instance. 

 -- cut 

FtpServerFactory factory = new FtpServerFactory();

//Customised server messages (optional)
String customMessageFile = 
config.getPropertyAsString("server.customMessages");
if ( customMessageFile != null) {
LOG.debug("Custom message resource specified: " + 
customMessageFile);
File f = new File(customMessageFile);
if (f.exists()) {
LOG.debug("Message file exists, configuring.");
MessageResourceFactory messageFactory = new 
MessageResourceFactory();
messageFactory.setCustomMessageDirectory(f);

factory.setMessageResource(messageFactory.createMessageResource());
} else {
LOG.error("Custom message bundle 
\""+customMessageFile + "\" specified, but does not exist. Not loaded.");
}
}
 cut ---




Best Regards,
Gary.