On 2013-03-08 10:00, Jurko Gospodnetić wrote:
...
2. Remove the need for including the windows.h header from rand.h
completely by simply explicitly declaring those few windows specific
types used there. I believe it is just the UINT, WPARAM & LPARAM types
used in RAND_event() - all simple typ
On 03/06/2013 10:47 AM, Michael Tuexen wrote:
...
> It fails because dtls1_do_write() contains the following check:
>
>OPENSSL_assert(s->d1->mtu >= dtls1_min_mtu()); /* should have
> something reasonable now */
>
> which fails if s->d1->mtu is set to zero.
> Isn't this after the sending faile
I strongly recommend reading the user guide, as it'll help a lot. You need to
do more than simply link your application with libcrypto and libssl. There's a
sample shell script, fipsld, that's also provided in the distribution that
shows the necessary actions (and can even be called in place o
Hi all.
At least in OpenSSL 1.0.1e, rand.h header file includes the Windows
specific windows.h header and does so in such a way that it can cause
conflicts with the rest of OpenSSL code.
windows.h defines some symbols like X509_NAME & X509_EXTENSIONS that
conflict with OpenSSL types. o
On Thu, 2013-03-07 at 19:54 +0100, Kurt Roeckx via RT wrote:
> On Thu, Mar 07, 2013 at 12:41:43PM +0100, Tomas Mraz via RT wrote:
> > On Fri, 2013-03-01 at 22:01 +0100, Kurt Roeckx wrote:
> > > I can't either, and yet I have multiple people reporting problems
> > > with the 1.0.1e version saying t
cc: openssl-b...@openssl.org
> On Wed, Mar 06, 2013, Matt Caswell wrote:
>
> > See the README for instructions, under the SUPPORT section:
> >
> > http://git.openssl.org/gitweb/?p=openssl.git;a=blob_plain;f=README;hb=refs/heads/master
> >
>
> ... or the FAQ:
>
> http://www.openssl.org/suppor
Hello,
I am trying to cross compile FIPS compliant openssl module
(openssl-fips-ecp-2.0.2.tar.gz) for linux armv4 pratform :
I have used following script to setup the environment:
===
export MACHINE=armv4t
export RELEASE=2.6.23
export SYSTEM=Linux
expor
