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

71–80 of 146 posts

Re: OpenSSH for Windows update

#71

Post by daveloyall »

nailer wrote: post #65
daveloyall wrote: post #47

Earlier quoted context omitted.

> PS. If you're coming from a Unix background and interested in learning posh: https://certsimple.com/rosetta-stone I stopped reading this when I got to this part: whois 'domain [domain name]' --> $web = New-WebServiceProxy 'http://www.webservicex.net/whois.asmx?WSDL' $web.GetWhoIs('[domain name]') It's cute that there is some kind of VBScript for calling web services, but this line tells me that this document must h…

The main aim is to be useful . Someone who wants to lookup Whois is better served by giving them something that will achieve that task. If you have other suggestions though, send a pull request. The project has already gotten a bunch from the SmartOS and FreeBSD communities.

If I could send a pull request to Microsoft for inclusion of a legit whois binary on their OS--nope, you're right, I'm just full of spite on this subject. :)

Re: OpenSSH for Windows update

#72

Post by daveloyall »

joosters wrote: post #70
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

You should be able to do that just fine. 'dir d:' runs on the windows box and 'less' on the unix box.

Excellent. That's very useful!

Re: OpenSSH for Windows update

#73

Post by nailer »

voltagex_ wrote: post #61
daveloyall wrote: post #47

Earlier quoted context omitted.

> PS. If you're coming from a Unix background and interested in learning posh: https://certsimple.com/rosetta-stone I stopped reading this when I got to this part: whois 'domain [domain name]' --> $web = New-WebServiceProxy 'http://www.webservicex.net/whois.asmx?WSDL' $web.GetWhoIs('[domain name]') It's cute that there is some kind of VBScript for calling web services, but this line tells me that this document must h…

Or hell, use something like https://github.com/bone187/PowerShell-Whois/blob/master/whoi... . I like PowerShell but sometimes the community makes me wonder.

That's certainly a lot cleaner than using the WSDL implementation. I've bumped the release on npm and used this instead - thank you.

If anyone else on HN wants to add anything, the source is just markdown, so you can hack away (gulp does the HTML building and JS does the interactivity): https://github.com/certsimple/rosetta-stone/blob/master/rose...

Re: OpenSSH for Windows update

#74

Post by teacup50 »

antics wrote: post #56
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.

SUA was not half-baked, this is a very, very hard problem. There is a very serious difference in the way POSIX and Windows model a lot of really important OS primitives, from asynchronicity model in signals, to the semantics of syscalls like `fork`. Every process using these primitives on POSIX has specific behavior defined under those primitives, and if you don't choose _exactly_ the right behavior on the POSIX subs…

Microsoft does control the kernel, and given that, none of this stuff is particularly complicated.

As for choosing "_exactly_ the right behavior" ... the whole point of POSIX is to clearly define the exact right behavior!

Re: OpenSSH for Windows update

#76

Post by DiabloD3 »

switch007 wrote: post #43
togusa wrote: post #22

Earlier quoted context omitted.

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.

This. Everything about Windows and automation just feels like Bill & co really hates you personally, hates your company, and even the air you breath

... while also hating malaria.

Re: OpenSSH for Windows update

#77

Post by DiabloD3 »

This is very goddamned awesome. All I hope is I can set the default user shell for my account. I already use msys2's zsh for my shell (because I use zsh everywhere, on all OS), and being able to ssh into my Windows machine 'normally' (for me, anyways) would be extremely useful.

Re: OpenSSH for Windows update

#78

Post by ThatGeoGuy »

modeless wrote: post #52
ThatGeoGuy wrote: post #23

Earlier quoted context omitted.

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.

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 early in its infancy to start worrying about what license they might have.

Re: OpenSSH for Windows update

#79

Post by antod »

togusa wrote: post #8
gionn wrote: post #7

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

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.

I can't help but nod knowingly :)

I was so keen for WinRM support to land in Packer so I could avoid installing cygwin.

It was out of the frying pan and into the fire.

Native Windows SSH should _hopefully_ solve all this hassle.

Re: OpenSSH for Windows update

#80

Post by drewbug »

nailer wrote: post #42
thristian wrote: post #17

Earlier quoted context omitted.

A crypto system is a big and complex thing, subtle and quick to anger, and I can't blame Microsoft for wanting to concentrate on the one they're already supporting, instead of having to support two. On the other hand, for the exact same reason, I expect OpenSSH probably isn't interested in supporting anything besides LibreSSL and maybe OpenSSL, at least while they're so closely related.

So you think it'll remain a fork, rather than a platform for OpenSSH? If they implemented a good openssl to cryptoAPI shim it could be usable by other projects linked against OpenSSL.

Agreed, this would be awesome.
Post reply on HN