Hello,
Stephen Henson via RT r...@openssl.org wrote:
|On Mon Dec 08 19:58:31 2014, sdao...@yandex.com wrote:
| If people start using SSL_CONF_CTX as they are supposed to with
| v1.0.2, then it can be expected that users start using strings
| like, e.g. (from my thing),
|
| set
Hello,
Stephen Henson via RT r...@openssl.org wrote:
|On Mon Dec 08 19:58:31 2014, sdao...@yandex.com wrote:
| If people start using SSL_CONF_CTX as they are supposed to with
| v1.0.2, then it can be expected that users start using strings
| like, e.g. (from my thing),
|
| set
On Thu, Dec 11, 2014, Steffen Nurpmeso via RT wrote:
are hard (not only to parse) for users but there is a lot of
information for good in very few bytes; sad is
Received SIGPIPE during IMAP operation
IMAP write error: error::lib(0):func(0):reason(0)
OpenSSL itself should
Dr. Stephen Henson st...@openssl.org wrote:
|On Thu, Dec 11, 2014, Steffen Nurpmeso via RT wrote:
| are hard (not only to parse) for users but there is a lot of
| information for good in very few bytes; sad is
|
| Received SIGPIPE during IMAP operation
| IMAP write error:
Dr. Stephen Henson st...@openssl.org wrote:
|On Thu, Dec 11, 2014, Steffen Nurpmeso via RT wrote:
| are hard (not only to parse) for users but there is a lot of
| information for good in very few bytes; sad is
|
| Received SIGPIPE during IMAP operation
| IMAP write error:
Kurt Roeckx via RT r...@openssl.org wrote:
|On Mon, Dec 08, 2014 at 07:58:31PM +0100, Steffen Nurpmeso via RT wrote:
| set ssl-protocol=ALL,-SSLv2
|
| This results in the obvious problem that when they (get)
| upgrade(d) their OpenSSL library they will see a completely
| intransparent
Kurt Roeckx via RT r...@openssl.org wrote:
|On Mon, Dec 08, 2014 at 07:58:31PM +0100, Steffen Nurpmeso via RT wrote:
| set ssl-protocol=ALL,-SSLv2
|
| This results in the obvious problem that when they (get)
| upgrade(d) their OpenSSL library they will see a completely
| intransparent
On Mon, Dec 08, 2014 at 07:58:31PM +0100, Steffen Nurpmeso via RT wrote:
set ssl-protocol=ALL,-SSLv2
This results in the obvious problem that when they (get)
upgrade(d) their OpenSSL library they will see a completely
intransparent error message that no normal user will understand:
It was
