What To Do / Not to Do in PowerShell: Part 9  You probably know
that Windows PowerShell supports code-signing, a means of
protecting users and ourselves against
theunintentional execution of untrusted scripts. Heaven knows,
half of y'all have probably set your shell's ExecutionPolicy to
"Unrestricted," and are touching up your makeup even know for
your appearance on CNN: "Gosh durn it, that Microsoft stuff just
whacked my whole 'vironment, it did! We're a-switchin' to the
Google!"  Another choice would be the RemoteSigned execution
policy which, frankly, I don't care for. It basically only
requires a signature for scripts that (a) live on a remote
computer or (b) were downloaded through IE or Outlook. Not much
extra security for me, there.  My choice is AllSigned, which
requires all scripts to carry a signature. Yep, it's a bit less
convenient, but I like the security it offers me. It forces me
to stop, look at a script, and then sign it myself if it isn't
already signed.  But I ask: Why aren't more of you si