Live data from Hacker News

Looking Forward: Support for Secure Shell

blogs.msdn.com

71–80 of 404 posts

Re: Looking Forward: Support for Secure Shell

#71
post #36

Earlier quoted context omitted.

They might actually create a usable consumer OS given enough time to fix the garbage in Linux.

I think you're confusing linux (the kernel) with linux distributions (mostly lousy windows managers that run on linux). Let's not get into an OS war between us here, but looking at the changes over the last 15 years, it's clear that MS is warming up to Linux. This is something that was absolutely unthinkable during the Gates and Ballmer eras. The linux community must be doing something right when developer demand and…

Linux, the kernel, is also pretty bad, though.

Re: Looking Forward: Support for Secure Shell

#73

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…

> In general people really are starting to run out of reasons to "hate" Microsoft. It will be interesting to see what they come up with in the future... I agree with you overall, MS has made GREAT strides in the last year towards moving my needle from "Wouldn't touch if my life depended on it" to "Huh, that's actually pretty interesting". The old MS still shows through with things like how they are handling Win 10 (B…

> how they are handling Win 10 (Both in versions and cost)

I'm a bit confused by this. It's free for any genuine Windows 7 or 8 user, and $99 to $199 for anyone else. There are two SKUs (Home and Pro), rather than the multitude with XP or Vista. How is this not a reasonable approach? Especially since Windows 10 is supposed to be the last Windows release of this kind.

Re: Looking Forward: Support for Secure Shell

#74
post #60

For all Balmer's thing of dancing on a stage and chanting "developers", there was no point under Gates or he at which Microsoft felt like a pro-developer company. That has completely changed in the last eighteen months. Each time I think "wouldn't it be cool if" I'm finding a few weeks later that someone at Microsoft is well ahead of me. How much easier it will be to ship my sucky roguelikes to Windows users in this…

Wishlist:

mobaxterm - http://mobaxterm.mobatek.net/

Re: Looking Forward: Support for Secure Shell

#75

Hallelujah... new package manager, modular install, and now ssh? What's left? Perhaps a real terminal? To bad this won't make it into Win 10, unless I misunderstood something. Looks like my days of sneering at Windows as a toy are numbered... end of an era, and it makes me a bit sad, sniff .

Well, Win10 is the 'last Windows' according to MS, so this will probably arrive as an update later.

Re: Looking Forward: Support for Secure Shell

#76

Hallelujah... new package manager, modular install, and now ssh? What's left? Perhaps a real terminal? To bad this won't make it into Win 10, unless I misunderstood something. Looks like my days of sneering at Windows as a toy are numbered... end of an era, and it makes me a bit sad, sniff .

Command line (cmd.exe or something) in Windows 10 is actually decent compared to Win8.1 and earlier (ugh).

Resizing and mouse select & copy works now like terminals in OS X and Linux. It can now be mouse drag-resized horizontally and vertically. Mouse text selection and copy works as it should, it now handles multiple (long) lines correctly and smoothly.

Re: Looking Forward: Support for Secure Shell

#77
post #57
post #40

Earlier quoted context omitted.

the code for the VPN is better because...?

It's not necessarily better. But now you have two layers of security (VPN + SSH), rather than just one. And as others have mentioned, either way it's still good practice to disable password auth, so that you can only connect to SSH using a public/private keypair.

Even better don't use default ports. Or have a second ssh that doesn't except any IP address at port 22 and than have your non-standard port with keys and limited user names and if possible a white list of your IP addresses.

Re: Looking Forward: Support for Secure Shell

#78

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…

SYSLOG! For the love of god, please support syslog! I work as a consultant supporting a SIEM, and the amount of hoops we need to jump through to get logs from Windows servers is crazy compared to changing one line in a syslog.conf file. I actually dread when a client says "we're an all Windows environment" because wow initial setup just got that much harder.

And if we want to install a syslog forwarder on their domain controllers... no one ever trusts software installed on their domain controllers. Everyone trusts a single line in syslog.conf.

Re: Looking Forward: Support for Secure Shell

#79
I've been doing something similar using a virtual machine running Windows 7 and a whole host of really stupid VPN solutions to connect to customer networks. I ran sshd via Cygwin, which logged me into /bin/sh, from which I could actually start cmd.exe. Presumably, I could also have started PowerShell had I tried it.

It's nice to see that they are offering an official way to do this.

Re: Looking Forward: Support for Secure Shell

#80
post #73

Earlier quoted context omitted.

> In general people really are starting to run out of reasons to "hate" Microsoft. It will be interesting to see what they come up with in the future... I agree with you overall, MS has made GREAT strides in the last year towards moving my needle from "Wouldn't touch if my life depended on it" to "Huh, that's actually pretty interesting". The old MS still shows through with things like how they are handling Win 10 (B…

> how they are handling Win 10 (Both in versions and cost) I'm a bit confused by this. It's free for any genuine Windows 7 or 8 user, and $99 to $199 for anyone else. There are two SKUs (Home and Pro), rather than the multitude with XP or Vista. How is this not a reasonable approach? Especially since Windows 10 is supposed to be the last Windows release of this kind.

I believe they also have Windows 10 Enterprise, Windows 10 education and if we include the phone OS: Windows 10 mobile and Windows 10 mobile enterprise.
Post reply on HN