Live data from Hacker News

OpenSSH for Windows update

blogs.msdn.com

31–40 of 146 posts

Re: OpenSSH for Windows update

#31
post #13

Earlier quoted context omitted.

Because people would build for that instead of Win32.

That is a valid concern. On the other hand, win32 has a strong developer community with 20+ years of legacy as the primary API of Windows. Now only if Microsoft hadn't try to screw its own developers by trying to push a new framework every 5 years.

It does but as you say due to the emperor's new clothes every few years, the loyalty isn't there now. I know of no companies doing greenfield desktop dev that are using any of their tech. It's all Qt, CEF, python/wx and JavaFX. Even the financial companies we deal with who were pretty heavy with the WPF are canning it next cycle.

Incumbent MFC, Winforms and WPF stuff will live as long as VB6 did (and still does) though.

Edit as HN won't let me reply (submitting too fast). In Europe and JavaFX also has hardware acceleration as does CEF as it uses Chrome's rendering engine.

Re: OpenSSH for Windows update

#32
post #9

> Address POSIX compatibility concerns Best way to address POSIX compatibility concerns is implementing a proper POSIX layer in Windows (and not in a half-baked manner like the now deprecated SUA). I can't imagine how it would hurt anybody.

We have enough POSIX to go round, I think. No need for any more ;)

Re: OpenSSH for Windows update

#33

I have had really good luck with this open source, native windows, ssh server. http://www.kpym.com/2/kpym/index.htm I have no affiliation with the project, i just thought i'd mention that it is a nice alternative i found.

Why does this support telnet? Just seems crazy to me. Is it on by default? That would be a violation of any sane security policy pretty much anywhere. Seems like a serious edge case requirement and odd to bundle with SSH. This is like buying a new car but then having the dealer give you a free horse with your purchase.

Telnet has the unique advantage of having an implementation for the opposite part on any TCP/IP compatible system without external libraries, crypto etc. and that you can recreate both a server and a client in literally an hour with nothing but a C compiler and an ordinary libc.

Re: OpenSSH for Windows update

#35
post #27
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.

No.

Re: OpenSSH for Windows update

#36
post #24
post #4

I suggest making Update update, ie lower case, I was confused as to why Windows Update was getting ssh

I thought standard title rules were every word other than words like 'and' and 'is' were capitalized.

I don't believe there is a hard rule for titles that should take precedence over clarity.

Re: OpenSSH for Windows update

#37
post #7

I am waiting the moment when I can throw away WinRM and SSH to all the servers.

You have to create a god damn scheduled task to do Windows Updates over WinRM. And it takes ages for Powershell to realise the task is running, and polling the status of the job is a PITA.

Took me days to automate Windows 2012 with Packer. Ugh

Re: OpenSSH for Windows update

#39
I'm interested in how this is going to work in PowerShell with the way everything works now, if there happen to be any details about that (whether here, somewhere else, or a past link)?
Post reply on HN