That is impossible. If you can't secure your Win9x client then you can
never ever establish any kind of secure communication from that client.
Security has to begin at the end points.
After you secure the client's cerificate store you then use those
certificates to secure the communication.
Title:
As somebody stated there is difference
between authentication and authorization.
Servers should be protected from "man in the
middle" attacks via "Access Control" software which authorize access to files,
servers, etc. via a triple combination of keys:
FQDN (fully qualified domain
Greg Stark wrote:
As somebody stated there is difference between authentication and
authorization. Servers should be protected from "man in the middle"
attacks via "Access Control" software which authorize access to
files, servers, etc. via a triple combination of keys:
FQDN (fully qualified
Hello:
I'm still learning SSL. I still do no understand how does or if
SSL/TSL prevents from a "man in the middle" attack. If the certificates
are good, no problem. But, how does a client, or what must I do for a
client to check the validity of a certificate, even a signed one from a
trusted
Darío Mariani wrote:
Hello:
I'm still learning SSL. I still do no understand how does or if
SSL/TSL prevents from a "man in the middle" attack. If the certificates
are good, no problem. But, how does a client, or what must I do for a
client to check the validity of a certificate, even a
