Re: [openssl-dev] OpenSSL version 1.1.0 published

N'morning UK. (^.^) Matt Caswell wrote: |On 25/08/16 22:14, Steffen Nurpmeso wrote: |> OpenSSL wrote: |>| OpenSSL version 1.1.0 released |> |> A bit distressing that it is me again, as if i would have |> something to do with that..., but: the tag

Re: [openssl-dev] OpenSSL version 1.1.0 published

|N'morning UK. (^.^) Ok i'm awake, you've created a new branch for that. Thanks. --steffen -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 published

On 26/08/16 11:42, Steffen Nurpmeso wrote: > N'morning UK. (^.^) > > Matt Caswell wrote: > |On 25/08/16 22:14, Steffen Nurpmeso wrote: > |> OpenSSL wrote: > |>| OpenSSL version 1.1.0 released > |> > |> A bit distressing that it is me again, as if

Re: [openssl-dev] OpenSSL version 1.1.0 published

Matt Caswell wrote: |> Matt Caswell wrote: |>|On 25/08/16 22:14, Steffen Nurpmeso wrote: |>|> OpenSSL wrote: |>|>| OpenSSL version 1.1.0 released |>|> |>|> A bit distressing that it is me again, as if i would have |>|>

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

On Fri, Aug 26, 2016 at 12:01 PM, Scott Ware wrote: > When building with Visual Studio 2008 SSE is disabled by default. When > building with Visual Studio 2012 and above you must supply a new flag > /arch:IA32 to not build with SSE. Would it be acceptable to update the >

Re: [openssl-dev] Fuzzer Patch(es)

On 08/25/2016 04:33 PM, Tom Ritter wrote: > NCC Group has prepared (or begun preparing) a patch that integrates > fuzzing of OpenSSL. Exciting stuff, most of which I will ignore for now and ask a targeted question. > - Because ossltest cooks MD5 to output a constant value, OpenSSL's RNG >

Re: [openssl-dev] Lib names on Windows changed in OpenSSL 1.1.0

Considering all of the API changes in 1.1, I think changing to the new library names are actually very useful, no chance of accidentally using old DLLs >-- Original Message -- > >In message <7ff7678e-3c4c-6343-3a5b-b2aa0caf7...@yahoo.com> on Fri, 26 Aug >2016 01:14:22 -0400, Ray Satiro

[openssl-dev] SSL_CTX_use_certificate_chain_file()

Hi,   Is there any negative impact ofusing SSL_CTX_use_certificate_file() and SSL_CTX_use_certificate_chain_file() together?   My application loads thecertificate using SSL_CTX_use_certificate_file()and loads the complete chain using SSL_CTX_use_certificate_chain_file().   Theapplication

[openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

When building with Visual Studio 2008 SSE is disabled by default. When building with Visual Studio 2012 and above you must supply a new flag /arch:IA32 to not build with SSE. Would it be acceptable to update the Configure process to add the /arch:IA32 if Visual Studio 2012 or greater is detected?

Re: [openssl-dev] SSL_CTX_use_certificate_chain_file()

On Fri, Aug 26, 2016 at 03:14:58PM +, asmar...@yahoo.com wrote: > Is there any negative impact ofusing SSL_CTX_use_certificate_file() and > SSL_CTX_use_certificate_chain_file() together? The first is redundant and should avoided. > My application loads thecertificate using

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

>> When building with Visual Studio 2008 SSE is disabled by default. When >> building with Visual Studio 2012 and above you must supply a new flag >> /arch:IA32 to not build with SSE. Would it be acceptable to update the >> Configure process to add the /arch:IA32 if Visual Studio 2012 or >>

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

On 8/26/16, 17:04, "openssl-dev on behalf of Andy Polyakov" wrote: >So suggestion is to impose /arch:ia32 on all users. Well, I personally >have lesser problem with that (as most most performance-critical >assembly code paths will

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

On Fri, Aug 26, 2016 at 5:11 PM, Blumenthal, Uri - 0553 - MITLL wrote: > On 8/26/16, 17:04, "openssl-dev on behalf of Andy Polyakov" > wrote: > >>So suggestion is to impose /arch:ia32 on all users. Well, I

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

If you want to dedicate a target to /arch:ia32, I can’t object or complain. VC-WIN32-XP sounds like a good choice for that. -- Regards, Uri Blumenthal On 8/26/16, 17:27, "openssl-dev on behalf of Scott Ware" wrote: >On Fri, Aug

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

> How about something like this.. A VC-WIN32-XP target that has > everything needed to make a max compatibility target > When building under VS2012 and above.. (I also tested in VS2015) > adds CFLAGS /arch:IA32 -D_USING_V110_SDK71_ > adds BIN_LDFLAGS=/subsystem:console,5.01 /opt:ref How about

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

In message

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

On Fri, Aug 26, 2016 at 5:43 PM, Andy Polyakov wrote: >> How about something like this.. A VC-WIN32-XP target that has >> everything needed to make a max compatibility target >> When building under VS2012 and above.. (I also tested in VS2015) >> adds CFLAGS /arch:IA32

Re: [openssl-dev] Lib names on Windows changed in OpenSSL 1.1.0

In message <7ff7678e-3c4c-6343-3a5b-b2aa0caf7...@yahoo.com> on Fri, 26 Aug 2016 01:14:22 -0400, Ray Satiro said: raysatiro> I am part of a project that has several build systems, and two in raysatiro> particular are not dynamically generated, a makefile and a number of