This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig030BC0BA05B1723CF1CF8054
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
schrieb Harald Schmalzbauer am 25.10.2010 23:20 (localtime):
> Hello,
>=20
> am I complete stupid or is there a serious problem with 8.1-RELEASE:
> I can write files which I have no write access to, if I have write
> access to the directory of the file.
=2E..
> This means file permission mode is irrelevant if the user has write
> access to the directory of the file. I can hardly believe that this is
> intentional. Why does a write lead to owbership changes?
> How should I give users write access to directories but prohibit
> deliting particular files? Do I have to use uunlnk flag?
> Sorry for that basic question, but I must have been missing something i=
n
> the last 10 years...
Sorry for the noise,
digging through lots of not-deep-enough information I finally found:
http://content.hccfl.edu/pollock/aunix1/filepermissions.htm
Now I can remember that I already was upset about this, one decade ago,
and there was a reason not to use the POSIX permission model at all for
so long.
In that particular case I'll have to use the uchg flag.
Sorry again for the noise!
--------------enig030BC0BA05B1723CF1CF8054
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkzF+LcACgkQLDqVQ9VXb8joMQCfUmAMzZiAqFbAvIwIiIrZFVy/
eZEAmQFNOS9QEqmjNJ47Jq9d/wn3qPlZ
=RFgP
-----END PGP SIGNATURE-----
--------------enig030BC0BA05B1723CF1CF8054--