Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Two ways to possibly close an ARDAgent security hole' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Two ways to possibly close an ARDAgent security hole
Authored by: mike3k on Jun 20, '08 10:31:20AM
You could simply clear ARDAgent's setuid bit:
sudo chmod 755 /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent


Now I get the result:
$ osascript -e 'tell app "ARDAgent" to do shell script "whoami"'
mike


[ Reply to This | # ]
Two ways to possibly close an ARDAgent security hole
Authored by: gxw on Jun 20, '08 06:25:17PM

Did this too.
Get my user id as the result when I run the command now.
Before the change, running the sample script resulted in a hang and a AppleEvent timed out. (-1712) error. Weird.



[ Reply to This | # ]