Slashdot Mirror
Microsoft To Support SSH In Windows and Contribute To OpenSSH
An anonymous reader writes: Microsoft has announced plans for native support for SSH in Windows. "A popular request the PowerShell team has received is to use Secure Shell protocol and Shell session (aka SSH) to interoperate between Windows and Linux – both Linux connecting to and managing Windows via SSH and, vice versa, Windows connecting to and managing Linux via SSH. Thus, the combination of PowerShell and SSH will deliver a robust and secure solution to automate and to remotely manage Linux and Windows systems." Based on the work from this new direction, they also plan to contribute back to the OpenSSH project as well.
it's only 2015 guys...
Even cooler than their work with the git project.
Now I'm scared... We may, once again, see Microsoft's approach of Embrace, Extend, and Extinguish in action...
In Soviet Washington the swamp drains you.
MS-SOP
You log onto a Windows C:> prompt.
It's about dam time!
No need for MS help when Cygwin exists. Furthermore, its super easy to setup.
now you can use Windows computers the way they were meant to be used, as dummy linux clients
I mean, they will take OpenSSH, compile-it for Windows, and make sure Power Shell is the default login shell. Then what? What piece of code could the Open SSH project want from Microsoft exactly?
Are M$ getting sensible in their old age?
John_Chalisque
Or Windows still won't be able to run Power Shell scripts by default?
Are they forgetting who runs OpenSSH? I'm picturing Redmond folk getting a new gastrointestinal egress bored, that would accommodate a Mac truck.
Microsoft's tactic of Embrace, Extend and Extinguish!
They will invariably add their own proprietary extensions which will make the open source users get left out from time to time. Thus bringing about a migration from OpenSSH to whatever closed source Microsoft controlled product is compatible. This is bad news all round.
But will it be certified as FIPS-compliant for use on Gover meant contracts?!?
You mean I don't need to install Cygwin anymore like I have been doing for the past 15 years to accomplish just that?
Next proposal: implement rsync natively...
Everything I write is lies, read between the lines.
* I remember joking about connecting to a 'doze server via SSH in 2005. Usually the response was a disgusted shiver.
* I guess Microsoft finally got sick of seeing PuTTY's hegemony in the terminal/SSH client market, and decided that this, *this* was a market they could finally dominate in this day and age?
* I shudder to think of how bastardized the command options are going to be, given the PowerShell's habit of using stuff like '-omgLookAtThisMassiveOptionNamingConvention', to the point where they have to alias a frickin' option...
Ah well, good on 'em. I'll stick with using Linux and OSX clients, thanks much.
Quo usque tandem abutere, Nimbus, patientia nostra?
In which case they will have to release the code that corresponds to binaries - would be useful for checking that there is not some little tweaks to help the NSA -- but if they have already put those into the system DLLs (eg for encryption) we would not really know. Maybe I am too cynical but I am very suspicious of what they did to skype.
Now all those programmers the NSA has embedded at Microsoft can be let loose to contribute to the SSH project.
Surely nothing good can come of this.
"If it ain't broke, it doesn't have enough features yet"
https://www.youtube.com/watch?...
-no sig today-
And now I see Dice is embedding videos in the main page.
Fuck you Dice, you are making Slashdot shittier and shittier.
When we stop coming, don't whine.
We've only been asking for non-assine remote powershell access for.. Well, since powershell was created.
There are methods for doing it now but hole-eee-fuck is it convoluted. Especially when you consider that there's an industry standard, secure, widely available remote console protocol/suite that's been around for decades.
Will this work out of the box? Because you basically have to go into the server you are accessing it and type some really weird shit on winrm to be able to even run scripts and god forsake you if you want to access the console remotely. Its so fucking annoying that I've met some people who just disable HTTPS and go straight for HTTP with basic authentication.
ssh and openshh: ssh is proprietary
solaris and opensolaris: solaris is proprietary
apache and no openapache: apache is open source
Everything I write is lies, read between the lines.
You know it's going to be just yet another way of hacking into a Windows box.
-The wise argue that there are few absolutes, the fool argues that there are no probabilities.
Losing nearly a billion dollars over an 8 year period, firing four-thousand permanent staff, and being dead last in search and browser rankings will do strange things to you. Steve Ballmer shoulders some of the blame for the nosedive with his nearly cult-like adherence to the redmond ethos of embrace-extend-extinguish in the face of a brand like linux that just can't be killed with it. But to think after 15 years as other slash dotters have commented that this will make any significant dent in the status quo is self-defeating at best.
SSH gives windows users the ability to do real work, and thats a controversial sentiment but in most large corporations admins that handle LAMP, percona, or hadoop do it from a windows machine by company policy. Microsoft doesn't understand that outside of email and office, the real juggernauts of industry are so far removed from redmonds product line it may as well be a different language entirely. conceding a pittance, this ssh, and promising to commit code to openssh do two things. One, they add continued relevance to windows in an office environment that otherwise is the next prime target to be extinguished as quickly as the home market for windows. Two, they provide code to openssh not because they have any particular valuable insight to add to the project which has handled itself just fine for 15 years, but because they need to ensure their openssh implementation actually works with other well-established and quite serviceable implementations. So don't expect any real innovation.
Good people go to bed earlier.
Regarding Windows Firewall:
The feature where you can supposedly define custom network groups for the scope. Can you finally create more than localsubnet? It would be nice to be able to define "My networks" as "x.x.x.0/24, y.y.0.0/16, 10.0.0.0/8" then set scope for multiple rules as "My networks".
that any server that it connects to has to be a member of AD ;)
Embrace....
The b*stards from the Linux Foundation never gave them a cent of the money they recieved to male critical infrastructure secure.
Do we want a major corp like microsoft involved in this?
"If any question why we died, Tell them because our fathers lied."
Hey guys with poor reading comprehension...
SSH = Secure Shell, not "Run Bash over crypto securely"
All this means is that it can drop unencrypted telnet and ftp, and allow SSH connections to do all the same things you could do from the windows command line.
Y'know like "runmaliciousprogram.exe"
At least this is a step up from requiring people to use terminal services or remove KVM just to deal with goddamn windows servers.
Will the support sftp access in explorer? I could simplify a lot of my webDAV/samba stuff that way...
MS is adding actually useful standard tools (well, standard outside of the MS isle of incompatibility) to windows! Good. That means we are at a stage where they cannot ignore what works anymore. As usual for MS decades late, but better late than never.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Indeed. I expect one of the things they'll be looking at doing is adding support for some of Windows' built-in authentication options. For example, recent versions of RDP use machine certificates, typically with a trust-on-first-use model similar to SSH. It would be nice if SSHing into a Windows box could re-use that machine cert, and SSHing from a Windows box could take advantage of the list of IP+cert pairs that you already trust. This would require some code changes to OpenSSH though, since it is of course currently utterly unaware of Windows' certificate stores.
Also, powershell isn't really used to displaying to anything except Windows consoles. Just for the hell of it, I tried running it in xterm (which, while antique, any *nix program would be OK with) by SSHing into a Windows box. It launched, but trying to run any commands - even exit - appeared to hang (though Ctrl+C worked to exit out of PS entirely). This may not be something that Microsoft needs the help of the OpenSSH devs to fix, but it's something that needs to be fixed, regardless. If people can SSH into Powershell, then Powershell needs to be able to display to whatever console they're SSHing from.
There's no place I could be, since I've found Serenity...
I've seen that before: Microsoft embraces some technology. Promises to contribute to it. Extends it in non-compatible ways. Hopes their version becomes the new world standard, and the original versions slowly dies.
A port was already achieved back in 2010. People wake up, including Microsoft - why are you waking up NOW?!
https://www.nomachine.com/node/2548
Mailing lists of OpenSSH
http://marc.info/?l=openssh-unix-dev&m=127323116722483&w=2
Wakey wakey Microsoft and everyone else
http://marc.info/?l=openssh-unix-dev&m=127323116722483&w=2
I've been wrapping commands for PuTTY and using PoshSSH. A native implementation would be sweet. I wonder how big a hassle it will be to convert my putty stuff for it.
Given that WinSCP has had an API you can drive from .NET and PowerShell for years already... what functionality are people thinking they actually need here? On the other hand if you're actually wanting an SSH server on Windows there's always Cygwin and CopSSH.
... they [Microsoft] also plan to contribute back to the OpenSSH project as well.
NO THANK YOU. Please keep your embrace-and-extend, security-is-a-joke grimy grippers out of the OpenSSH codebase.
Tiller's Rule: Never use a word in written form that you've only heard and never read. You will end up looking foolish.
When I see an also, and then an as well as well, well, then I'm unhappy too.
Native ssh is great. But what would make it even better is if windows would give up their c:\blah\blah file system structure and standardize with linux and osx by embracing /blah/blah. So annoying when working in a mixed OS environment. Lets see, did this app need the backslash escaped, c:/\ or will it handle c:\, does it even recognize c: or just / or just \, etc..