Re: [PATCH 2/3] fstests: test restricted symlinks & hardlinks sysctls

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]



On 5/18/20 9:42 AM, Eric Sandeen wrote:
>>> +test_symlink()
>>> +{
>>> +	ln -s $TEST_DIR/$seq/target $TEST_DIR/$seq/sticky_dir/symlink
>>> +	chown $OTHER.$OTHER $TEST_DIR/$seq/sticky_dir
>>> +	chown $OWNER.$OWNER $TEST_DIR/$seq/sticky_dir/symlink
>>> +	# If we can read the target, we followed the link
>>> +	sudo -u $OTHER cat $TEST_DIR/$seq/sticky_dir/symlink 2>&1 \
>> Use _user_do instead of sudo?
> but OTHER is "fsgqa2;" _user_do uses "fsgqa" .... hrm.  I suppose I could
> update _user_do to take a username, but is it worth it?
>  
> Maybe I should just make one of the users root, I'm just worried about accidentally
> running into admin capabilities...

Actually I'll just re-use 123456-fsgq for OWNER, then OTHER can be fsgqa, and
I'll use _user_do.

Thanks,
-Eric



[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux