I found the right intel via Google on installing ProFTPD on OSX @ http://www.unibia.com/unibianet/os-x/install-proftpd
This particular piece of information made my day: "ProFTPD will by default use PAM to get system account information. This first needs to be enabled in OS X, otherwise users will not be able to log in with ProFTPD. The built in OS X FTP server utilizes the "/private/etc/pam.d/ftpd" authentication module. While ProFTPD is looking for "/private/etc/pam.d/ftp". Using the terminal, we will make a copy of the OS X FTP PAM module for ProFTPD." ProFTPD looks for /private/etc/pam.d/ftp. To make ProFTPD happy you can: $ sudo cp /private/etc/pam.d/ftpd /private/etc/pam.d/ftp Password: And then voila! ftp jas...@localhost Trying ::1... ftp: Can't connect to `::1': Connection refused Trying fe80::1%lo0... ftp: Can't connect to `fe80::1%lo0': Connection refused Trying 127.0.0.1... Connected to localhost. 220 ProFTPD 1.3.2c Server (ProFTPD Default Installation) [127.0.0.1] 331 Password required for jasper Password: 230 User jasper logged in Remote system type is UNIX. Using binary mode to transfer files. ftp> It would be useful if a tip on this is given after the MacPort proftpd has been built or if the building/compiling of ProFTPD is adjusted to look for pam where OSX has it stored under. Anyways, happy I got it working... On Mon, Feb 8, 2010 at 2:47 AM, Peter B. West <[email protected]> wrote: > > On 08/02/2010, at 2:06 AM, Jasper Frumau wrote: > > > On Sun, Feb 7, 2010 at 6:47 PM, Jasper Frumau <[email protected]> > wrote: > > > > > ... > > 'cat /etc/passwd' -- the user names are the first thing in the lines. > That's how it works on other unices, anyway. OS X seems to have put my > username somewhere else; there are lots of names there, but I'm not in that > list. > > > > Mine isn't either > > > > When I checked /etc/passwd one more time I read: > > > > cat /etc/passwd > > ## > > # User Database > > # > > # Note that this file is consulted directly only when the system is > running > > # in single-user mode. At other times this information is provided by > > # Open Directory. > > # > > # This file will not be consulted for authentication unless the BSD local > node > > # is enabled via /Applications/Utilities/Directory Utility.app > > # > > # See the DirectoryService(8) man page for additional information about > > # Open Directory. > > > > I cannot find an app Directory Utility in my Snow Leopard apps though. I > am reading more about Open Directory and Mac now... > > Access through System Preferences, Accounts. Login Options. Then in Network > Account Server either Edit or Join, then Open Directory Utility. Unlock and > authenticate. > > Peter > >
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
