| Now I have just one major league problem: when I logged in as one
| users, to test the connections, I discovered that I had SUPER
| was able to delete any file that I could see, including ones that
| owned by root. Digging uncovered the fact that pure-ftpd runs
| privileges... not so good for my situation.
| My guess is I need to compile with the --with-privsep switch
| So, finally I have a real FreeBSD question!
| What is the proper way, in ports, to set a configuration flag?
| way I could figure out was to add it to the Makefile.
| PRIVSEP "Enable privilege separation" on \
| If this is the correct way to turn this compile switch on, it
| seem to work. After running:
| make deinstall
| make config # checking the privilage separation box
| make reinstall
| The logged in user can still delete any file, regardless of
| or ownership. This is clearly a problem... I don't want my users
| able to blow away their own websites while they are uploading some
| images. I am still digging for info on this problem. Any
| -- John
Try this sequence instead, and you should be all set:
make config (skip this if you've already chosen the options you want)
The clean target will make sure that your environment is reset back
known state. The install target will then perform a fresh build and
install with the privsep option enabled. If you already had
your port directory, then the reinstall target installs them without
rebuilding, as far as I can tell from reading /usr/ports/Mk/
I tried your sequence, but it didn't seem to work. Or, perhaps it
worked and the PRIVSEP option doesn't do what I expect it to. Logging
in as a normal user gives that user root privileges.
This seems pretty scary to me. Not so bad, since the user is locked
into his own directory, but enough power to hurt themselves, which is
too much power, IMHO. My users aren't experts. I can definitely see
them clicking the delete key by accident.
Back to digging for info...
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"