Thu, 27 Sep 2007, by [EMAIL PROTECTED]:

> On Wednesday 26 September 2007 23:41, Theo v. Werkhoven wrote:
> > Wed, 26 Sep 2007, by [EMAIL PROTECTED]:
> > > Hi
> > > I have setup a vsftpd server and it works fine. Users can login and are
> > > chroote'd to their home folders.
> > >
> > > I have allowed myself to break out of the chroot because I want to manage
> > > files under /srv/www/htdocs remotely. But I do not have permissions to do
> > > anything there. Stuff under htdocs is owned by root:root on the server
> > > but ftp'ing in here it's owned by 0:0. How can I give myself permission
> > > to the htdocs folder?
> >
> > Make htdocs owned by another user. I've setup an 'ftpadmin' user for this.
> > Let htdocs be the (chrooted) home dir of ftpadmin and logged in as this
> > user you can do what you need.
> >
> Thanks Theo. Just one more question. What group does ftpadmin belong to? Will 

I'v also setup an 'ftpadmin' group for this user.

> there be any permission issues if I do that? Will the permissions be 
> preserved? Some need 777, others 666, others 600.

The vsftpd I admin chowns incoming files (for virtual users) to UID
'virtual', GID 'virtual'. Every 5 mins a script runs on the files to
chown them to 'ftpadmin', so this user can move or delete them.
The permissions are not changed.

$ tree -dug /srv/ftp/
/srv/ftp/
`-- [ftpadmin root    ]  virtual
    |-- [ftpadmin virtual ]  AAAA
    |   |-- [ftpadmin virtual ]  From_Company
    |   `-- [ftpadmin virtual ]  To_Company

$ getent passwd ftpadmin
ftpadmin:x:111:112:FTP admin account:/srv/ftp/virtual/:/bin/bash

$ getent group ftpadmin
ftpadmin:!:112:

Theo
-- 
Theo v. Werkhoven    Registered Linux user# 99872 http://counter.li.org
ICBM 52 13 26N , 4 29 47E.     +      ICQ: 277217131
SUSE 10.2                      +   Jabber: [EMAIL PROTECTED]
Kernel 2.6.20                  +   See headers for PGP/GPG info.
Claimer: any email I receive will become my property. Disclaimers do not apply.
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to