On 3/22/2010 5:10 PM, Andy Polyakov wrote:
The nasmw.exe file no longer exists. The program is now distributed as
simply nasm.exe and the build files should be adjusted in 1.0 and 0.9.8
branches to reflect this.
>>> ??? The issue was addressed in 0.9.9 and 1.0 a while (like two year
The nasmw.exe file no longer exists. The program is now distributed as
simply nasm.exe and the build files should be adjusted in 1.0 and 0.9.8
branches to reflect this.
??? The issue was addressed in 0.9.9 and 1.0 a while (like two years)
ago. VC-32.pl checks for both nasm and nasmw and pick new
On 3/22/2010 4:02 PM, Andy Polyakov wrote:
>> The nasmw.exe file no longer exists. The program is now distributed as
>> simply nasm.exe and the build files should be adjusted in 1.0 and 0.9.8
>> branches to reflect this.
>
> ??? The issue was addressed in 0.9.9 and 1.0 a while (like two years)
>
On 22/03/10 20:57, Andy Polyakov wrote:
I can't get the latest version of openssl to build on Darwin.
It was working for years, so what's your version?
Darwin 5.5
I *think* the assembler is confused by the quotes in comments.
You mean apostrophes, like in "it's."
I did this
./Configur
>>> I agree that OPENSSL_isservice() cannot be changed,
>> ??? My suggestion for *you* was to modify it to unconditionally
>> return 1...
> Our application can both run in foreground and in service context. So
> simply changing to return 1 is not possible.
If changing to return 1 is not acceptable
The nasmw.exe file no longer exists. The program is now distributed as
simply nasm.exe and the build files should be adjusted in 1.0 and 0.9.8
branches to reflect this.
??? The issue was addressed in 0.9.9 and 1.0 a while (like two years)
ago. VC-32.pl checks for both nasm and nasmw and pick n
I can't get the latest version of openssl to build on Darwin.
It was working for years, so what's your version?
I *think*
the assembler is confused by the quotes in comments.
You mean apostrophes, like in "it's."
I did this
./Configure darwin-ppc-cc
make
The build fails thus:
...
cc -I.
On Mon, Mar 22, 2010 at 04:30:23PM +0100, Kurt Roeckx wrote:
> On Mon, Mar 22, 2010 at 02:01:23PM +0100, Stephen Henson via RT wrote:
> >
> > I notice that the certificate in question is using SHA256. Do the
> > affected applications call SSL_library_init() only and not
> > OpenSSL_add_all_algorit
On Mon, Mar 22, 2010 at 04:30:23PM +0100, Kurt Roeckx wrote:
> On Mon, Mar 22, 2010 at 02:01:23PM +0100, Stephen Henson via RT wrote:
> >
> > I notice that the certificate in question is using SHA256. Do the
> > affected applications call SSL_library_init() only and not
> > OpenSSL_add_all_algorit
On Mon, Mar 22, 2010 at 02:01:23PM +0100, Stephen Henson via RT wrote:
> > [k...@roeckx.be - Mon Mar 22 09:48:17 2010]:
> >
> > As far as I can tell client does exactly the same between a connection
> > that works and one that doesn't work. The server just closes the
> > connection.
> >
> > No c
On Mon, Mar 22, 2010 at 02:01:23PM +0100, Stephen Henson via RT wrote:
> > [k...@roeckx.be - Mon Mar 22 09:48:17 2010]:
> >
> > As far as I can tell client does exactly the same between a connection
> > that works and one that doesn't work. The server just closes the
> > connection.
> >
> > No c
> [k...@roeckx.be - Mon Mar 22 09:48:17 2010]:
>
> As far as I can tell client does exactly the same between a connection
> that works and one that doesn't work. The server just closes the
> connection.
>
> No client certificates are being used, but for some reason that gets
> in the error log.
Hi,
It seems that with with the change to 0.9.8m postfix and dovecot
don't properly accept connections anymore in all cases.
In postfix's log this look like:
SSL_accept:SSLv3 flush data
read from 7FA27CBE5E70 [7FA27CBEF150] (5 bytes => -1 (0x))
SSL_accept:error in SSLv3 read clien
13 matches
Mail list logo
