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

141–146 of 146 posts

Re: OpenSSH for Windows update

#141

Post by 0xFFC »

rodgerd wrote: post #111
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?

Microsoft are pushing the command line to the point that: a) Many operations in newer bits of Windows have simple-mode available in the GUI, but more sophisticated options must be scripted. StorageSpaces has a few examples of this, where some of the options around tiered storage, SSD caching, and the layout of pools can only be accessed via posh. b) Microsoft are pushing completely headless versions of Windows Server…

About headless version , it is so great to hear that , although I am not using windows , but hearing that is good news overall , it seems with new CEO Microsoft back on truck . I would not remember with ballmer they released windows server with Metro UI . WTF !

Re: OpenSSH for Windows update

#142

Post by schoen »

ionised wrote: post #130
DonnyV wrote: post #27

Earlier quoted context omitted.

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.

They collaborated with the NSA to develop an exploit in the SSL implementation used in Outlook.com. From the Snowden documents; July 31, 2012 Microsoft (MS) began encrypting web-based chat with the introduction of the new outlook.com service. This new Secure Socket Layer (SSL) encryption effectively cut off collection of the new service for FAA 702 and likely 12333 (to some degree) for the Intelligence Community (IC)…

It's not clear this should be called an "exploit". It sounds like Microsoft in its capacity as a cryptographic endpoint turning over either plaintext or session keys (or in the severely worst case, long-term private keys). It doesn't make much sense to me to refer to that as an "exploit".

Re: OpenSSH for Windows update

#143

Post by e12e »

kohenkatz wrote: post #138
e12e wrote: post #116

The more things change..., from: https://github.com/PowerShell/Win32-OpenSSH/wiki/Deploy-Win3... "If you need key-based authentication: Install key-auth package run setup-ssh-lsa.cmd reboot " Reboot? And this gem: "SSH daemon needs to run as System to support key-based authentication". Which means, either use weak authentication, or run the daemon as system. I don't even understand why, it's not like the public keys…

Have you checked what user OpenSSH usually runs as on a linux machine in order to allow key-based authentication? I'll give you a hint: it's root. That's no different than running as SYSTEM on Windows.

As a sibling comment mentioned, it makes perfect sense that the ability to create a user session requires a certain privilege. What struck me as odd, was that it only needed this on Windows when using key-based authentication - not when allowing password-based login.

AFAIK ssh needs access to /etc/shadow on Linux, if you want to use system passwords. But also, AFAIK, nothing stops you from running ssh in a chroot, without any such access (well, access to a /etc/shadow under the chroot probably).

Re: OpenSSH for Windows update

#144

Post by daveloyall »

ryanlol wrote: post #134
daveloyall wrote: post #71

Earlier quoted context omitted.

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. :)

Actually, pretty sure most linux distributions don't ship with the whois binary. (This is entirely based on the fact that I find myself installing it far too often)

That's a feature. My initial installations don't include much. Tools are installed the first time I need to use them.

Re: OpenSSH for Windows update

#145

Post by teacup50 »

dragonwriter wrote: post #125
teacup50 wrote: post #74

Earlier quoted context omitted.

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!

Sure, its "easy" if Microsoft wants to redefine Windows in POSIX terms; iits not easy to keep Windows functioning as Windows and provide a POSIX compatibility layer, since Windows isn't designed around POSIX expectations.

Do you actually have specifics, here? I'm happy to discuss things like how to model fork() in-kernel.
Post reply on HN