Re: ACL: Default and other problems
Chuck Swiger [Tue, Oct 24, 2006 at 09:21:51AM -0700]: [...] Now I am interested on how you would solve this problem with standard Unix-Ids without using external tools (like callin chown/chgrp/chmod each update). This constraint makes the problem impossible to solve. Either you are interested in the impossible, or you aren't really looking to solve the problem using standard Unix mechanisms... Actually, I am really not looking for 'old Unix mechanism' to solve that issue, because I think ACLs are definetly made for this kind of problem. I've been using ACLs on Linux for some years now and I am really wondering why simply applying the default ACLs is such a problem in fbsd. As far as I know, ACLs are considered stable in FreeBSD, aren't they? I am really wondering who to contact for the issues I've reported on [0]. Thanks for any hints, Nico [0]: http://home.schottelius.org/~nico/freebsd/acl/ -- ``...if there's one thing about Linux users, they're do-ers, not whiners.'' (A quotation of Andy Patrizio I completely agree with) signature.asc Description: Digital signature
Re: ACL: Default and other problems
On Oct 25, 2006, at 5:33 AM, Nico -telmich- Schottelius wrote: This constraint makes the problem impossible to solve. Either you are interested in the impossible, or you aren't really looking to solve the problem using standard Unix mechanisms... Actually, I am really not looking for 'old Unix mechanism' to solve that issue, because I think ACLs are definetly made for this kind of problem. OK. I've been using ACLs on Linux for some years now and I am really wondering why simply applying the default ACLs is such a problem in fbsd. As far as I know, ACLs are considered stable in FreeBSD, aren't they? 5.3 was the earliest stable release of 5.x; the TrustedBSD project has been importing improvements and so forth since 5.3 was released. You might want to retry your tests with FreeBSD 5.5 or 6.2 and see whether things have improved since then. I am really wondering who to contact for the issues I've reported on [0]. Thanks for any hints, Nico [0]: http://home.schottelius.org/~nico/freebsd/acl/ You should probably use send-pr to file a bug report, and list your test-cases in it. If you can write a patch to improve or fix any mis- behavior by the tools dealing with ACLs, that will help... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACL: Default and other problems
Looks like noone is really using ACLs (and default ACLs) on fbsd. classic unix uid/gid is simplest and enough for MOST (or every - i think) cases. it just needs to be used right Please imagine this. We're running a web server and want each user to be able to modify/delete files created (owned) by Apache user if the file is in that particular users home directory. Maybe this is possible with just uid/gid if every new file created within this directory has the users group and the permissions 664 or even 775, how would this be done (forcing new files group identity and permissions). Thanks, -Patrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACL: Default and other problems
Wow, sombody even reads this thread! Wojciech Puchar [Mon, Oct 23, 2006 at 07:43:47PM +0200]: posted a question about ACLs because I'm having difficulties setting up default ACLs. My question was posted 11/10 but I haven't got an answer yet. Looks like noone is really using ACLs (and default ACLs) on fbsd. classic unix uid/gid is simplest and enough for MOST (or every - i think) cases. it just needs to be used right Situation: - git running on fbsd 5.3. - 4 people work on the same project - git is used over ssh (aka git+ssh://) - when new objects are created, they belong to the creating user - normal umask is 077 (we are all paranoid) We want that every newly created file and directory is modifyable by any user of the 'git' group. Now I am interested on how you would solve this problem with standard Unix-Ids without using external tools (like callin chown/chgrp/chmod each update). Sincerly Nico -- ``...if there's one thing about Linux users, they're do-ers, not whiners.'' (A quotation of Andy Patrizio I completely agree with) signature.asc Description: Digital signature
Re: ACL: Default and other problems
On Oct 24, 2006, at 1:32 AM, Nico -telmich- Schottelius wrote: Situation: - git running on fbsd 5.3. - 4 people work on the same project - git is used over ssh (aka git+ssh://) - when new objects are created, they belong to the creating user - normal umask is 077 (we are all paranoid) We want that every newly created file and directory is modifyable by any user of the 'git' group. Have git be setgid to this git group and call umask() to 027. Or write a trivial shell-script wrapper to reset the umask, if you want to do it that way. Now I am interested on how you would solve this problem with standard Unix-Ids without using external tools (like callin chown/chgrp/chmod each update). This constraint makes the problem impossible to solve. Either you are interested in the impossible, or you aren't really looking to solve the problem using standard Unix mechanisms... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACL: Default and other problems
Patrik Jansson [Thu, Oct 19, 2006 at 09:38:36AM +0200]: I would also like to know if there's a in-depth ACL documentation. I posted a question about ACLs because I'm having difficulties setting up default ACLs. My question was posted 11/10 but I haven't got an answer yet. Looks like noone is really using ACLs (and default ACLs) on fbsd. I am currently using some git-hooks to set the permissions on every update, but I am thinking about replacing the server with Linux using jfs or ext3 as filesystem, because those are tested and working with default ACLs. And without the need to readd the already existent permissions. Nico signature.asc Description: Digital signature
Re: ACL: Default and other problems
posted a question about ACLs because I'm having difficulties setting up default ACLs. My question was posted 11/10 but I haven't got an answer yet. Looks like noone is really using ACLs (and default ACLs) on fbsd. classic unix uid/gid is simplest and enough for MOST (or every - i think) cases. it just needs to be used right ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACL: Default and other problems
I experiemented with the ACls under fbsd 5.3 and got some problems with how freebsd calculates the permissions. I followed the instructions on [0]. My aim is to install default ACLs, so a group of users (with possible broken umask) can work together on git-repositories. The idea is that the default ACL will provide ACL-based rwx access for the group 'git' (minus real permissions / mask makes rw or rwx for files, rwx for directories). I've mostly problems with default ACLs and the new permissions. I put two test-scripts to [1], plus their output (*.output) and the questions I've to the results (*.question) on a website. Any pointers on what I did wrong or in depth FreeBSD-ACL documentation are appreciated. I would also like to know if there's a in-depth ACL documentation. I posted a question about ACLs because I'm having difficulties setting up default ACLs. My question was posted 11/10 but I haven't got an answer yet. Cheers, Patrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ACL: Default and other problems
Hello! I experiemented with the ACls under fbsd 5.3 and got some problems with how freebsd calculates the permissions. I followed the instructions on [0]. My aim is to install default ACLs, so a group of users (with possible broken umask) can work together on git-repositories. The idea is that the default ACL will provide ACL-based rwx access for the group 'git' (minus real permissions / mask makes rw or rwx for files, rwx for directories). I've mostly problems with default ACLs and the new permissions. I put two test-scripts to [1], plus their output (*.output) and the questions I've to the results (*.question) on a website. Any pointers on what I did wrong or in depth FreeBSD-ACL documentation are appreciated. Sincerly Nico [0]: http://ezine.daemonnews.org/200310/acl.html [1]: http://home.schottelius.org/~nico/freebsd/acl/ signature.asc Description: Digital signature
