Re: FSO and the Scripting Host

From: Tim Baur (trbo20_at_disregard_yahoo.com)
Date: 10/07/04

  • Next message: Bryan Dickerson: "Re: Validating email addresses" 
    Date: Thu, 07 Oct 2004 13:11:58 -0700

    I guess I was under the impression that the case was:

    "Some day a sysadmin can flip a switch that will kill your software."

    Not:

    "A sysadmin might remove a standard Microsoft component that you may
    include with your setup."

    It's entirely possible someone might remove anything they deem a risk.
    It's also possible that a commercial-off-the-shelf piece of software will
    put it back on. That's not the same as changing system level security
    settings.

    > I know _of_ someone who got *fired* for installing an application which
    > brought the scrrun library along with it, onto a "secure" machine owned
    > by that person's employer's client (a military arm of the government)

    That sucks for your friend, really, but what was he/she doing installing an
    application on a highly classified system without researching the
    application's security risk? Generally, systems with that much security
    adhere to a stringent change control review process.

  • Next message: Bryan Dickerson: "Re: Validating email addresses"