I just upgraded a development system and noticed that the ftpd is much more
recent than what we are currently running in our product. I installed the
ftpd file on another node (only that file). When I try to log on (and it did
work with the previous ftpd so no stupid problems with ftpusers etc), I get
error 530 LOGIN INCORRECT.
ftpd is the only change to a system that DID work.
I’m upgrading from the Dec 1998 version to the May 2000.
Any ideas?
Doug
Previously, Doug Rixmann wrote in qdn.public.qnx4:
I just upgraded a development system and noticed that the ftpd is much more
recent than what we are currently running in our product. I installed the
ftpd file on another node (only that file). When I try to log on (and it did
work with the previous ftpd so no stupid problems with ftpusers etc), I get
error 530 LOGIN INCORRECT.ftpd is the only change to a system that DID work.
I’m upgrading from the Dec 1998 version to the May 2000.
Any ideas?
If you have previously installed the qnx qcrypt security update,
it ships with a different ftpd than is installed with the standard
tcp/ip package. If you installed the 4.25 tcp update it overwrote
your qcrypt ftpd, which is linked against different password libs.
You can reinstall the qcrypt stuff on top of your 4.25 tcp/ip update
to bring things up to snuff again.
I understand. Actually in the release there is a ftpd.new and ftpd.qcrypt
file. What is the difference and which should we be using.
“Ken Schumm” <kwschumm@IH8SPAMqsolv.com> wrote in message
news:Voyager.020325164951.9521C@dilbert…
Previously, Doug Rixmann wrote in qdn.public.qnx4:
I just upgraded a development system and noticed that the ftpd is much
more
recent than what we are currently running in our product. I installed
the
ftpd file on another node (only that file). When I try to log on (and it
did
work with the previous ftpd so no stupid problems with ftpusers etc), I
get
error 530 LOGIN INCORRECT.ftpd is the only change to a system that DID work.
I’m upgrading from the Dec 1998 version to the May 2000.
Any ideas?
If you have previously installed the qnx qcrypt security update,
it ships with a different ftpd than is installed with the standard
tcp/ip package. If you installed the 4.25 tcp update it overwrote
your qcrypt ftpd, which is linked against different password libs.
You can reinstall the qcrypt stuff on top of your 4.25 tcp/ip update
to bring things up to snuff again.
Previously, Doug Rixmann wrote in qdn.public.qnx4:
I understand. Actually in the release there is a ftpd.new and ftpd.qcrypt
file. What is the difference and which should we be using.
The issue is how your password shadow file has been encrypted.
The shadow file is normally encrypted using a less secure algorithm. If
you install the qcrypt package, the shadow file is encrypted differently.
The qcrypt utilities (ftpd, login, etc) expect the shadow file to use
‘qcrypt’ style encryption, and the standard utility set expects the
shadow file to use the standard encryption algorithm.
Mixing things up is where the problem comes in, and installing an
update can do that to you if you have previously installed qcrypt.
I’ll email you the qcrypt release notes - that may clear things
up for you.