ioFTPD v7.6.3 Released (Beta)

[Yil]

This release only contains 1 new feature and 2 bug fixes, but hopefully I got the logic right to avoid a race condition on updating directory information that could end up corrupting memory... Since it happens only when multiple users are actively accessing/updating the same directory this may explain why more active sites see this and I hadn't previously. The use of [chattr] directory data (such as with TCL based zipscripts) makes the problem FAR more likely and with worse side effects.

Latest Version:
Link: ioFTPD-v7.6.3.zip (http://home.comcast.net/~yil/ioFTPD-v7.6.3.zip)

[Yil]

v7.6.0 Release Notes:

1) Files in \System:
Changed : ioFTPD.[exe,pdb] - Version 7.6.0.0.


*** New Features:

2) The FTP command 'PASS' now provides partial support for the "-" prefix
on a user's password. glFTPD allows a dash before the user's password to
mean that multi-line command responses should be disabled. This was
primarily used by scripts and autotraders where no user would ever view
the response so why bother generating and sending the extra lines. ioFTPD
will now accept the dash prefix on a password to eliminate error log spam
of the form:
User '<user>' (<ident>@ <host/ip>) tried to login with invalid password.
created by people using the "preee" tool. Evidently newly created sites
default to a server type of glftpd which would use the dash prefix for
additional logins when the "Use second Login for faster FXP" feature was
enabled and thus the password check would fail. For the record, changing
the server type to "AUTO" in preee will also fix the problem, but that
would require informing users with bad configurations one by one...

NOTE: the next release of ioFTPD will honor the spirit of the prefix
and disable themes, .message file showing, etc.


*** Bug Fixes:

3) Fixed a bug where you couldn't receive lengthy directory listings
(usually from 'LIST -alR') over SSL data channels.

4) Fixed two tricky bugs when updating directory VFS permissions, owner,
and/or [chattr] data which is what zipscripts like ioNinja do when files
are being uploaded. If a user is trying to access the directory's
root entry (most likely when listing the directory) at the same time as
an update is being performed memory could end up being corrupted in some
cases. The more simultaneous updates the larger the risks and potential
for wider corruption.

[Flow]

Thanks Yil

[Flow]

Clean install. No script running. I executed ftp command site swho, i killed the server :)

SITE SWHO
Error: 10054: Connection reset by peer

Site down and died

[Yil]

Yea, I can confirm that 'site swho' crashed mine as well. Will get that fixed!

[Yil]

v7.6.1 Release Notes:

1) Files in \System:
Changed : ioFTPD.[exe,pdb] - Version 7.6.1.0.


*** New Features:

2) Fixed a bug with 'site swho' which would corrupt the stack and depending
upon where the optimizer put stuff could cause crashes.

[Yil]

Turns out the problem wasn't "new" (code wasn't changed so it's been there a while), but the compiler/optimizer must have moved things around a bit and now it became an issue... Should be fixed.

[Flow]

nopp, still crashing on me b7.6.1.0

[Yil]

v7.6.2 Release Notes:

1) Files in \System:
Changed : ioFTPD.[exe,pdb] - Version 7.6.2.0.


*** Bug Fixes:

2) Actually made the change that was supposed to go into v7.6.1 to the right
tree and not the v8 source...

[Yil]

So sorry, I found the bug and "fixed" it, but it was to the directory with the new code for the v8 release. So v7.6.1 was effectively just a recompile of v7.6.0 LOL! Hopefully this one may work better :)

[ArtX]

site swho doesn't crash the server here using 7.6.2 :-)

[Flow]

Oh yea, fixed. Thanks

[Sabour]

8.0 planned release, wohoo grats and kudos to you Yil :)

[Yil]

v7.6.3 Release Notes:

1) Files in \System:
Changed : ioFTPD.[exe,pdb] - Version 7.6.3.0.


*** Bug Fixes:

2) Fixed a bug (introduced in, I think, v7.5.3) that would cause the path
resolver to overwrite the first letter of the last path with a '/' in
some cases if the Keep_Links_In_Paths option is disabled (default config
has this enabled). The server seemed to work OK, but it would break
scripts and bots which read the logfiles since the path would be wrong.