OpenSSH for Windows update • Hacker News Board

Re: OpenSSH for Windows update

#21

Post by phippsbrad » Mon, Oct 19, 2015, 8:55 PM UTC

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.

Re: OpenSSH for Windows update

#22

Post by togusa » Mon, Oct 19, 2015, 8:57 PM UTC

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.

Yep definitely the worst thing ever. Not just that though; everything. I've lost so much hair in the last few months over trying to get a CD environment up on windows.

Re: OpenSSH for Windows update

#23

Post by ThatGeoGuy » Mon, Oct 19, 2015, 8:58 PM UTC

kasabali wrote: 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.

Is this not what midipix.org intends to do? Granted, they're nowhere near close to being finished at this point in time, but it would be great to see the project pick up steam in this space.

Re: OpenSSH for Windows update

#24

Post by mhurron » Mon, Oct 19, 2015, 8:59 PM UTC

mavhc wrote: 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.

Re: OpenSSH for Windows update

#25

Post by kasabali » Mon, Oct 19, 2015, 9:00 PM UTC

togusa wrote: post #13

kasabali wrote: 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.

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.

Re: OpenSSH for Windows update

#26

Post by kasabali » Mon, Oct 19, 2015, 9:03 PM UTC

ThatGeoGuy wrote: post #23

kasabali wrote: 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.

Is this not what midipix.org intends to do? Granted, they're nowhere near close to being finished at this point in time, but it would be great to see the project pick up steam in this space.

Thanks for mentioning it. I check their website occasionally and hope that it'll be a reliable and sustainable alternative.

Re: OpenSSH for Windows update

#27

Post by DonnyV » Mon, Oct 19, 2015, 9:08 PM UTC

daguava wrote: post #5

nailer wrote: post #3

> Leverage Windows crypto api’s instead of OpenSSL/LibreSSL and run as Windows Service Was wondering about that. I'm surprised the OpenBSD team is accepting the commits - something so fundamental and Windows specific doesn't seem like their kind of thing - but great! PS. If you're coming from a Unix background and interested in learning posh: https://certsimple.com/rosetta-stone

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.

Re: OpenSSH for Windows update

#28

Post by polyomino » Mon, Oct 19, 2015, 9:08 PM UTC

togusa wrote: post #16

shmerl wrote: post #14

Earlier quoted context omitted.

So how would it hurt anybody exactly?

Shareholders.

developers will abandon win32 whether windows supports posix or not

Re: OpenSSH for Windows update

#29

Post by shmerl » Mon, Oct 19, 2015, 9:08 PM UTC

togusa wrote: post #16

shmerl wrote: post #14

Earlier quoted context omitted.

So how would it hurt anybody exactly?

Shareholders.

I doubt shareholders would be hurt by making things easier for developers. It's a retarded mentality that lock-in is good (while it hurts developers).

Re: OpenSSH for Windows update

#30

Post by drzaiusapelord » Mon, Oct 19, 2015, 9:08 PM UTC

phippsbrad wrote: post #21

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.