Building on what exvor has said, a group can be designated for file sharers. A user can then create a subdirectory in his $HOME, and set the group to the sharers group. If the setgid bit is set on this directory, files created there will also have the same group. Then anyone in the sharers group can access another users shared directory and its files.
|
Quote:
Hmmm... I guess this is the most practical way forward. Shame it can't be done in a cleaner fashion though. It's quite a big ask for a newb. I'm going to implement this asap. May have to come back for more detailed help :-) S |
Quote:
You don't think it's weird that all and sundry can wonder around inside your account and check out anything they wish to have a look at !?! :-) I also don't get the logic behind specifically naming a directory 'Public' when all folders are public. It's really counter-intuitive for a Win-convert. Anyway... I'm getting on my hobby-horse... Really appreciate all the kind suggestions given. S |
Quote:
The next machines I used were DEC Alpha. These were mutli user machines, workstations and servers that you connected to with XTerminals. You data was safe from being corrupted by others since you had your own account and only you or the sys admin could modify your files. Why hide your files by default? They were never hidden on the old single user operating systems. If for some reason you did have something to hide, you could hide it. And if you really wanted to hide it so even the sys adim couldn't see it you pgp encrypt it. Quote:
Cheers, Evo2. |
evo2,
Quote:
These days people are brought up on multi-user boxes, Windows primarily, which consider privacy as important as security. I personally think this is a sensible approach. *Given* that the modern approach is that things are private by default, I feel the Linux way is out of sync and is, to me at least, a major hindrance to wider adoption by the Windows crowd. Things move on. If Linux is to be seen to be an OS for non-geeks, it needs to take on board some of the basic expectations users have these days. (No, I don't mean expectations regarding crashes and Viruses ;-) BTW, you've really put me out of considerable misery by explaining the 'Public' folder naming. I still think it's crazy but at least I can see *some* logic there :-) S |
Quote:
Quote:
Quote:
Usually I only have a few private stuff - that is basically my PGP private keys - hey and guess what - I noticed that they have not the world readable attributes. So it seems that is quite ok. But: I think in an office where probably several secretaries are sharing the same PC things are a little different. But company IT will get the security changed in such cases... |
mwildam,
Quote:
Quote:
Quote:
At the moment we get an extreme where anyone can look at anything, unless you are savvy enough to make the changes necessary. Most people aren't that savvy and I personally don't think they should have to be as it would be so simple to have a setup which covers all the bases. In this day and age I think it's madness to assume a 'Safe Environment', as is the present case. I would personally veer towards as 'As secure/private as is reasonably possible' as a default. Of course it's easy to become an extremist there as well ;-) S |
All times are GMT -5. The time now is 03:54 PM. |