On Thu, Jul 28, 2016 at 2:49 PM, László Házy 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.
[root]# cat /usr/lib/sysctl.d/50-default.conf | grep fs
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
I guess this explains it. Problem is (my problem now) that it breaks
the startup scripts of a $5 software, which does work on an older
FedoraCore. Is this a kernel problem then?
Thanks t
On 7/28/16 2:19 PM, Piotr Grzybowski wrote:
>
> ok, so if we now have discovered that it is +t that makes the difference and
> also that it is not a bash bug, I wonder what kernel version are you running?
> did Chet tests include sticky bit and the same kernel?
It's a more-or-less vanilla Fedo
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 i
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.
signature.asc
Description: OpenPGP digital signature
ok, so if we now have discovered that it is +t that makes the difference and
also that it is not a bash bug, I wonder what kernel version are you running?
did Chet tests include sticky bit and the same kernel?
pg
On 28 Jul 2016, at 19:46, László Házy wrote:
> I did, and then everything works
On 7/28/16 12:52 PM, László Házy wrote:
> Thanks for the effort Chet. Here are the results of some tests I have done,
> including what you requested. Note that I have SELinux as disabled.
>
> [user1]# cat /var/tmp/link
> cat: /var/tmp/link: Permission denied
This is consistent with my results.
I turned it off from /etc/selinux/config and then rebooted the
computer. I'll read up on the bug you mentioned.
On Thu, 2016-07-28 at 03:28 -0400, Siteshwar Vashisht wrote:
> - Original Message -
> >
> > From: "László Házy"
> > To: "Greg Wooledge"
> > Cc: bug-bash@gnu.org
> > Sent: Thurs
- Original Message -
> From: "László Házy"
> To: "Greg Wooledge"
> Cc: bug-bash@gnu.org
> Sent: Thursday, July 28, 2016 2:18:55 AM
> Subject: Re: bug in [ -f file ] test
>
> I had disabled SELinux, and got the same results. So it is not SELinux.
How did you turn off SELinux ? Was it tur
