[Lukas]

I assume that you have no problem with database settings.

It seems there is no way to have ProFTP working without setting the user homedir world writeable. The problem is that every dir you have to open, in order to reach the specified homedir, must have the same permission. So I moved my /Library/WebServer/www/ to the first level of my hard disk (i.e. /www/). I made it world writeable (chmod 777) and it works correctly.

Remember to set your config file in order to restrict access only to your default directory. Do not forget to specify “DefaultRoot ~/” in the <Global> part.

Hope this helps…

Lukas

[Lukas]

Hi!

Version 1.28 of ProFTPd is out. I tried this one without downloading mod_msql (i.e. using the one enclosed with the source) and everything went well.

Lukas

[Lukas]

Thank’s a lot Cabbage…

Did anything make you think that I posted here because of the fact Mac OS X Server users are much more expert than normal Mac OS X users?

I configured my OS X client following instruction from afp548.com and captainnet.net sites and everything works fine… I only have these little problems… probably Server version is not so different.

You told me “Oh… go back to your Client toy and don’t bother… “…

I think if I need an answer, I will certainly find it in a forum like this… not macosx.com.

Lukas

[Lukas]

Argh Cabbage…. thanks for your quick reply but…
I’m on Mac OS X 10.2.4 CLIENT. I installed ProFTP with MySQL support for users following the Article ProFTP for the Pro on this site.

Is there a way?

Lukas

[Lukas]

Sorry… not logged in… previous post was mine…

Lukas

[Lukas]

I chose to use it as a standalone server, started by a startup item in /Library/StartupItems/, like Postfix and other server software I have on my 10.2.3 client.

I had the same problem with inetd but using inetd was not my idea since the beginning.

About the user problem there is a post a little before this. It seems there is no way to have ProFTP working without setting the user homedir world writeable. The problem is that every dir you have to open, in order to reach the specified homedir, must have the same permission. So I moved my /Library/WebServer/[size=18:2bf23880aa]www[/size:2bf23880aa]/ to the first level of my hard disk (i.e. /[size=18:2bf23880aa]www[/size:2bf23880aa]/). I made it world writeable and it works correctly. What I am not sure of is: how insecure is it now my www folder (and my web and ftp server)? I am waiting for a reply from Didde Brockman, the author of the tutorial. As soon as I hear from him, I will post again.

Hope this helps…

Lukas

[Lukas]

ARGH!!!! Thanx to Xpessdocs!!!

You were right, the problem is that the homedir must be reachable (world writeable). The question is… WHY? If you use Mysql to store user, what is the user ProFTP uses to access the homedir of the logging-in user? That is, what privileges does ProFTP use to access the homedir, if you consider that the logging-in user is not a real unix user? Is it possible that there is no solution to this? I really do not like to leave my dirs world-writeable….

For XPRESSDOCS: I have not so clear the concept of chroot… can you tell me how to use it in tne proftpd.conf in order to protect the hole of the forced world writeable homedir? Thanx a lot

Lukas

[Author]

Posts