PowerShell Team Blog

I just returned from DerbyCon. An amazing security conference that covers both attack and defense. All talks are on youtube. Here is a good summary of the powershell talks. Really good stuff. https://blogs.msdn.microsoft.com/powershell/2016/09/27/powershell-secu…

From [1], cited and linked to in TFA: > To do that, we simply start the ssh-agent service (as Administrator) and use ssh-add to store our private key. Did Microsoft do some major surgery on the ssh-agent program or am I missing something else? If the agent is started as Administrator, why can I connect to it with my user privileges? And if I do, can other users on the same system do so, too, accessing the same set of keys? [1] https://blogs.msdn.microsoft.com/powershell/2017/12/15/using-the-opens…

Yeah, probably never happen. You'd never see J. Snover the 'father of PowerShell' at ChefConf last year talking about PowerShell Desired State Configuration (DSC) and its support for Chef (https://www.youtube.com/watch?v=Gh9zfm5gVEg) or two years ago the PowerShell team announcing a DSC Cookbook for Chef (https://blogs.msdn.microsoft.com/powershell/2014/07/29/chef-with-power… or last year announcing Puppet's announcement of support for PowerShell DSC ( https://blogs.msdn.microsoft.com/powershell/2015/10/06/desired-state-c… ) You know that the entire point of PowerShell is to make Windows functionality available from the command line, for centralised management and configuration, for automated provisioning on Azure, right?

> I don't think Windows users appreciate the importance of a good command line accessible over SSH for managing headless systems. You should check out this link - production quality OpenSSH for Windows planned for H1 2016. https://blogs.msdn.microsoft.com/powershell/2015/10/19/openssh-for-win…

> "One strong advantage of the current system is that the input matches the interface. Everything is text, so it all can be typed with the keyboard. But if this shell "displays structured results as real fing structures (YAML, JSON, ...)", that may not be true. If the shell spits out a table, is it a CSV table? A YAML / JSON nested array? How is the user supposed to edit it? The interface isn't clear, and any layers at all are going to take some thought to be able to compose naturally with other tools. (The author addresses part of this with "All operations made via a UI, including mouse operations in GUI must have and display textual representation, allowing to copy / paste / save to a file / send to friend.")" In PowerShell, all data is stored as .NET objects. Using this object-oriented approach enables the sort of flexibility I believe you're looking for. Perhaps something similar could be developed for Linux. There has been some activity in this area: https://github.com/Pash-Project/Pash https://blogs.msdn.microsoft.com/powershell/2015/05/05/powershell-dsc-… http://www.forbes.com/sites/justinwarren/2016/03/08/is-microsoft-about…