Kenneth Goldman/Watson/IBM@IBMUS wrote on 11/20/2013 10:37:04 AM:
> > Encrypt with a private key for integrity purposes: this shows that the
> > data that was encrypted corresponds to the owner of the key.
> > Encrypt with a public key for confidentiality purposes: this shows that
> > the data can
On 11/18/2013 11:29 AM, Robert W Weaver wrote:
owner-openssl-us...@openssl.org (Kenneth
Goldman/Watson/IBM@IBMUS) wrote on 11/18/2013 10:03:29 AM:
> Do not encrypt with a private key. Encrypt with the public key and
> decrypt with the private key.
Encrypt with a private key for integrity purp
Thank you for your advice. SSL_CTX_get_cert_store() was the right clue and
X509_STORE_add_cert() did the trick.
> -Original Message-
> From: owner-openssl-us...@openssl.org [mailto:owner-openssl-
> us...@openssl.org] On Behalf Of Dave Thompson
> Sent: 19 November 2013 00:07
> To: openssl-u
Salz, Rich wrote:
The common practice is for clients to connect in the clear, then issue a command to turn
on TLS, such as the SMTP "STARTTLS" command.
It is only common practice for a small number of well known protocols.
This doesn't mean it is the best solution.
If you have a bespoke pro
Rahila Syed wrote:
I am using OpenSSH compression for compressing data between
PostgreSQL servers. I am using following command,
ssh -c arcfour,blowfish-cbc -4 -2 -v -C -L 3304:localhost:5432 user@server2
I want to know if vulnerability CRIME which attacks SSL deflate
compression algorithm
