Jump to content

iwelt

Members
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About iwelt

  • Rank
    Occasional Forum Poster
  1. Hi waltr thank you for your post. Unfortunately I'm not a expert in securing linux so i do not know where to look for the settings you mentioned. Only thing I found is that the default umask is 022. But i don't think thats the point, because this misbehaviour involves files owned by different users/groups Maybe this more "real world" example might show what i mean: Retrospect-Test-Files: total 348 -rwsr-xr-x 1 root root 68440 Sep 18 09:04 mount -rwsr-xr-- 1 root dip 265880 May 5 2005 pppd -rwsr-x--- 1 root www-run 10596 Sep 5 13:16 suexec2 Restored-Retrospect-Test-Files: total 348 -rwsr-xr-x 1 root root 68440 Sep 18 09:04 mount -rwxr-xr-- 1 root dip 265880 May 5 2005 pppd -rwxr-x--- 1 root www-run 10596 Sep 5 13:16 suexec2 As mentioned above, SGID/SUID will only be restored correctly if user AND group is root. We DID a complete restore and ran into this problem, that's how we found that issue. After restoring the apache suexec doesn't work neither does postfix or spamassasin. Maybe there is something that i don't see or something i don't know? thanks in advance Jan
  2. Hi there! I'm still having this problem and obviously noone can help me. Maybe my english is too bad for describing the problem the right way? Thanks in advance
  3. Additional information: I've also testet this on Redhat 9 with same results.
  4. I have a problem with restoring files on linux clients. Files with SUID or SGID set will not be restored correctly if one of owner or group of the file is NOT root. Here is an example: Original Files: retrotest:/test# l misc/ total 3172 drwxr-xr-x 2 root root 4096 2005-07-05 16:08 sbin -rwxr-s--- 1 nobody nogroup 265880 2005-07-05 18:23 test_sgid-nobody_nogroup -rwxr-s--- 1 nobody root 265880 2005-07-05 18:23 test_sgid-nobody_root -rwxr-s--- 1 root nogroup 265880 2005-07-05 18:24 test_sgid-root_nogroup -rwxr-s--- 1 root root 265880 2005-07-05 18:24 test_sgid-root_root -rwsr-x--- 1 nobody nogroup 265880 2005-07-05 18:15 test_suid-nobody_nogrooup -rwsr-x--- 1 nobody root 265880 2005-07-05 18:20 test_suid-nobody_root -rwsr-x--- 1 root nogroup 265880 2005-07-05 18:15 test_suid-root_nogroup -rwsr-x--- 1 root root 265880 2005-07-05 18:15 test_suid-root_root -rwsr-s--- 1 nobody nogroup 265880 2005-07-05 18:15 test_suid_sgid-nobody_nogroup -rwsr-s--- 1 nobody root 265880 2005-07-05 18:20 test_suid_sgid-nobody_root -rwsr-s--- 1 root nogroup 265880 2005-07-05 18:15 test_suid_sgid-root_nogroup -rwsr-s--- 1 root root 265880 2005-07-05 18:15 test_suid_sgid-root_root Restored Files: retrotest:/test# l misc/ total 3172 drwxr-xr-x 2 root root 4096 2005-07-05 16:08 sbin -rwxr-x--- 1 nobody nogroup 265880 2005-07-05 18:23 test_sgid-nobody_nogroup -rwxr-x--- 1 nobody root 265880 2005-07-05 18:23 test_sgid-nobody_root -rwxr-x--- 1 root nogroup 265880 2005-07-05 18:24 test_sgid-root_nogroup -rwxr-s--- 1 root root 265880 2005-07-05 18:24 test_sgid-root_root -rwxr-x--- 1 nobody nogroup 265880 2005-07-05 18:15 test_suid-nobody_nogrooup -rwxr-x--- 1 nobody root 265880 2005-07-05 18:20 test_suid-nobody_root -rwxr-x--- 1 root nogroup 265880 2005-07-05 18:15 test_suid-root_nogroup -rwsr-x--- 1 root root 265880 2005-07-05 18:15 test_suid-root_root -rwxr-x--- 1 nobody nogroup 265880 2005-07-05 18:15 test_suid_sgid-nobody_nogroup -rwxr-x--- 1 nobody root 265880 2005-07-05 18:20 test_suid_sgid-nobody_root -rwxr-x--- 1 root nogroup 265880 2005-07-05 18:15 test_suid_sgid-root_nogroup -rwsr-s--- 1 root root 265880 2005-07-05 18:15 test_suid_sgid-root_root (note: green = restored correctly red = not restored correctly ) As you can see, only files which are owned by user root AND group root are restored with the SUID/SGID-bit set correctly. All other combinations of owner/group leads to missing SUID/SGID-bits on the restored files. I've been running into this using retrospect Multi-Server 6.5.350 and Linux client 6.5.108 I've also tried the new retrospect Server 7 and had no luck: Retrospect Server 7.0.301 with Update 7.0.5.102 Retrospect Client 7.0.109 Operating systems tested: Server: Windows 2000 Professional, Windows XP Professional Client: Fedora Core2, Debian 3.1 Is this is a fatal bug?
×