I think your problem (and the stack overflow) is caused by using "CALLBACK" in
the 3 function typedefs. Try using __cdecl instead of CALLBACK.
__Martin
> On Tue, 11 Oct 2016 16:15:24 +, Simone Sgualdini via RT said:
>
>
> Hi,
>
>
> I'm writing a c++ server application that calls thou
> On Thu, 25 Sep 2014 11:24:36 +0200, Michael Menge said:
>
> Quoting Andy Polyakov :
>
> >>> in that case it crashes here:
> >>>
> >>> if (s->msg_callback)
> >>> s->msg_callback(0, s->version, SSL3_RT_HANDSHAKE,
> >>> s->init_buf->data, (size_t)s->init_num + 4, s, s->
In my experience, the best way to build your own rpm is to install the old
version's src rpm from your Linux distribution, copy the new source tar file
into the rpmbuild SOURCES directory and edit the spec file to use it. Also
change the package version numbers in the spec file and review any patc
Why are building your own openssl? Did you try the official Ubuntu update?
sudo apt-get update
sudo apt-get upgrade
__Martin
> On Mon, 14 Apr 2014 16:59:06 +0530, LOKESH JANGIR said:
>
> Hi,
>
> I am installing openssl in /usr/local/openssl folder and it is creating
> libssl.a and libcry
See http://www.openssl.org/related/binaries.html for an OpenSSL installer for
64-bit Windows. Dunno about managedopenssl.dll.
__Martin
> On Thu, 14 Jun 2012 15:23:03 +0530, sridevi chilumula said:
>
> Hi
>
> Can you please help me on this.
>
> Sridevi Chilumula
> Tata Consultancy Service
> On Wed, 04 Mar 2009 21:40:52 +, Tanguy Fautré said:
>
> We've figured the try/except modification was safe for the following
> reasons.
>
> - The traversal is read-only. Trapping an access violation/segfault in
> this case is safe (i.e. we do not modify an unknown memory location).
>
> On Mon, 02 Mar 2009 16:56:39 +, Tanguy Fautré said:
>
> We also suspected that the crashes could be caused by heap corruption done
> by our application. In order to disprove this, we enabled full CRT checks on
> memory allocation/deallocations; no error came up. On top of that, MSDN
> do
> On Fri, 1 Aug 2008 08:26:55 +0200, Ger Hobbelt said:
>
> I'm glad this works for you, but be warned: the fact that that cute
> hack works in your environment now will not guarantee it will work
> elsewhere. The fact that you need to transmit another few ('faked')
> bytes to get the data you
> On Wed, 19 Mar 2008 00:12:56 -0700, Larry Bugbee said:
>
> Hi,
>
> I'm building 0.9.9 from the latest SNAP and have been successful with
> openssl (the app) but no joy with building .dylib files on MacOSX.
> The linker fails with:
> ld: absolute addressing (perhaps -mdynamic-no-pi
> Hi, Yair Elharrar!
>
> For me it looks bad. :-/ Because, BN_sub doesn't handle this situation (r =
> b):
> 1) BN_sub call BN_uadd(r,a,b), but r = b, then
> 2) BN_sub change r->neg, but r = b, then
> 3) BN_sub call BN_expand(r), then
> 4) BN_sub call BN_ucmp(a,b), but b here is not that b th
> On Tue, 18 Dec 2007 09:15:42 +0100, Jurko Gospodnetić said:
>
>Hi Martin.
>
>Thank you for replying.
>
> > Yes, sometimes there is nothing on the error queue after SSL_get_error() has
> > returned SSL_ERROR_SYSCALL.
>
>That's what I assumed.
>
> > Also, if your app is multit
> On Wed, 12 Dec 2007 21:22:50 +0100, Jurko Gospodnetiæ said:
>
>Hi.
>
>Could someone more knowledgeable with OpenSSL please explain to me
> exactly how the OpenSSL error information queue (accessed using
> ERR_get_error(), SSL_get_error() and related APIs) is supposed to be used.
>
> On Thu, 9 Aug 2007 16:09:14 -0700, John Firebaugh said:
>
> Following the Windows build instructions in the OpenSSL FIPS Users Guide
> (using MinGW and MSYS) results in OpenSSL libraries that may crash if
> used in a multithreaded program.
>
> The problem is due to the definition of MS_STAT
> On Tue, 7 Aug 2007 14:57:41 +0200 (CEST), Jan Pechanec via RT said:
>
> building the fips module ends with a tricky error:
>
> /usr/ccs/bin/ld: illegal option -- n
> usage: ld [-6:abc:d:e:f:h:il:mo:p:rstu:z:B:CD:F:GI:L:M:N:P:Q:R:S:VY:?]
> file(s)
> [-64] enforce a
> On Sat, 2 Jun 2007 19:35:37 +0200, Stephen Henson said:
>
> On Fri, Jun 01, 2007, Robin Bryce wrote:
>
> > Hi,
> >
> > In both openssl-0.9.8b and openssl trunk ssl3_send_server_key_exchange
> > passes the address of an uninitialised variable to RSA_sign as the
> > siglen parameter. In the
> On Fri, 1 Jun 2007 16:21:35 +0100, Robin Bryce said:
>
> Hi,
>
> In both openssl-0.9.8b and openssl trunk ssl3_send_server_key_exchange
> passes the address of an uninitialised variable to RSA_sign as the
> siglen parameter. In the presence of RSA_FLAG_SIGN_VER and an engine
> implementatio
> On Fri, 02 Mar 2007 13:21:18 +0100, Peter Sylvester said:
>
> One can omit the SSL_CTX_free but in oder to be clean, someone must call
> it, and this may unfortunately not necessarily be the same instance who
> created it.
OK, so a less hacky solution using the current APIs would be to do
>>>>> On Fri, 02 Mar 2007 07:58:14 +, Darryl Miles said:
> Delivered-To: openssl-dev-l@master.openssl.org
> Delivered-To: openssl-dev@openssl.org
>
> Martin Simmons wrote:
> >>>>>> On Thu, 01 Mar 2007 11:40:24 +0100, Peter Sylvester
> On Thu, 01 Mar 2007 11:40:24 +0100, Peter Sylvester said:
>
> Hi,
>
> A call to SSL_new increments the reference count of the SSL_CTX object.
> In some application contexts one would like to pass around an SSL_CTX object
> and share it.
>
> If sharing occurs before an SSL_new is called an
and can be excused from tweaking
> arguments to LoadLibrary calls in Win64 port. I'd say 32 in name is more
> of less meaningless artifact. At least it's more than sufficient to
> maintain *any* consistent naming between 32- and 64-bit builds.
Right, there are alread
ll and ssleay32.dll, and Mingw build crypto32.dll and
> ssl32.dll. Patch includes code to support this difference, but I'm
> not absolutely sure it belongs there.
BTW, what is the meaning of "32" in the names?
ion 'C' proved invalid
ERROR in CLIENT
5924:error:1407E086:SSL routines:SSL2_SET_CERTIFICATE:certificate verify
failed:s2_clnt.c:1048:
SSLv2, cipher (NONE) (NONE)
1 handshakes of 256 bytes done
which I understand are planned failures.
--
Martin Simmons
> - Original Me
o ran make test, which printed 6571 lines of "stuff". How do I tell if
this is good stuff?
--
Martin Simmons
openssl-Configure.patch
Description: Binary data
23 matches
Mail list logo
