On Wed, Sep 23, 2015 at 03:57:18pm +0200, Andy Polyakov wrote:
> > - mingw debug and shared builds in master.
>
> While I can confirm problem with shared (fixable with attached patch,
> please double-check),
Can confirm that your patch works.
> I can't confirm problem with debug (please
Harri Porten wrote:
> Hi!
>
> In case you are interested in seeing the condition/decision source code
> coverage as achieved through the OpenSSL test suite:
>
> http://www.opencoverage.net/projects/openssl/index_html/sources.html
Is it just me, or are none of the files in ssl/ getting checked?
On Sun Sep 20 22:51:21 2015, steve wrote:
>
> In more detail I just tried a build from sources. I did this:
>
> set FIPSDIR=X:\some\for\fips\module\installation
> cd
> ms\do_fips
> cd
> perl Configure VC-WIN32 fips
> nmake -f ms\ntdll.mak
>
> With no problems. I'd suggest you try that as a
apps/rehash.c fails to compile on Solaris and other systems that do not
define NAME_MAX in limits.h.
Namely, Solaris has this comment in limits.h:
/*
* POSIX 1003.1a, section 2.9.5, table 2-5 contains [NAME_MAX] and the
* related text states:
*
* A definition of one of the values from
> It appears ARFLAGS is set to the architecture when using RPATH options
> in Configure's $cflags and $ldflags. RPATHS are important (IMHO)
> because OpenSSL can get into a situation where /usr/local/bin/openssl
> uses /usr/local/lib/libssl.so, but libssl.so uses the system's
>
>>> - mingw debug and shared builds in master.
>>
>> While I can confirm problem with shared (fixable with attached patch,
>> please double-check),
>
> Can confirm that your patch works.
>
>> I can't confirm problem with debug (please elaborate).
>
> The travis debug builds now also use
> So that in this case, i.e.
> travis-ci.org, I'd argue for limiting testing to current working de-facto
> status
> for all versions but master. Is it reasonable?
Yes, this makes a lot of sense; let's do it.
--
Senior Architect, Akamai Technologies
IM: richs...@jabber.at Twitter: RichSalz
On Friday 11 September 2015 15:34:15 Matt Caswell wrote:
> I've just opened a github pull request to show recent work I have been
> doing on rewriting the OpenSSL state machine (for version 1.1.0).
> See: https://github.com/openssl/openssl/pull/394
>
> My objectives for the rewrite were:
> -
Hello!
Current master treats -set_serial as digest alg and expects -set-serial
instead.
It is the only place in apps, x509 and ca commands seem to accept
-set_serial.
--
SY, Dmitry Belyavsky
___
openssl-bugs-mod mailing list
thanks, fixed!
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
On Thu, Sep 24, 2015 at 04:23:52pm +0200, Andy Polyakov wrote:
> >>> - mingw debug and shared builds in master.
> >>
> >> While I can confirm problem with shared (fixable with attached patch,
> >> please double-check),
> >
> > Can confirm that your patch works.
> >
> >> I can't confirm problem
On Thu, Sep 24, 2015 at 04:08:27PM +, Tiantian Liu via RT wrote:
> I used to use the SSL functions from OpenSSL 0.9.8, and my application
> worked fine. I applied the SSLv23_method() to setup the SSL context and
> communicate with customer's server over various SSL/TLS protocols.
>
> While,
Hi,
I am a software developer who is struggling on an application development based
on OpenSSL 1.0.1 (released on 2012-03-14) under Linux (32-bit Redhat).
I used to use the SSL functions from OpenSSL 0.9.8, and my application worked
fine. I applied the SSLv23_method() to setup the SSL context
On Thu Sep 24 19:17:34 2015, dlmee...@gmail.com wrote:
> In a bid to use openssl's non blocking mode with bio pair, we are calling
> SSL_do_handshake to perform handshake and we would like to do callback
> based on role of SSL.
>
> and Seems that OpenSSL does not expose any APi for doing the same.
In a bid to use openssl's non blocking mode with bio pair, we are calling
SSL_do_handshake to perform handshake and we would like to do callback
based on role of SSL.
and Seems that OpenSSL does not expose any APi for doing the same.
The attached patch adds a new API, which returns the
On Fri, Sep 25, 2015 at 01:05:34am +0530, Devchandra L Meetei wrote:
> Hey all
Hi,
> Just uploaded a patch at https://rt.openssl.org/Ticket/Display.html?id=4061
> for adding a new API for getting role, client or server.
>
> Please let me know what do you think of it.
There seems to be no patch
Hello,
Does OpenSSL support TLS with SHA2-512? I'm able to compile 1.0.1p with
SHA2-256 and SHA2-384 support, but not with SHA2-512. `openssl ciphers`
does not list any SHA512 cipher, while `openssl dgst` does support
SHA512.
Thanks,
Justin
___
I have made the reproducer cleaner and it should use relatively stable
API's of tlsfuzzer now.
openssl req -x509 -newkey rsa -keyout localhost.key -out localhost.crt\
-nodes -batch
~/dev/openssl/apps/openssl s_server -key localhost.key -cert\
localhost.crt
pip install --pre tlslite-ng
git clone
Stephen Henson via RT in gmane.comp.encryption.openssl.devel (Thu, 24 Sep
2015 11:52:05 +):
>I've tried a newer version of VC++ and I also get the "No Applink" error when
>it is trying to embed the fingerprint in libeay32.dll. I'll see if this can be
>fixed.
For FIPS 2.0.9 I had some patches
Hey all
Just uploaded a patch at https://rt.openssl.org/Ticket/Display.html?id=4061
for adding a new API for getting role, client or server.
Please let me know what do you think of it.
--
Warm Regards
--Dev
OpenPegasus Developer
"I'm one of those people that think Thomas Edison and the light
20 matches
Mail list logo
