21–30 of 404 posts
Earlier quoted context omitted.
People have, and do have access to it. Windows Research kernel. Kernel leaks, etc. Generally the code quality is considered good.
I'm sure that the NSA agrees with you.
Oh wait, you were just trying to score cheap snark points, weren't you?
[1] - https://www.nsa.gov/ia/mitigation_guidance/security_configur...
I happily await the day when I no longer need to install PuTTY on all of my fresh Windows installs.
They really need to announce a conhost replacement. The "experiments" in Windows 10 are undeniably improvements for when we still use things like cmd, but Powershell needs a modern terminal window and there needs to be a native answer to Putty for both SSH and Powershell remoting. I'd say after SSH this should be a priority for the Powershell team. Conhost is holding them back. A lot.
> Given our changes in leadership and culture, we decided to give it another try and this time, because we are able to show the clear and compelling customer value, the company is very supportive. Is that code for Ballmer's regime vs Nadella's regime?
To give a concrete example of the changes (heard from a former Microsoft employee): Under Ballmer they were not allowed to touch anything open-source. Pretty soon after he left that was changed to a policy that a BSD/MIT open-source solution must be used if it is available unless there's a damned good reason.
Wonderful. I am a big supporter of Powershell, and while Powershell has supported remoting since almost day one, it will never enjoy quite as much support as SSH already receives (e.g. third party tools, firewall support, etc). It is also nice that they're looking into using something fairly "proven" secure, OpenSSH is exposed to the internet a lot (even if, yes, that is not best practice) so we can reasonably expect…
Please elaborate.
Earlier quoted context omitted.
They really need to announce a conhost replacement. The "experiments" in Windows 10 are undeniably improvements for when we still use things like cmd, but Powershell needs a modern terminal window and there needs to be a native answer to Putty for both SSH and Powershell remoting. I'd say after SSH this should be a priority for the Powershell team. Conhost is holding them back. A lot.
Isn't ISE pretty much what you are asking for?
I happily await the day when I no longer need to install PuTTY on all of my fresh Windows installs.
They really need to announce a conhost replacement. The "experiments" in Windows 10 are undeniably improvements for when we still use things like cmd, but Powershell needs a modern terminal window and there needs to be a native answer to Putty for both SSH and Powershell remoting. I'd say after SSH this should be a priority for the Powershell team. Conhost is holding them back. A lot.
Given that a lot of new development in the Windows world is focused on the console, I expect that we will see more enhancements in the future.