[i] ppv7-mvm.r37 47,7 Mbytes/01:54(s)/439,86Kbps
[1] PRET RETR ppv7-mvm.r36
[1] 200 OK, will use *****-5 for upcoming transfer
[1] CPSV
[1] 227 Entering Passive Mode (****************).
[2] PORT ****************
[2] 200 PORT command successful.
[2] STOR ppv7-mvm.r36
[2] 150 Opening BINARY mode data connection for ppv7-mvm.r36.
[1] RETR ppv7-mvm.r36
[1] 150 File status okay; about to open data connection from *****-5.
[1] 426- Connection reset by peer: socket write error
[1] 426 Connection reset by peer: socket write error
cd \cert
makecert.exe -r -n "CN=ioFTPD" -b 05/07/2007 -e 01/01/2100 -eku 1.3.6.1.5.5.7.3.1 -ss my -sr CurrentUser -a md5 -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 C:\ioFTPD\ioFTPD.cer
Then goto your C:\ioFTPD\ioFTPD.cer file and dubble click on it (Open it, and choose install)
in ioFTPD.ini search for;
#
# >>>>>>>>>>>> SSL CHANGE THIS <<<<<<<<<<<<<<
#
# After you have created your certificate, change this to the name you used
# which should be your dynamic DNS name, your fixed external IP address, or
# if you have neither of those a made up descriptive name for you server.
# Since all locally generated certificates will report as being unverified
# you might as well get rid of clients also complaining your cert name doesn't
# match your DNS name or IP address. Certificate_Name = ioFTPD
When you changed that to according, restart iOFTPD, try login again.
cd \cert
makecert.exe -r -n "CN=ioFTPD" -b 05/07/2007 -e 01/01/2100 -eku 1.3.6.1.5.5.7.3.1 -ss my -sr CurrentUser -a md5 -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 C:\ioFTPD\ioFTPD.cer
Then goto your C:\ioFTPD\ioFTPD.cer file and dubble click on it (Open it, and choose install)
in ioFTPD.ini search for;
#
# >>>>>>>>>>>> SSL CHANGE THIS <<<<<<<<<<<<<<
#
# After you have created your certificate, change this to the name you used
# which should be your dynamic DNS name, your fixed external IP address, or
# if you have neither of those a made up descriptive name for you server.
# Since all locally generated certificates will report as being unverified
# you might as well get rid of clients also complaining your cert name doesn't
# match your DNS name or IP address. Certificate_Name = ioFTPD
When you changed that to according, restart iOFTPD, try login again.
Hope this give you a hint.
hello.
i am new in using ioftpd. everytime when try to install ssl i got this error:
plan3t: First off it looks like you can login fine. Assuming this was done via SSL/TLS this proves the cert is somewhat OK. Second, it looks like you are FXPing which introduces a bunch of other variables.
You obscured the IP addresses (which is good) but I just want to make sure they are actually valid and not 192.168.1.x or something else which is clearly incorrect and happens ALL THE TIME when people don't setup the HOST= option in ioftpd.ini and are behind NAT firewalls... When you say crash and then say you can't kick the user I'm a bit confused. The connection may be dropped, and/or the user stuck logged in or something but ioftpd didn't crash and completely exit.
John H: Error: Invalid issuer store location - that sounds like the cert isn't installed into the proper location or something else is wrong with it. Download certmgr.exe which should come with makecert.exe from MS (you'll need to search a bit as I'm not sure its released outside of the platform download now) so you can examine the certificate store...
Makecert in my experience makes AND installs the certificate. You don't need to click on the .cer file and install it.