rudis dot net

PowerShell was a huge improvement over CMD.EXE and the features in 2.0 seem to provide even more functionality. Not enough hours in the day to look at all of these shiny new toys...

Windows PowerShell : The Community Technology Preview (CTP) of Windows PowerShell 2.0: "This CTP release helps developers to more easily layer their runtime or GUI on top of PowerShell, leveraging its cmdlets and remoting infrastructure.  It includes APIs to create and use a pool of Runspaces (engines) to run cmdlets.  This release also presents very early looks at Restricted Runspaces (the ability to declare a script, cmdlet or variable public or private) and the Graphical PowerShell (a script editor and a Unicode-enabled console).  These are just a few of the new features I think are interesting in Windows PowerShell 2.0 CTP.  Additionally this CTP includes some simple updates... like new parameters to select-string (Context, AllMatches, NotMatch and Encoding) and new operators like –split and -join!"

Phil and I have been busy again with two articles coming in FedTech Magazine (yes, writing to help the security of Big Brother). One is up now and deals with security of "G2B" (a.k.a. B2B) networks. We'll have one in the print 'zine in November which I'll "announce" once it's out.

Here's the teaser lead:

To borrow and twist a phrase from John Donne: “No LAN is an island,” especially in the 21st century. Unless you’re dealing with heavily protected systems and networks, you either already have existing external, third-party — government-to-business (G2B) — connections or will in the not-too-distant future. Then there are the virtual workers to contend with who require access to information on your network no matter where they are physically located on (or off) the planet.

In this reality, it’s crucial to know how to apply policies, processes and technology to safeguard your networks.