On Mon, Aug 11, 2003 at 11:27:33AM -0400, Igor Pechtchanski wrote:
> Jason, do you think this inability to validate UNC paths stems from
> proftpd prepending a "/" to the path or something?
No, AFAICT, I have already address this problem in the following:
http://bugs.proftpd.org/show_bug.cgi?id=2075
> I mean, Cygwin syscalls should be able to access the UNC path with no
> problems...
Agreed.
> Is this worth investigating?
I guess so, but I don't really have the "itch."
Brian, would you be willing to help? What do you mean by "validate" in
the following?
> On Mon, 11 Aug 2003 Brian Kelly wrote:
> > 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.
What is the exact error message in proftpd's log file when the home
directory is specified in UNC?
Thanks,
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
--
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/
