build 164 - SSH and FTP problems (most command don't work)

[su_A_ve]

FTP BUGS:

mkdir - 'Command unkown or not supported...'
rmdir - 'Command unkown or not supported...'
mget *.ext - Tries to get EVERY file regarless of extension (mput does work though)
dir directory - lists current directory instead of directory given

SSH BUGS:

cd .. - Doesn't work
Locked to user's home directory (regardless of setting)
For example (see below for settings):

sftp localhost
"Remote working directory is /" (Note that it's actually c:\temp)
sftp> cd ..
"Remote working directory is /.." (but I'm still in c:\temp)
sftp> cd test
"Remote working directory is /.." (but I'm still in c:\temp)
sftp> cd /
"Remote working directory is /.." (but I'm still in c:\temp)
sftp> cd test
"Remote working directory is /test/" (Now I'm in c:\temp\test)
sftp> cd ..
"Remote working directory is /test/.." (but I'm still in c:\temp\test)
sftp> cd /test
"Remote working directory is /test/" (Now I'm in c:\temp\test)

I mean, this looks more like pre-alpha...

I have very basic settings.

Domain Base directory - C:\ (no virtual paths)
User's home directory - c:\temp (not locked to home dir)
Users's permissions - C:\ RWAD-LCRI

[su_A_ve]

mkdir and rmdir aren't FTP commands... I believe they are unix shell/dos command line commands. MKD and RMD are the FTP commands you might be thinking of.

mget is not an FTP command either as far as I know so this could be a unix / Windows situation that does not match up. I'll take a look at it.

You'll have many unhappy customers if you don't support these commands. EVERY other FTP server package supports these...

Unix, Linux, even VMS...

My .02...