Existing users, 
 SyncUp - 2.0utility to perform synchronizing backups |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: |   (1.0) |
Features: | (1.0) |
Support: | (1.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | (1.0) |
Price: | (5.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
installer permissions "ScrewUp" - Version: 2.0, 1/16/2005 02:53PM PST
Hal Itosis
I can verify some user complaints which have preceded. My PowerBook G4 running 10.3.7 has but two accounts: the 'main' admin created when the computer was first run (uid=501), and a second user severely limited (uid=502). Beyond those two users, login as 'root' has also been enabled.
I ran the SyncUp installer while logged in as the main admin (501). I immediately noticed that the SyncUp folder in /Applications belonged to user 502 (wtf!?). So I logged in as root and repaired the SyncUp manually (using Terminal).
Then I decided to investigate further. To my utter surprise, a number of OTHER items had also be changed to grant exclusive ownership to uid 502. This command in Terminal will summarize the errors:
Interestingly enough, repairing permissions with Disk Utility did not clear out all the errors:
Determining correct file permissions.
User differs on ./Applications, should be 0, owner is 502
Group differs on ./Applications, should be 80, group is 502
Owner and group corrected on ./Applications
Permissions corrected on ./Applications
We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util. New permissions are 33261
User differs on ./usr, should be 0, owner is 502
Group differs on ./usr, should be 0, group is 502
Owner and group corrected on ./usr
Permissions corrected on ./usr
User differs on ., should be 0, owner is 502
Group differs on ., should be 80, group is 502
Owner and group corrected on .
Permissions corrected on .
The privileges have been verified or repaired on the selected volume
Disk Utility's repair omitted the following items:
If the SyncUp installer is fraught with such mistakes,
what confidence should we feel about the app itself?
-HI-
I ran the SyncUp installer while logged in as the main admin (501). I immediately noticed that the SyncUp folder in /Applications belonged to user 502 (wtf!?). So I logged in as root and repaired the SyncUp manually (using Terminal).
Then I decided to investigate further. To my utter surprise, a number of OTHER items had also be changed to grant exclusive ownership to uid 502. This command in Terminal will summarize the errors:
ls -halon / /usr /usr/local /usr/local/bin | grep 502
drwxrwxr-t 45 502 502 - 1K 16 Jan 15:05 .
drwxrwxr-t 45 502 502 - 1K 16 Jan 15:05 ..
-rw-r--r-- 1 502 502 - 6K 10 Dec 09:04 .DS_Store
drwxrwxr-x 61 502 502 - 2K 16 Jan 15:05 Applications
drwxr-xr-x 10 502 502 - 340B 16 Jan 15:05 usr
drwxr-xr-x 10 502 502 - 340B 16 Jan 15:05 .
drwxrwxr-t 45 502 502 - 1K 16 Jan 15:05 ..
-rw-r--r-- 1 502 502 - 6K 3 Dec 06:17 .DS_Store
drwxr-xr-x 6 502 502 - 204B 16 Jan 15:05 local
drwxr-xr-x 6 502 502 - 204B 16 Jan 15:05 .
drwxr-xr-x 10 502 502 - 340B 16 Jan 15:05 ..
-rw-r--r-- 1 502 502 - 6K 3 Dec 06:17 .DS_Store
drwxr-xr-x 27 502 502 - 918B 16 Jan 15:05 bin
drwxr-xr-x 27 502 502 - 918B 16 Jan 15:05 .
drwxr-xr-x 6 502 502 - 204B 16 Jan 15:05 ..
-rwxr-xr-x 1 502 502 - 229K 3 Dec 06:13 rsync
Interestingly enough, repairing permissions with Disk Utility did not clear out all the errors:
Determining correct file permissions.
User differs on ./Applications, should be 0, owner is 502
Group differs on ./Applications, should be 80, group is 502
Owner and group corrected on ./Applications
Permissions corrected on ./Applications
We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util. New permissions are 33261
User differs on ./usr, should be 0, owner is 502
Group differs on ./usr, should be 0, group is 502
Owner and group corrected on ./usr
Permissions corrected on ./usr
User differs on ., should be 0, owner is 502
Group differs on ., should be 80, group is 502
Owner and group corrected on .
Permissions corrected on .
The privileges have been verified or repaired on the selected volume
Disk Utility's repair omitted the following items:
localhost:~ root# ls -halon / | grep 502
-rw-r--r-- 1 502 502 - 12K 16 Jan 15:41 .DS_Store
localhost:~ root# ls -halon /usr | grep 502
-rw-r--r-- 1 502 502 - 6K 16 Jan 15:41 .DS_Store
drwxr-xr-x 6 502 502 - 204B 16 Jan 15:05 local
localhost:~ root# ls -halon /usr/local | grep 502
drwxr-xr-x 6 502 502 - 204B 16 Jan 15:05 .
-rw-r--r-- 1 502 502 - 6K 16 Jan 15:41 .DS_Store
drwxr-xr-x 27 502 502 - 918B 16 Jan 15:05 bin
localhost:~ root# ls -halon /usr/local/bin | grep 502
drwxr-xr-x 27 502 502 - 918B 16 Jan 15:05 .
drwxr-xr-x 6 502 502 - 204B 16 Jan 15:05 ..
-rwxr-xr-x 1 502 502 - 229K 3 Dec 06:13 rsync
If the SyncUp installer is fraught with such mistakes,
what confidence should we feel about the app itself?
-HI-
BE CAREFULL with this one... - Version: 2.0, 1/15/2005 03:25PM PST
(1 of 3 users found this comment useful)
wsheluk
I gave this programme a trial run and discovered after installing I could not change the names of folders. I did a Finder/trash since there is no uninstaller! Now that's bad!!! Then I had to reinstall 10.37 combo to get back to normal. This app is not for me!
first of all i would like to make clear that the installer.app is done by apple, not by me.
the "magic" it does is simply preserving ownership of all the files it copies.
unfortunately there is no way to change it.
in my case - my useid is 502. a user not present on most systems. (the first admin user has userid 501)
and when the installer copies the files, they are owned by 502. which is no problem since it does not exist and the app needs to be executeable by everyone anyway.
/usr/local/bin is also not present on most systems, so when the installer copies it, it belongs to - you guess it right - 502.
so - no magic changing on your security. just file copying.
i would very much like to give you the app without installer but i cannot include rsyncx in the bundle for legal reasons.
all other issues describe are unrelated to my software or the installer.
the most interesting thing about all that is - that noone of you ever tried to contact me. the email is present in the readme file and i usually answer all support questions.
instead you just complain here.
makes me a little sad - think of the time i invested writing the app.
regards
thomas