2
edits
Talk:Software Update: Difference between revisions
Automatic Updates vs System Security
Spmirowski (talk | contribs) (Automatic Updates vs System Security) |
|||
| Line 87: | Line 87: | ||
Picture the large microsoft windows running company where employees are users, not even "power users", and don't have write permission to the installation directory. The quoted paragraph seems to specifically exclude the clients automatically upgrading. Now, I think the way other programs running under windows get around the necessary priviledge elevation, is by running a "service" as a user with rights to the installation directory, e.g. system, or administrator, which the client running as user can connect to. Without this, there doesn't seem to be a way of managing firefox without visiting each an every computer it is installed on. | Picture the large microsoft windows running company where employees are users, not even "power users", and don't have write permission to the installation directory. The quoted paragraph seems to specifically exclude the clients automatically upgrading. Now, I think the way other programs running under windows get around the necessary priviledge elevation, is by running a "service" as a user with rights to the installation directory, e.g. system, or administrator, which the client running as user can connect to. Without this, there doesn't seem to be a way of managing firefox without visiting each an every computer it is installed on. | ||
== Automatic Updates vs System Security == | |||
"Picture the large microsoft windows running company where employees are users, not even "power users", and don't have write permission to the installation directory. The quoted paragraph seems to specifically exclude the clients automatically upgrading. Now, I think the way other programs running under windows get around the necessary priviledge elevation, is by running a "service" as a user with rights to the installation directory, e.g. system, or administrator, which the client running as user can connect to. Without this, there doesn't seem to be a way of managing firefox without visiting each an every computer it is installed on." | |||
As an administrator of a multiple Domains and stand-alone networks over many campuses, it is a poor system to upgrade Firefox if it must be done an administrator on each machine. If it was a service or a program that called an admin account to do the upgrade, it would a be much less of a head ache. I don't like IE, however, automatic updates saves me so much time. Certainly, I don't want to give Users/Domain User RW access to programs to do updates. Less perm to the Users, less security issues. | |||
Most home computers bought, OEM etc, are improperly setup. Stores/OEMs set up the default account as an administrator (this is why so many people have spyware, malware issues). But for those home computers that are setup for limited user or just user accounts, the same problem will occur as well. And that's just Windows. | |||
What about GNU/Linux or OSX? Root owns my programs. Will Firefox have to be ran as Root or a super user just to update? | |||