> Thanks for the update. I was curious why it was removed from 1.0.1. It
> seemed to be beyond the scope of a bug fix. Given 1.0.2 has now been
> released, should eng_rsax been removed there too?
I goofed removing it from 1.0.1
For 1.0.2 it wasn't compiled so it's just an OCD kinda thing :)
On 28/01/15 14:23, John Foley wrote:
> Thanks for fixing this. Windows is now building on 1_0_1-stable.
> Having said that, you inspired me to add another job on my jenkins
> server to to a sanity build on master for Windows. I'm seeing the
> following error when trying to build on master usin
Thanks for fixing this. Windows is now building on 1_0_1-stable.
Having said that, you inspired me to add another job on my jenkins
server to to a sanity build on master for Windows. I'm seeing the
following error when trying to build on master using the identical build
process. Should I dig de
> I'm sure this would resolve the issue. The problem exists in 1.0.1, but not
> 1.0.2. Here's the entry in the 1.0.1 libeay.num:
Fixed. It was a mistake to remove engine_rsax, and I just reverted that.
Should show up in the snapshots within an hour
___
Thanks for the update. I was curious why it was removed from 1.0.1. It
seemed to be beyond the scope of a bug fix. Given 1.0.2 has now been
released, should eng_rsax been removed there too?
On 01/27/2015 01:06 PM, Salz, Rich wrote:
> Oh, I thought it was in master!
>
> In 1.0.1 it was a mista
Oh, I thought it was in master!
In 1.0.1 it was a mistake to remove eng_rsax. And a commit to fix that will be
submitted shortl.
--
Principal Security Engineer, Akamai Technologies
IM: rs...@jabber.me Twitter: RichSalz
___
openssl-dev mailing lis
I'm sure this would resolve the issue. The problem exists in 1.0.1, but
not 1.0.2. Here's the entry in the 1.0.1 libeay.num:
ENGINE_load_rsax 4652 EXIST::FUNCTION:ENGINE
And here's the entry in the 1.0.2 flavor of libeay.num:
ENGINE_load_rsax 4652 NOEXIST::FUNCTION:
You just need to to "make
> It looks like the Windows export symbols may need updating now that the
> rsax engine has been removed (yesterday). Here's the error from the log...
If you remove the reference to it from util/libeay.num does that fix the build?
--
Principal Security Engineer, Akamai Technologies
IM: rs...@j
It looks like the Windows export symbols may need updating now that the
rsax engine has been removed (yesterday). Here's the error from the log...
link /nologo /subsystem:console /opt:ref /debug /dll /out:out32dll\libeay32.dll
/def:ms/LIBEAY32.def @C:\Users\ADMINI~1\AppData\Local\Temp\1\nm3A91.t
