![]() ![]() Another drawback to scripted installs is that the vendor may not have a great internet connection. With the script based solution in the hacked scenario, there's no way to tell. And what if it fails the check, then what? If I manually go to the Mozilla website (for example) and download the app, then package it up and put it in Jamf for deployment, I at least have a good grasp on how many machines got THAT package. However, there have been recent incidents where hackers got access to those servers and inserted their own hacked version into the official channel when the old versions would autoupdate directly from the vendor's servers.One way to mitigate that might be to build in CRC checks into your scripts, but then that adds extra overhead. Your scripted method of obtaining the updated apps talks directly to the vendor's servers should make everyone feel warm and fuzzy. Your points for scripted installs are valid. ![]() I don't think there is a perfect solution. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |