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

Install Win32 OpenSSH test release

github.com

Post reply on HN
Print view View original

21–30 of 47 posts

Re: Install Win32 OpenSSH test release

#21

Post by voltagex_ »

YCOmega wrote: post #12

Microsoft is going about the whole SSH thing in a very backwards way. If all they did was make or back an official POSIX environment, all of this comes for free. Insisting that PowerShell be the focal point for all these changes is just bizarre. Just install msys2.

PowerShell is the focal point for Windows on Azure, for Server Core and for Server Nano. So it makes perfect sense from that perspective. As a Windows and Linux user, this is absolutely fantastic.

msys2 still can't overcome some of the limitations of mintty so it kinda makes sense.

More choice in this case isn't a bad thing.

Re: Install Win32 OpenSSH test release

#22

Post by mikemaccana »

quanticle wrote: post #9
0x0 wrote: post #8

Interesting that the build instructions refer to Cygwin. It's a bit surprising, I'd have expected something more native. What does this bring to the table that regular Cygwin OpenSSHd couldn't do 10 years ago?

Powershell integration. Cygwin SSH drops you into a bash prompt running on the Windows box. Powershell is much more deeply integrated with Windows, and is more useful for actual system administration (e.g. configuring IIS, SQL Server, etc) than Cygwin's bash.

Asides from being an actual Windows app as you mentioned, it's also a current OpenSSH codebase.

Re: Install Win32 OpenSSH test release

#23

Post by zrm »

EvanAnderson wrote: post #19
zrm wrote: post #18

Feature request: Domain group policy setting for authorized keys. Make some ssh key(s) authorized to logon as some domain user(s) for every machine in the domain.

You could do this right now w/ w/ a "Startup Script" or using Group Policy Preferences. The authorization to logon is, presumably, tied to the "User Right" to logon interactively and shouldn't have anything to do w/ the SSH server (since it's just userland).

Authorized keys in the context of ssh means the ability to logon without password using public key authentication.

Now that I'm thinking about this, anybody know how they're doing public key authentication for domain accounts at all? If you don't use a password to logon, how are you supposed to get a Kerberos ticket to use domain network resources?

Re: Install Win32 OpenSSH test release

#24

Post by YCOmega »

mikemaccana wrote: post #20
YCOmega wrote: post #12

Microsoft is going about the whole SSH thing in a very backwards way. If all they did was make or back an official POSIX environment, all of this comes for free. Insisting that PowerShell be the focal point for all these changes is just bizarre. Just install msys2.

A half-bad Unix on top of Windows, with its own duplicate way of handling services, storage, users, permissions and everything else, is a pretty poor setup. Powershell (particularly the way it separates data from presentation) is one of the best shells on any OS. Being able to access it from Linux is a good thing.

This "separate data from presentation" sounds like TCO-speak. Way too frequently referenced to be a genuine inspiration.

It's only "half bad" (if that even) because while the whole world moved on from Windows to Unix (OSX, Linux), Microsoft dug their heels in. Think of it as paying down long overdue technical debt.

Re: Install Win32 OpenSSH test release

#25

Post by RayDonnelly »

DiabloD3 wrote: post #16
YCOmega wrote: post #12

Microsoft is going about the whole SSH thing in a very backwards way. If all they did was make or back an official POSIX environment, all of this comes for free. Insisting that PowerShell be the focal point for all these changes is just bizarre. Just install msys2.

I don't know why YCOmega is getting downvoted, msys2 is actually an extremely nice environment, now that Interix has been dead for quite some time. I wish msys2 would figure out how to port Cygwin's sshd, or figure out how to use Microsoft's new one to give me a msys2'ed zsh prompt instead of Powershell.

As far as I can tell (initial glance only), building this port requires Visual Studio which is a shame. It'd require a bit of effort to port. I wish MS had gone down the CMake route again.

As for Cygwin's sshd, we don't want to step their toes any more than we already have.

Re: Install Win32 OpenSSH test release

#26

Post by mikemaccana »

YCOmega wrote: post #24
mikemaccana wrote: post #20

Earlier quoted context omitted.

A half-bad Unix on top of Windows, with its own duplicate way of handling services, storage, users, permissions and everything else, is a pretty poor setup. Powershell (particularly the way it separates data from presentation) is one of the best shells on any OS. Being able to access it from Linux is a good thing.

This "separate data from presentation" sounds like TCO-speak. Way too frequently referenced to be a genuine inspiration. It's only "half bad" (if that even) because while the whole world moved on from Windows to Unix (OSX, Linux), Microsoft dug their heels in. Think of it as paying down long overdue technical debt.

> This "separate data from presentation" sounds like TCO-speak. Way too frequently referenced to be a genuine inspiration.

Huh? It's a very specific thing. When you run stuff on Powershell, you pipe it to 'select' or 'where' and pick fields, rather than running grep / sed / awk and inventing regexs to scrape stuff.

    ps | where {$_.StartTime -ge $1HourAgo}
Before accusing me of 'TCO speak' and being 'ungenuine' - for mentioning something that's a well known engineering concept, particularly in the Unix world (ever used TeX?), you could have done <1 minute of research.

Re: Install Win32 OpenSSH test release

#27

Post by dijit »

zrm wrote: post #23
EvanAnderson wrote: post #19

Earlier quoted context omitted.

You could do this right now w/ w/ a "Startup Script" or using Group Policy Preferences. The authorization to logon is, presumably, tied to the "User Right" to logon interactively and shouldn't have anything to do w/ the SSH server (since it's just userland).

Authorized keys in the context of ssh means the ability to logon without password using public key authentication. Now that I'm thinking about this, anybody know how they're doing public key authentication for domain accounts at all? If you don't use a password to logon, how are you supposed to get a Kerberos ticket to use domain network resources?

On Linux you can still execute 'kinit' to power up and get a ticket. (Via password).

I'm sure there will be something similar. Unless authentication in the first place cannot be decoupled from ssh login, then your key would have to be able to grant you a Kerberos ticket.

Re: Install Win32 OpenSSH test release

#29

Post by detaro »

finid wrote: post #28

You can already install OpenSSH for Windows without bothering with PowerShell. See http://linuxbsdos.com/2015/07/30/how-to-install-openssh-on-w...

Can you run PowerShell through this?

Also, you probably want PowerShell if you manage a windows system remotely. (Ok, you specifically maybe not, but many users do)

Re: Install Win32 OpenSSH test release

#30

Post by [deleted] »

mikemaccana wrote: post #26
YCOmega wrote: post #24

Earlier quoted context omitted.

This "separate data from presentation" sounds like TCO-speak. Way too frequently referenced to be a genuine inspiration. It's only "half bad" (if that even) because while the whole world moved on from Windows to Unix (OSX, Linux), Microsoft dug their heels in. Think of it as paying down long overdue technical debt.

> This "separate data from presentation" sounds like TCO-speak. Way too frequently referenced to be a genuine inspiration. Huh? It's a very specific thing. When you run stuff on Powershell, you pipe it to 'select' or 'where' and pick fields, rather than running grep / sed / awk and inventing regexs to scrape stuff. ps | where {$_.StartTime -ge $1HourAgo} Before accusing me of 'TCO speak' and being 'ungenuine' - for m…

[deleted]
Post reply on HN