| Summary: | default umask set wrong on new build server? | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> |
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
David Williams
and ... probably more important ... I think the setgid needs to be set on the build id home directories (right?) I can set it to 0002 but that is more restrictive than 022. Not likely the cause. But good catch, though. It should be set to the more secure 0002. As for the setgid, it doesn't really matter, since the entire group will not be accessing files inside the user's home directory. ok, must be something else ... and ... in the course of "fixing" my directory file permissions, I think I messed up my .ssh directory and files, and now can't seem to set the permissions correct on those ... I've tried setting .ssh and authorizedkeyss to u=rw (only) ... but didn't see to fix. I can ssh with password, but not with my key (but, could earlier). (In reply to comment #3) > ok, must be something else ... and ... in the course of "fixing" my directory > file permissions, I think I messed up my .ssh directory and files, and now > can't seem to set the permissions correct on those ... I've tried setting .ssh > and authorizedkeyss to u=rw (only) ... but didn't see to fix. I can ssh with > password, but not with my key (but, could earlier). Oh ... I meant to say ... any advice? (In reply to comment #4) > (In reply to comment #3) > > ok, must be something else ... and ... in the course of "fixing" my directory > > file permissions, I think I messed up my .ssh directory and files, and now > > can't seem to set the permissions correct on those ... I've tried setting .ssh > > and authorizedkeyss to u=rw (only) ... but didn't see to fix. I can ssh with > > password, but not with my key (but, could earlier). > > Oh ... I meant to say ... any advice? I fixed (I guess) by changing my wtpBuild home directory back to g=rx ... ssh doesn't like rws in the home directory (I guess). (In reply to comment #2) > I can set it to 0002 but that is more restrictive than 022. Are you sure? (Doesn't that sound funny ... me asking _you_ that? :) umask -S 022 ==> u=rwx, g=rx, o=rx umask -S 0002 ==> u=rwx, g=rwx, o=rx (I always have to revert to symbols ... I've mastered hex ... but octal throws me off :) I've had a little history with this umask problem in the past, such as bug 299185 and bug 300296 (where 0002) seem'd right answer, but in other places, 022 seemed the right answer (e.g. bug 292629#c35) ... so, obviously, I'm always getting these values confused. But seems to me 0002 cases directories to be created with group write permissions set. I believe the umask issue here is fixed (right?) so closing. That is, default is now 0002 with I think works better in combination with setting guid bit 'on'. One of the files I could not delete in the past, is now created by hudsonBuild with enough permissions I can delete from my david_williams group membership in callisto-dev: -rw-rw-r-- 1 hudsonBuild callisto-dev 219K 2010-09-30 16:17 artifacts.jar thanks |