From: Brian.Kelly@empireblue.com
To: cygwin@cygwin.com
Subject: FTPD is still not working
Date: Thu, 06 Sep 2001 09:13:00 -0000 [thread overview]
Message-ID: <85256ABF.0058CE4B.00@wt1hub01.empirebcbs.com> (raw)
I've been working on software that utilized the cygwin ftpd daemon. Everything
was working
fine in March-April. Then I took a break from the NT development and
concentrated on
UNIX. In the meantime, I downloaded new releases of inetutils (and other
modules) as they
became available and installed them without fanfare. Unfortunately, I didn't
test the ftp server
software and "dumbly" assumed it would work as it always had.
GOTCHA!!!!!!!!
When I attempted to incorporate the NT work I had earlier accomplished into the
near finished
project, I was in for a nasty surprise. NT FTP NO LONGER WORKED. After some
research
through the mail archives, I found this post:
######################################################
######################################################
######################################################
Re: [ANNOUNCEMENT] Updated: inetutils-1.3.2-13
To: Corinna Vinschen <cygwin at cygwin dot com>
Subject: Re: [ANNOUNCEMENT] Updated: inetutils-1.3.2-13
From: "Gerrit P. Haase" <gerrit dot haase at t-online dot de>
Date: Wed, 23 May 2001 23:25:46 +0200
Organization: Esse keine toten Tiere
References: <3B0AF4D4.8719.2475C4F1@localhost>; from gerrit.haase@t-online.de on
Tue, May 22, 2001 at 11:23:00PM +0200
Reply-to: gerrit dot haase at t-online dot de
Corinna Vinschen schrieb am 2001-05-23, 10:42:
> On Tue, May 22, 2001 at 11:23:00PM +0200, Gerrit P. Haase wrote:
> > Corinna Vinschen schrieb am 2001-05-22, 10:47:
> >
> > > I've updated the version of inetutils in cygwin/latest to 1.3.2-13.
> >
> > I will never understand all this...
>
> I think, I do. It's probably my fault.
>
> > And why am I SYSTEM now?
>
> Are you using ntsec? If not, could you set CYGWIN to contain ntsec
> for inetd and look if that changes things for you?
Yes, sure am I using ntsec, as systemwide Variable and also in cygwin.bat:
1: inetd got no TTY:
$ ps -e
PID PPID PGID WINPID TTY UID STIME COMMAND
433 1 433 433 1 500 22:33:33 /usr/bin/bash
390 433 390 532 1 500 22:39:19 /usr/local/bin/perl
284 1 284 284 0 500 22:54:14 /usr/bin/bash
528 1 528 528 ? 18 22:55:03 /usr/sbin/inetd
242 528 528 242 ? 18 22:55:15 /usr/sbin/inetd
481 284 481 412 0 500 22:55:21 /usr/bin/ps
2: it is UID 18
3: CYGWIN is:
$ set
[...]
CYGWIN=$'binmode tty ntea ntsec title case_check:strict'
[...]
4: After login with telnet, i'm User SYSTEM, BASH=/bin/sh and
NO CYGWIN at all, login to ftpd fails (failed not before upgrade).
I don't use rsh so i don't know if it is different now.
> Sigh, I fear I have to change this and that in the authentication
> code in Cygwin...
O.K. i'll try next release.
> Unfortunately, this code is executed even if ntsec is off while another
> piece of code which tries to evaluate the current user is partly not
> executed when ntsec is off. AFAICS, this results in a misinterpretation
> of the user information.
Hmm, i never turn off ntsec if not trying a new port of some cute software.
gph
######################################################
######################################################
######################################################
This is precisely the problem I am having. And I am using the very latest
release inetutils-1.3.2-14.
Is there something I'm missing? If this is still an ongoing problem, then is it
possible to get
a copy of inetutils that didn't have this problem? I do not have backups of the
distribution code
from March-April. (I wish I did!) I'm really under the gun here.
Thanks
Brian Kelly
--
This electronic message contains information that may be legally confidential and/or privileged. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it.
--
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2001-09-06 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 9:13 Brian.Kelly [this message]
2001-09-06 9:21 ` Corinna Vinschen
2001-09-06 10:02 ` Gerrit P. Haase
2001-09-06 15:31 Brian.Kelly
2001-09-07 1:23 ` Gerrit P. Haase
2001-09-07 3:58 Brian.Kelly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85256ABF.0058CE4B.00@wt1hub01.empirebcbs.com \
--to=brian.kelly@empireblue.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).