On Tue, Jun 20, 2006 at 07:03:49PM +0200, Kurt Roeckx wrote:
>> Applications are also expected to provide a thread ID callback by
>> calling CRYPTO_set_id_callback(), although the failure to do so should
>> not be a problem on Linux where different threads run with different
>> PIDs, since OpenSSL
On Tue, Jun 20, 2006 at 02:06:25PM +0200, Bodo Moeller wrote:
> On Fri, Jun 09, 2006 at 07:02:36PM +0200, Kurt Roeckx wrote:
> > On Fri, Jun 09, 2006 at 12:58:56PM +0200, Howard Chu via RT wrote:
>
> >> Given the lack of response here, we're tracking this now as
> >> http://www.openldap.org/its/in
Current snapshots use a more thorough locking approach that takes into
account inconsistent cache views on multi-processor or multi-core
systems (where consistency can be reached by obtaining locks). The
application has to call CRYPTO_set_id_callback() for OpenSSL to work
properly.
__
On Fri, Jun 09, 2006 at 07:02:36PM +0200, Kurt Roeckx wrote:
> On Fri, Jun 09, 2006 at 12:58:56PM +0200, Howard Chu via RT wrote:
>> Howard Chu wrote:
>>> I'm seeing a lot of "bad record mac" errors when receiving a lot of
>>> connection requests at once. It sounds the same as this email
>>> http
On Fri, Jun 09, 2006 at 12:58:56PM +0200, Howard Chu via RT wrote:
>
> Howard Chu wrote:
> > I'm seeing a lot of "bad record mac" errors when receiving a lot of
> > connection requests at once. It sounds the same as this email
> > http://www.redhat.com/archives/rhl-list/2005-May/msg01506.html
> >
Howard Chu wrote:
> I'm seeing a lot of "bad record mac" errors when receiving a lot of
> connection requests at once. It sounds the same as this email
> http://www.redhat.com/archives/rhl-list/2005-May/msg01506.html
> which unfortunately was never replied to.
>
> Surrounding the SSL_accept call
