On Thu, Jul 28, 2016 at 2:49 PM, László Házy <haz...@yahoo.com> wrote:
> [root]# cat /usr/lib/sysctl.d/50-default.conf | grep fs > fs.protected_hardlinks = 1 > fs.protected_symlinks = 1 > You can change those parameters in the file. Or you can do a test by doing: sysctl -w fs.protected_hardlinks=0 sysctl -w fs.protected_symlinks=0 > > > I guess this explains it. Problem is (my problem now) that it breaks the > startup scripts of a $50000 software, which does work on an older > FedoraCore. Is this a kernel problem then? > > Thanks to all for your help. > > > On Thu, 2016-07-28 at 21:06 +0200, Piotr Grzybowski wrote: > > yeah, thats why I asked about version, but never mind that, Laszlo: I would > like to see : > > cat /usr/lib/sysctl.d/50-default.conf | grep fs > > pg > > > > On 28 Jul 2016, at 20:56, Charles Daffern wrote: > > > > As far as I'm aware, the inability to use symlinks owned by another user > in a sticky directory is a security feature of some kernels. It helps to > prevent symlink attacks. > > > > -- Klein bottle for rent -- inquire within. Maranatha! <>< John McKown
