tag:blogger.com,1999:blog-11573761.post438736892551928352..comments2023-09-23T07:38:46.925-07:00Comments on Chris Quirke's Blog: Design vs. Code ErrorsChris Quirkehttp://www.blogger.com/profile/05538828571660803875noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11573761.post-55551761840807820222007-12-11T06:54:00.000-08:002007-12-11T06:54:00.000-08:00There are a number of expansions on "never turn yo...There are a number of expansions on "never turn your back on an installer": Stay offline, write-protect all installation disks, don't turn off av (tho oft instructed to), and don't consider the job done until you've done a first-run and gone through all the settings.<BR/><BR/>That's because the relationship between sware vendor and user is either triangular (vendor makes money from some 3rd-party, thus serves their interests first) or bilaterally hostile (you want to use the sware, they want you to pay for it).<BR/><BR/>So, aside from network exposure of exploit surfaces, it's best to stay offline during installs - and that's one objection I have to IE7.<BR/><BR/>The issue gets another dimension when you use a baseline patch-level code base (e.g. boot an installation or mOS disk); should that be allowed to "connect" to anything, e.g. to run online scanners, etc.?Chris Quirkehttps://www.blogger.com/profile/05538828571660803875noreply@blogger.comtag:blogger.com,1999:blog-11573761.post-66062866698480055512007-12-10T11:29:00.000-08:002007-12-10T11:29:00.000-08:00Bravo, Chris. Another favorite on that list of no-...Bravo, Chris. Another favorite on that list of no-nos is enabling the NIC before Windows XP installation is completed. That, coupled with File Printer Sharing enabled by default, and of course each of the appropriate pinholes is great wormbait during those installations! ^_^netjustinhttps://www.blogger.com/profile/08255962379052142169noreply@blogger.com