Anyone interested in my ioFTPD build?

[UltraFine]

Originally Posted by Prodigy

Hmm, looks like unable to access 0xC0000005 is pretty generic one on windows, one of the reason is faulty hardware or windows installation, if that's the case it should also happened with Yil one.

My assembly language is pretty rusty, but it would be helpful if you give me the complete setup in which the case is happened.

Mean while, could you please trying the following to disable DEP on ioFTPD.exe ?, steps are in here.

Prodigy, just for your interest: I have tried to disable DEP for ioftpd.exe (to put it into the excluded list) and my win7 does not go for it. I get a message that exluding this program from DEP is impossible. DEP has to be run for this program.

[Prodigy]

@Henkie2
Only a newbie attempt, far from skilled

@UltraFine
I see, but does it run fine so far without crashes on windows 7?

[UltraFine]

Originally Posted by Prodigy

@Henkie2
Only a newbie attempt, far from skilled

@UltraFine
I see, but does it run fine so far without crashes on windows 7?

Hello Prodigy,

I ran the test here, the result: It crashed both SCHEDULER calls again. Here are the details:

[SCHEDULER]
1. Newday at 0 o'clock 10 Minutes ioA.exe NEWDATE
2. searchlog at 4 o'clock 0 Minutes ioA.exe SEARCHLOGCREATE


The first script made ioftpd crash so hard that no dump files were created and ioftpd was DELETED. It was not in the directory anymore. The second time , after I have copied it back from the RAR file into the /sysdirectory and restartet it, it crashed again on searchlog at 4am in the morning.

TINYDUMP-20181221.040022-27124.dmp - 56kb
MINIDUMP-20181221.040022-27124.dmp - 643kb

ioFTPD File - size: 475 KB (486.912 Bytes), date: 18.12.2018 21:05:24
/lib directory is a unchanded copy out of the RAR archive belonging to the abobe ioftpd.exe

Test machine: Windows 10

CRASH-Log.txt
Fri Dec 21 04:00:22 2018 - ioFTPD v7.7.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x004114A9 [attempting to read data from 0x00000006]
PID=27124, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 29580

System information:
Processor #0 Name: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
Processor #0 Identifier: Intel64 Family 6 Model 23 Stepping 10
Processor #1 Name: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
Processor #1 Identifier: Intel64 Family 6 Model 23 Stepping 10
OS: Windows 6.2 (build 9200)
Registry: Windows 10 Enterprise
Decoded: Vista
Page size: 4096
Notice: Unable to acquire Debug Rights


The SEARCHLOGCREATE ioA script is configured to scan a huge harddrive with alot of directories and file which it puts into a plain text file search.log. The script DID run and it managed to create the search.log file which became 56MB in size. It seems the script crashed ioftpd AFTER it finished its work.


I will send you the dump files per E-Mail.

UltraFine

P.S. I tried the same test on my Win7-64 machine and it worked without a crash. The only difference was that I had a very little directory tree to scan for search.log on win7 machine. Maybe like 50 directories and sub-dirs. It produced a searchlog of 20kb. The searchlog on Win10 machine was way bigger and produced 56MB.

[Prodigy]

Ok so 'reliability' has increased for a while, sounds good, i will wait for the crash dumps.

[Prodigy]

So i have found that Visual Studio 2013 managed to compile ioFTPD without any code modifications, so here it is if you want to try again.

Now naming it ioFTPD 7.7.4

https://mega.nz/#!4IsTzaIL!aiJPIG1QS0OANbe8AyIjUy2Fn5pYaYCihdq4IdXHeT8

As usual, replace the ..\lib and ..\system folder with mine.

[UltraFine]

Originally Posted by Prodigy

So i have found that Visual Studio 2013 managed to compile ioFTPD without any code modifications, so here it is if you want to try again.

Now naming it ioFTPD 7.7.4

https://mega.nz/#!4IsTzaIL!aiJPIG1QS0OANbe8AyIjUy2Fn5pYaYCihdq4IdXHeT8

As usual, replace the ..\lib and ..\system folder with mine.

