News for hackers. Stuff that matters.
Re:Introducing PackageManagement in Windows 10 by Aleman360 on Wednesday April 29, 2015 @12:24PM (#9459389)
PowerShell is disabled by default for security reasons. It's one command to enable it.
Re:Introducing PackageManagement in Windows 10 by useerup on Thursday April 30, 2015 @03:52AM (#9463793)
> PowerShell is disabled by default for security reasons.

Small correction: PowerShell script files are disabled by default for security reasons.

PowerShell is available with all Windows versions since Vista SP1.

On the latest Windows versions, remote command (part of Remote Management) is enabled by default. I.e. you can connect (given proper credentials) to a Server 2012R2 through PowerShell remoting and execute commands.

Indeed, the new "Server Nano" will not have any way to log in locally at all. There is no shell (as in operating system shell), and no local editor (like notepad). Only the remote command interface. PowerShell will be extended to allow remote file editing - i.e. use a local editor for a file residing on the remote computer (been missing that for the longest time now)

Re:Introducing PackageManagement in Windows 10 by WorldWideWayne on Wednesday April 29, 2015 @12:36PM (#9459522)
Yeah, one command - on every machine... Meanwhile on Linux, I don't need to do any special configuration to run scripts.
Re:Introducing PackageManagement in Windows 10 by theg2 on Wednesday April 29, 2015 @12:43PM (#9459578)
You do if those scripts can affect the system and need to run as root. Powershell is incredibly powerful (and dangerous) and some security isn't the worst thing.
Re:Introducing PackageManagement in Windows 10 by swasheck on Wednesday April 29, 2015 @01:07PM (#9459798)
the irony of this is that if ms were to leave powershell open to run any scripts from anywhere at any time, they'd be ridiculed for lax security policies.
Re:Introducing PackageManagement in Windows 10 by mmcru on Wednesday April 29, 2015 @04:52PM (#9461686)
why? .cmd and .bat can run any time, and can do just as much damage as powershell.
Re:Introducing PackageManagement in Windows 10 by astrodust on Wednesday April 29, 2015 @01:52PM (#9460220)
It's no more powerful and dangerous than bash in the right hands.
Re:Introducing PackageManagement in Windows 10 by dragonwriter on Wednesday April 29, 2015 @12:40PM (#9459556)
> Yeah, one command - on every machine...

I think Microsoft envisions centrally-managed environments, rather than those with lots of Windows machines that aren't centrally managed.

Re:Introducing PackageManagement in Windows 10 by dragontamer on Wednesday April 29, 2015 @12:44PM (#9459591)
> on every machine...

Or through one group policy pushed to every machine.

Re:Introducing PackageManagement in Windows 10 by Someone1234 on Wednesday April 29, 2015 @03:07PM (#9460883)
Plus, unlike what most people envision on here, Microsoft intends companies to push AllSigned or RemoteSigned, rather than Unrestricted.

So the company can push their CA and new PS policy in a single GPO, and then all internal PS scripts are signed using an internal CA generated code signing certificate.

This sounds complex but it is actually as simple as running Set-AuthenticodeSignature on each script using the code signing certificate.