Not sure what platform the other person is using, but, for the record
the soname 1.0.0 causes big problems on Solaris 11 and up. Solaris 11
ships an OpenSSL 1.0.0 version in standard library locations, if anyone just
builds
anything higher than that, and do NOT modify build to add -R runtime
load
On Wed, Apr 22, 2015 at 12:12:45AM +, Shanku Roy wrote:
> lrw-r--r-- root root 2015-04-10 02:33 libcrypto.so ->
> libcrypto.so.1.0.0
> -rw-r--r-- root root 1988088 2015-04-10 02:27 libcrypto.so.1.0.0
>
> Is there any configure option in OpenSSL build scripts to not
On Tue, Apr 21, 2015 at 09:21:47PM +, Vollaro, John wrote:
> Is it possible to remove a message I posted to the openssl-user email forum?
No.
--
Viktor.
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinf
Hello OpneSSL Community,
OpenSSL build system currently creates symbolic links to actual binaries and
actual binaries are named as *.so.1.0.0 :
lrw-r--r-- root root 2015-04-10 02:33 libcrypto.so ->
libcrypto.so.1.0.0
-rw-r--r-- root root 1988088 2015-04-10 02:27 libc
Hello OpneSSL Community,
OpenSSL build system currently creates symbolic links to actual binaries and
actual binaries are named as *.so.1.0.0 :
lrw-r--r-- root root 2015-04-10 02:33 libcrypto.so ->
libcrypto.so.1.0.0
-rw-r--r-- root root 1988088 2015-04-10 02:27 libcry
Is it possible to remove a message I posted to the openssl-user email forum?
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipien
Reposting because I sent it to the "mta" address:
I am building OpenSSL 1.0.2a with no-dgram and no-dtls1. When I do so, I get a
linker error that BIO_new_dgram() is undefined.
The following appears to fix the issue:
cut here
--- s_server.c.orig 2015-03-19 17:17:53 -0700
++
> Is there a way to specify where objects and binaries go? Or, alternatively,
> where the source lives (rather like OpenSSH's --srcdir option)?
Not currently. This might change as the make "system" is being reviewed and
overhauled. Until then, rsync is your best option, as long as all your
p
I'm cross-compiling for multiple platforms. Any changes I make to platform A
have to be reflected in platform B.
Currently, I have to have two full source trees, and ensure that they're in
sync.
Is there a way to specify where objects and binaries go? Or, alternatively,
where the source liv
That was it... thank you so much!!!
Charles A. Barbe
Senior Software Engineer
Allworx, a Windstream company
245 East Main St | Rochester NY | 14604
charles.ba...@allworx.com | 585.421.5565
From: openssl-users [openssl-users-boun...@openssl.org] on behalf
It does not work using the openssl command-line tool.
I suspect that the .pem file I have only has the public key.
-Original Message-
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Salz, Rich
Sent: Monday, April 20, 2015 5:25 PM
To: openssl-users@openssl.org;
On Tue, Apr 21, 2015, Barbe, Charles wrote:
> I've spent the last few days configuring the cryptodev engine on my platform
> and I am also seeing the same behavior with that engine as I did with af_alg.
> It seems like OpenSSL does not even attempt to use the engine for ciphers. My
> next step
I've spent the last few days configuring the cryptodev engine on my platform
and I am also seeing the same behavior with that engine as I did with af_alg.
It seems like OpenSSL does not even attempt to use the engine for ciphers. My
next step is to start plowing through the openssl code to figur
Thanks for your response, Viktor. You views fall in line with our opinions on
how the situation should be handled.
Any other opinions?
> Date: Mon, 20 Apr 2015 16:26:43 +
> From: openssl-us...@dukhovni.org
> To: openssl-users@openssl.org
> Subject: Re: [openssl-users] Peer closing connection
Obvious simplification:
cut here
--- s_server.c.orig 2015-03-19 17:17:53 -0700
+++ s_server.c 2015-04-20 11:27:30 -0700
@@ -2183,6 +2183,7 @@
# endif
#endif
+#ifndef OPENSSL_NO_DGRAM
if (stype == SOCK_DGRAM) {
sbio = BIO_new_dgram(s, BIO_NOCLOSE); @@ -2220,6 +2221,9
On 20/04/2015 18:26, Viktor Dukhovni wrote:
On Mon, Apr 20, 2015 at 03:03:37PM +, Jason Schultz wrote:
We have also read that this particular behavior is not unheard of in SSL
implementations, and treating the TCP FIN as a proper way to close the
connection as described above is OK.
Only w
On 04/20/15 00:10, Salz, Rich wrote:
Sometimes, the program crashes when doing an SSL_CTX_free; before the
crash, ctx is an invalid pointer, that's why I can get a valid value from
SSL_CTX_get_max_cert_list (ctx), so it's not a double free problem.
You mean it's a VALID pointer?
We'll need a mo
17 matches
Mail list logo
