S
Sat Apr 30 23:31:50 CDT 2005
I guess Microsoft considers communications in Windows secure (true - you
have selection of protocols supporting TLS, encrypted RPC etc, VPNs and easy
to deploy IPsec) and leave space for ISVs. You can get OpenSSH for Windows
for free under BSD license (do wjhatever you want -
http://sshwindows.sourceforge.net).
If secure communications are transparent to applications - like Windows
IPsec, for instance - malware will spread anyway. Introducing communications
that will require individual configuration for each network node and
session, like with SSH, is not manageable in enterprise and cannot replace
Windows file and print services. So FTP-TLS and SSH won't help here. The
right strategy would be - get secure and stay secure.
--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-
"Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom> wrote in message
news:elIbsVDTFHA.1384@TK2MSFTNGP09.phx.gbl...
> > More research is not required: Microsoft provides neither SSH nor
FTP-TLS
> > software.
>
> Why is that? You would think that with the current set of malware plaguing
> Windows, Microsoft would offer SSL and SSH for Windows as components of
some
> kind.
> Seems odd.
>
> What have I missed here?
>
> Thanks
>
> Stephen Howe
>
>