Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenSSH for Windows update

blogs.msdn.com

Post reply on HN
Print view View original

101–110 of 146 posts

Re: OpenSSH for Windows update

#101

Post by est »

geofft wrote: post #96
est wrote: post #90

Earlier quoted context omitted.

you could run ANSI.sys in modern cmd.exe, sadly there's no ANSI.sys in Win7 anymore. https://groups.google.com/forum/#!topic/alt.msdos.batch.nt/Y...

Cool. Looks like that is essentially listing DEVICE=ANSI.SYS in config.nt? Google results imply some things about 16-bit emulation here -- was that post about running actual DOS ANSI.SYS in a VDM running actual DOS COMMAND.COM, within a native Windows terminal?

IIRC, the command.com only bootstrap the ANSI coloring, after that you can run anything in cmd.exe

Re: OpenSSH for Windows update

#102

Post by j_s »

I'm a fan of Bitvise SSH for a Windows SSH server; it's been enough to replace Terminal Services when each employee has their own work machine to remote desktop into.

It's nice that Microsoft recognizes the need for this functionality; I wonder how they will approach the potential per-client licensing issues they like to bring up with their server OS's.

https://www.bitvise.com/ssh-server

Re: OpenSSH for Windows update

#103

Post by Sanddancer »

martin1975 wrote: post #99

Never was much of a windows fan, so a (slightly ignorant) question for someone who is a Win admin - can most administrative things nowadays be done via the command line on Windows (like we've been able to do in *nix land) or is there a gap between what can be done via the GUI vs the command line?

Yep. Recent windows servers even default to boot straight to console these days, with none of the GUI services running. MS has realized that centralized deployment and maintenance is really useful and is acting accordingly, hence things like openssh for windows.

Re: OpenSSH for Windows update

#104

Post by nitrogen »

ThatGeoGuy wrote: post #78
modeless wrote: post #52

Earlier quoted context omitted.

midipix looks awesome, but seems to be GPL (not LGPL). Does that mean anything using it must be GPL too? I think that would be unacceptable for such a low layer of the stack.

I don't know why you're being downvoted, but this is a legitimate concern for some businesses (well, legitimate may be too strong, but it is a concern a lot of legal departments will have). After discussing this issue on #midipix on freenode, they had mentioned they will explore dual-licensing or some variant of such once the software is more stable and can be reliably deployed. In any case, the project is far too ea…

The longer a project proceeds, the harder it is to get developers' permission to change licenses.

Re: OpenSSH for Windows update

#105

Post by jen20 »

MichaelGG wrote: post #18
togusa wrote: post #8

Earlier quoted context omitted.

Hell yes. Watching packer shit a brick 5 times a day trying to upload virtualbox guest additions via WinRM makes me want this yesterday. Also I had to up the memory ceiling on WinRM to 800Mb (WTF!) to even get it to complete.

It really is surprisingly bad, isn't it? I recently was involved in a continuous deployment system targeting Windows. We simply couldn't get WinRM to reliably upload fast and ended up installing SSH everywhere.

Having worked on that code (in Packer) - the WinRM protocol is completely unsuitable for use as an SCP replacement. It's amazing it works at all even for small files! The actual "winrmcp" implementation is here https://github.com/packer-community/winrmcp if you're interested in the inner workings.

Re: OpenSSH for Windows update

#106

Post by TTPrograms »

detaro wrote: post #100
martin1975 wrote: post #99

Never was much of a windows fan, so a (slightly ignorant) question for someone who is a Win admin - can most administrative things nowadays be done via the command line on Windows (like we've been able to do in *nix land) or is there a gap between what can be done via the GUI vs the command line?

(From what I've heard from people using them) On the current server versions, PowerShell should allow to do all that the GUI can do. There is a GUI-less version and I think the GUI actually uses PowerShell underneath, so you can look up in a log how the commands look like for something you only knew how to do graphically before.

That is so cool. I have to look into this...

Re: OpenSSH for Windows update

#107

Post by tammer »

martin1975 wrote: post #99

Never was much of a windows fan, so a (slightly ignorant) question for someone who is a Win admin - can most administrative things nowadays be done via the command line on Windows (like we've been able to do in *nix land) or is there a gap between what can be done via the GUI vs the command line?

From a sysadmin in the field - it's complicated.

New Server features are primarily controllable via PowerShell and now only secondarily expose a bit of control via GUI. So, indeed PowerShell has taken precedence. However, it would be wrong to say that Windows administration is exactly like managing Unix systems. On the contrary, the more one works with it the more one realizes PowerShell is the anti-Bash.

Lacking in the aeons of interface legacy built into standard Unices, you won't find standbys like 'grep' readily available or even easily implemented. Rather, PowerShell is built from the ground up for scripting. While the addition of SSH will certainly be helpful for quickly checking statuses, (and possibly more in the future should readline usability of PowerShell improve) right now most PowerShell interactions happen via scripting from a local workstation or web or application inputs rather than directly via the interactive shell.

Re: OpenSSH for Windows update

#108

Post by voltagex_ »

roller wrote: post #98
daveloyall wrote: post #44

Earlier quoted context omitted.

I don't know anything about PowerShell, but I have a similar question, I think: how is this going to work? Will I be able to do something like this command line (from my *nix machine)? ssh user@windows.machine.local dir d: | less

This is a key thing I'm curious about. How is drive mapping handled? If I "net use d: \\host\share" from one session, it won't nessarily translate and mount D: to all sessions (or will it)?

I can't check right now, but if you have two local users, Delta and Gamma, and Gamma mounts D:\, does Delta see it or is it specific to Gamma's session?

Re: OpenSSH for Windows update

#110

Post by matsur »

DonnyV wrote: post #27
daguava wrote: post #5

Earlier quoted context omitted.

Was just coming here to voice my concerns over this choice as well, wondering what their reasoning is for changing crypto systems.

I really don't like that there replacing an open source crypto with a closed source one. Putting on my tin foil hat but didn't Microsoft hand over a back door to the NSA already.

The two cryptographers who originally publicly identified the backdoor (that Snowden eventually confirmed) work for Microsoft. So, the opposite of what you're insinuating.

http://rump2007.cr.yp.to/15-shumow.pdf

Always possible MS is not to be trusted, but there's nothing on the record to support that.

Post reply on HN