New answers tagged client-side
Vulnerable clients are less of a problem than vulnerable servers. The major web browsers don't use OpenSSL for security, and most non-browser clients (eg. database interfaces or email programs) are rather picky about which servers they connect to.
dublicate actually good answers here and here I have tested my self firefox and google chrome on my systems - looks like not affected tested wget - affected - but probability that someone will use wget not high. So for clients side all looks not so bad, because general user tools looks like not affected.
If the question is understood properly, what is really asked here is how to do a key-exchange. Having implemented this in the same manner discussed for a security product, the following general approach works independent of the underlying transport protocol (and further does not make any assumptions about its underlying security): Client generates a ...
Both answers have identified SSL/TLS, but consider adding client authentication to the mix. This will guarantee that the server will only accept connections for authenticated / known clients. The drawback with this is that: a) Each client must be issued with its own client authentication certificate (although not necessarily from the same CA as the ...
Secure Sockets Layer (SSL) seems to be the answer you are looking for. Here's a quote from the Wikipedia page: They use X.509 certificates and hence asymmetric cryptography to assure the counterparty with whom they are communicating, and to exchange a symmetric key. This session key is then used to encrypt data flowing between the parties. This allows ...
What you are looking for is a public/private key pair otherwise known as SSL in the computer world. An SSL certificate as you mentioned is enough security since to find out what is being sent you need the private key of the certificate and you cant get that without breaking into the server. If you don't want to use SSL another option would be to use a ...
Top 50 recent answers are included