Sure, I will re-test this one for you. Though I would say a version number that contains compilation date like 7.7.4.21122018 would be the best. Because when you recompile the same version several times and I test the same major version, I still can mess up the files of different dates.

Ultra

[UltraFine]

Originally Posted by Prodigy

So i have found that Visual Studio 2013 managed to compile ioFTPD without any code modifications, so here it is if you want to try again.

Now naming it ioFTPD 7.7.4

https://mega.nz/#!4IsTzaIL!aiJPIG1QS0OANbe8AyIjUy2Fn5pYaYCihdq4IdXHeT8

As usual, replace the ..\lib and ..\system folder with mine.

Yes. This version that is marked as 7.7.4 compiled on 21.12.2018 at 16:23:50 works well. Both scheduler events (ioA NEWDATE, SEARCHLOGCREATE) ran without a problem. I tested this on two machines. Win7 and Win10.

Cheers

[Henkie2]

Last version runs great even faster on speeds
Thanks once again, also tested latest eggdrop only that one gives errors;
- cant find logs ioftpd.logs (dZSbot needs to read logs)
- need to add this line init.tcl or eggdrop wont start here at all : set ::tcl_library "./lib/tcl8.5"

[Prodigy]

Thanks, it wouldn't be possible without you guys testing it out, currently trying to support TLS v1.2 by using LibreSSL, still testing by UltraFine.

@Henkie2
By overall functionality of eggdrop is working fine so far?

[Prodigy]

ioFTPD is probably in the world the first ever FTP Server which supports TLS 1.3!.
Curl output :

*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 5420 (#0)
< 220 FTP Server ready.
> AUTH SSL
< 234 AUTH SSL successful.
* Cipher selection: TLS13-CHACHA20-POLY1305-SHA256
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* Server certificate:
*  subject: CN=ioFTPD
*  start date: Dec 27 13:21:15 2018 GMT
*  expire date: Dec 25 13:21:15 2028 GMT
*  issuer: CN=ioFTPD
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
> USER ioFTPD
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< 331 Password required for ioFTPD.
> PASS ioFTPD
< 230-User ioFTPD from 192.150.14.69, welcome to our FTP server.
< 230-
< 230-ioFTPD activity:
< 230-
< 230-      Users online     : 2
< 230-      Active transfers : 0
< 230-      Uptime           : 29 secs
< 230-
< 230-Enjoy your stay.
< 230 User ioFTPD logged in.
> PBSZ 0
< 200 PBSZ 0 successful.
> PROT P
< 200 Protection set to: Private.
> PWD
< 257 "/" is current directory.
* Entry path is '/'
> EPSV
* Connect data stream passively
< 500 'EPSV': Command not understood
* Failed EPSV attempt. Disabling EPSV
> PASV
* ftp_perform ends with SECONDARY: 0
< 227 Entering Passive Mode (127,0,0,1,21,48)
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connecting to 127.0.0.1 (127.0.0.1) port 5424
* Connected to 127.0.0.1 (127.0.0.1) port 5420 (#0)
> TYPE I
< 200 Type set to I.
> SIZE test.log
< 213 5079
> RETR test.log
< 150 Opening BINARY mode data connection for test.log (5079 bytes) using SSL/TLS.
* Maxdownload = -1
* Getting file with size: 5079
* Doing the SSL/TLS handshake on the data stream
* Cipher selection: TLS13-CHACHA20-POLY1305-SHA256
* SSL re-using session ID
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* Server certificate:
*  subject: CN=ioFTPD
*  start date: Dec 27 13:21:15 2018 GMT
*  expire date: Dec 25 13:21:15 2028 GMT
*  issuer: CN=ioFTPD
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing

None of the any FTP Client for windows supporting TLS 1.3, except curl :-(

[R34nimator]

Has this been tested on Windows Server 2016 Data Center

[shift]

Prodigy does youre latest ioftpd work with youre beta of ioninja beta 6 ?

[jackupwick]

Still its working fine and have latest updates?

[Prodigy]

@jackupwick

Join the ioFTPD discord server, https://discord.gg/j6GGPXg .