Don??™t use after hours scripting for
any application, command, or utility that is unreliable or presents security risks.
9.
Remember that a command is an internal feature of the command processor or another
executable environment, such as the FTP application. A utility is an external, freestanding
application. Even though commands and utilities are both executable code, commands
depend on the resources of their enabling environment.
10.
Even though a utility exists, that doesn??™t mean you should use it. For example, Microsoft
disables the Messenger service by default in newer versions of Windows because crackers
can use it to gain access to your system. However, the Msg utility requires access to the
Messenger service. Unless you want to create a security hole in your system, refrain from
using the Msg utility except where the network has no outside access.
11.
Remember, this book documents a number of command and utility features that don??™t appear
as part of the command or utility help, the local Windows help, or even the Windows Resource
Kit. Some of these additions come from third-party Web sites (the sites appear in the book
whenever possible).
Pages:
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335