[kwlug-disc] Windows to support SSH?

[B. S.]

Confused.

Cygwin.

Bash.

SSH.

Done. No stinking versions, no anything else ... it's ... just ... done. (And one can just get on with their day of using the hammer, the same hammer they use everywhere else, not having to figure out which hammer they're holding at that moment.) [For that matter, perl, php, <pick your favourite language>.]

I expect the significance of the Windows announcement will be more that accounts / groups / permissions will be tied into the windows back end. Which will no doubt be wrinkly and weird (to get used to).

Never mind windows telnet (with NTLM, i.e. secure) authentication is already present throughout.

Take things a bit further, since some like screen, etc., ... will (windows) ssh actually (by itself) buy you anything (that you don't already have)? If you have to load cygwin to get screen, you've already got ssh and so on, so does the windows announcement really matter? Add in VNC and ... is any of this really newsworthy?

[Glad for the post of the announcement, interesting and better to know than not, but not sure it much matters.]


----- Original Message -----
> From: Jonathan Poole <jpoole at digitaljedi.ca>
> To: KWLUG discussion <kwlug-disc at kwlug.org>
> Cc: 
> Sent: Wednesday, June 3, 2015 2:18 PM
> Subject: Re: [kwlug-disc] Windows to support SSH?
> 
> Of course, it would be nice if the Windows command interpreter wasn’t such an 
> awful embarrassment and could do things like string quote escaping without 
> losing its mind. I heard some of the political backstory to why cmd has been 
> left to languish for the past two decades and was not surprised (summary: old 
> and crusty NT dev, with matching territorialism and ego). Oh, and the answer to 
> “cmd is crappy” is not PowerShell, thanks. Who said that? We can go outside and 
> settle it, if you want.
> 
> Not really sure what the answer is. For instance, every time I write a bit of 
> bash I want to throw up a little. The only shell programming language I didn’t 
> actively hate was the MPW Shell, and that is decades dead now; MPW sure had some 
> flaws, but parts of it were really nice.
> 
> I think the push from chef/ansible/salt/puppet for ssh in terms of automation is 
> probably leaning on Microsoft quite a bit, chef has done some wonders with azure 
> as of late, but ssh is a big win.
> 
> As soon as I can change my firewall rules to only accept port tcp:22 instead of 
> tcp:3389/tcp:22 then I'll be happy.
> 
> 
> 
> -----Original message-----
>>  From:CrankyOldBugger
>>  Sent: Wednesday, June 3 2015, 2:09 pm
>>  To: KWLUG discussion
>>  Subject: Re: [kwlug-disc] Windows to support SSH?
>> 
>> 
>> 
>>  Thats my biggest beef with PowerShell right there:  its so version 
> specific.  Its a real PITA at work when we have NT4, W2K, W2K3, W2K8, and W2K12 
> servers to deal with.  The only thing I can rely on is DOS batch files.
>> 
>>  Having SSH go cross-platform and cross-versions would be great.
>> 
>>  On Wed, 3 Jun 2015 at 13:59 Paul Nijjar <paul_nijjar at yahoo.ca 
> <mailto:paul_nijjar at yahoo.ca>> wrote:
>> 
>>  On Wed, Jun 03, 2015 at 02:05:40PM +0000, CrankyOldBugger wrote:
>> 
>>  > http://thehackernews.com/2015/06/windows-secure-shell.html 
> <http://thehackernews.com/2015/06/windows-secure-shell.html>
>> 
>>  >
>> 
>>  > This would be great if it didnt involve PowerShell.
>> 
>>  I have no problem with it involving Powershell, because Powershell is
>> 
>>  pretty great. The designers learned a lot of lessons from other
>> 
>>  free-software scripting languages, and it shows.
>> 
>>  Whats sucky about Powershell is that it is tied to specific versions
>> 
>>  of Windows, so you cannot get the Win8 version of Powershell for
>> 
>>  Windows 7 machines (as far as I know).
>> 
>>  It would be so great to be able to SSH into a Windows machine. RDP
>> 
>>  kind of works, but SSH opens up so many possibilities for remote
>> 
>>  scripting and administration.