Microsoft Announces Support for SSH

Contributed by
tbert
on 2015-06-03
from the third-time's-the-charm dept.

Windows admins rejoice! Microsoft's PowerShell Team
announced
future support for SSH, specifically
OpenSSH:

[T]he PowerShell team realized the best option will be for our team to adopt an industry proven solution while providing tight integration with Windows; a solution that Microsoft will deliver in Windows while working closely with subject matter experts across the planet to build it. Based on these goals, Iím pleased to announce that the PowerShell team will support and contribute to the OpenSSH community - Very excited to work with the OpenSSH community to deliver the PowerShell and Windows SSH solution!

A follow up question the reader might have is When and How will the SSH support be available? The team is in the early planning phase, and thereíre not exact days yet. However the PowerShell team will provide details in the near future on availability dates.

Emphasis in the original. Wider adoption of secure technologies can only benefit the community. Hopefully that future is actually near, both for deployment and 'support and contribution'.

(Comments are closed)

By
Anonymous Coward ()
on 2015-06-03 20:59

there goes the neighbourhood...

By
Chas () chas@syro.org
on 2015-06-04 16:50

I really hope that they are going to use the strongest ciphers, and disable the older, unsafe components.

https://stribika.github.io/2015/01/04/secure-secure-shell.html

I'd prefer them to force compatibility issues in the name of strengthening security.

By
Blake ()
on 2015-06-09 23:55
2112.net

> I really hope that they are going to use the strongest ciphers, and disable the older, unsafe components.
>
> https://stribika.github.io/2015/01/04/secure-secure-shell.html
>
> I'd prefer them to force compatibility issues in the name of strengthening security.

Well, I work on a lot of CPU-constrained systems & systems with nasty schedulers, so I prefer to use the cypher with the least CPU impact possible (usually arcfour256 on boxes that support it).

By
Chas ()
on 2015-06-10 15:53

> Well, I work on a lot of CPU-constrained systems & systems with nasty schedulers, so I prefer to use the cypher with the least CPU impact possible (usually arcfour256 on boxes that support it).

You should read:

RFC 7465

RFC 7525

And then you should stop using RC4.

By
adam ()
on 2015-06-11 15:09

> > I really hope that they are going to use the strongest ciphers, and disable the older, unsafe components.
> >
> > https://stribika.github.io/2015/01/04/secure-secure-shell.html
> >
> > I'd prefer them to force compatibility issues in the name of strengthening security.
>
> Well, I work on a lot of CPU-constrained systems & systems with nasty schedulers, so I prefer to use the cypher with the least CPU impact possible (usually arcfour256 on boxes that support it).

You know what has minimal CPU impact? telnet.

By
&#12464;&#12524;&#12455; ()
on 2015-06-29 09:42

> > I really hope that they are going to use the strongest ciphers, and disable the older, unsafe components.
> >
> > https://stribika.github.io/2015/01/04/secure-secure-shell.html
> >
> > I'd prefer them to force compatibility issues in the name of strengthening security.
>
> Well, I work on a lot of CPU-constrained systems & systems with nasty schedulers, so I prefer to use the cypher with the least CPU impact possible (usually arcfour256 on boxes that support it).

So, I don't really see how your CPU-constrained systems really relate at all to SSH on Windows, indeed, what are your CPU-constrained systems running, probably something else entirely, maybe oddball RTOSes? Do they run SSH at all in the first place?

No offence, but it seems very off topic.

By
Just Another OpenBSD User ()
on 2015-06-10 12:44

The OpenBSD Foundation fundraising goal is almost half way (47.5%) achieved for 2015. Every contribution helps, please see details here: