Hi! Thanks for the answer. On Sun, 24 Oct 2004 01:47:43 +0900, - Edwin - <copperwa11s@yahoo.co.jp> wrote:
I think the problem stems from the fact that when you add a new user using YaST (using all default settings), the default group would be "users" and the permissions on the home directory would be something like this:
drwxr-xr-x
Yes, this is what happens.
So, yes, this is *not* good since the group "other" will have read + execute permissions on one's home directory. Also, [...]
(I thought be default Linux was more secure...)
Well, maybe this is true for the "Personal" or "Professional" versions of *SUSE* Linux ;) (Not sure about the server version since I haven't tried it.)
We do have one SuSE "server" at work, but it's actually 64bit Professional 9.0 :-)
Apparently there's a problem, IMHO, with the current implementation in YaST when adding users using the default settings. Anyway, I'm sure not all linux distros behave the same way. Besides, there's a "fix" for that default behavior of YaST -- see below.
YaST is actually the reason why I chose SuSE. I saw it at work and I thought that it is the best things I've seen in Linux for some time. It still needs lot's of work (install samba, start samba, add users... ups, no way to add users for samba :-), but it's getting there.
Somebody already mentioned about "chrooting" or "scponly" so let me just mention a completely different approach. [snip] Apache+SSL+WebDAV+acl
That is actually interesting... thanks. I'll look into that too.
Besides, if those who need to transfer files remotely are using Windows, they just need to "Add a Network Place" and no need to install additional programs.
Even more interesting! -- HG