Contributed by tbert on 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 (81.83.83.198) on
By Chas (147.154.235.102) chas@syro.org on
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.
Comments
By Blake (2a01:e34:ec06:8f90:cabc:c8ff:fedb:4d83) on 2112.net
>
> 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).
Comments
By Chas (147.154.235.102) on
You should read:
RFC 7465
RFC 7525
And then you should stop using RC4.
By adam (2620:0:100d:0:d08a:81d3:285f:f5ec) on
> >
> > 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 グレェ (107.205.12.115) on
> >
> > 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).
That's fine. . . but recent versions of Windows have *substantially* higher computational needs than OpenBSD. . .
OpenBSD still runs on various DEC Vax iterations!
No version of windows *ever* did.
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 (95.42.222.99) on
http://www.openbsdfoundation.org/campaign2015.html