Mail Archives: cygwin/2003/08/11/11:27:59
Brian,
Congratulations on getting this working. FWIW, you could use "mount" to
mount the UNC directory under /home/loginname (even make it a user mount
by logging in as that user and doing "mount -u").
Jason, do you think this inability to validate UNC paths stems from
proftpd prepending a "/" to the path or something? I mean, Cygwin
syscalls should be able to access the UNC path with no problems... Is
this worth investigating?
Igor
On Mon, 11 Aug 2003 Brian DOT Kelly AT empireblue DOT com wrote:
> Hi Jason, thanks for the response.
>
> OK - here's the scoop.
>
> *** I GOT IT WORKING with domain authentication ***
>
> After doing an strace, I found that proftpd could not validate a home
> directory via UNC conventions. In the domain enviroment I'm working on,
> the domain account I'm using for testing has it's *home* directory on a
> network shared resource - and mkpasswd -d -u loginname created an entry
> with the home directory set to //servername/users/loginname. proftpd
> could *not* validate this and therefore exited without attempting any
> further authentication. Once I changed the home directory setting in
> passwd to /home/loginname the domain login succeeded.
>
> On a further note, I was able to get the SYSTEM id working for proftpd.
> Turns out proftpd is HYPER sensitve to the permissions-owner-group
> settings for the /var directory tree. I resolved this by doing
>
> chown -R SYSTEM:Administrators /var
>
> That essentially fixed it.
>
> Futhermore, it was *not* necessary to have to provide any further user
> rights to the SYSTEM id.
>
> It is working in "inetd" mode.
>
> Brian Kelly
>
>
>
>
>
>
> "Jason Tishler" <jason AT tishler DOT net>@cygwin.com on 08/11/2003 07:10:45 AM
>
> Sent by: cygwin-owner AT cygwin DOT com
>
>
> To: cygwin AT cygwin DOT com
> cc: (bcc: Brian Kelly/WTC1/Empire)
>
> Subject: Re: proftpd issues
>
>
> Brian,
>
> On Sat, Aug 09, 2003 at 09:12:57AM -0400, Brian Kelly wrote:
> > I'm sorry Igor, I'm not giving you enough info. proftpd is being
> > called from xinetd which itself is being launched via init. *telnet*
> > works fine and authenticates BOTH local and domain ID's. So that
> > *should* - correct me if I'm wrong - eliminate the passwd and group
> > file entries as culprits. Especially since I'm using the very same
> > domain ID for my testing.
>
> Does /var/log/ProFTPD.log indicated anything interesting when
> authentication fails. Can you strace the problem? What happens when
> you run proftpd in stand-alone mode -- not under xinetd?
>
> > Furthermore, if I change the ftp daemon to the one supplied with
> > inetutils, Domain authentication works again.
>
> FWIW, the authentication code in proftpd was copied from inetutils's
> ftpd.
>
> Jason
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -