Am 03.10.13 11:08, schrieb David Osborne:
>
> Can you foresee any problems with this?
>
no. the core modules we use are quite well debugged and stress-tested
(we do not use nsperm). Various debugger / fortifyer / analyzer find
different things, so we can't exclude something showing up and if
Thanks Gustaf. That did the trick.
When we build a Wheezy package using debhelper v9, the default build flags
will automatically be included at build time, which are the following:
david@wheezybuild:~/naviserver$ dpkg-buildflags
CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-
Hi David,
many thanks for the good bug report. i was able to reproduce the problem
on FC,
The bug looks like a cut and paste problem, where the SHA context was
used for
sizing an MD5 entry and is several years old.
https://bitbucket.org/naviserver/naviserver/commits/4e205d1a1332dfa59c594adf15
Hi again,
I've just been attempting to package Naviserver for Debian Wheezy.
Using tip (and I think also with v4.99.5 tag), I get a stack overflow when
I try to load the nsperm module.
To reproduce, I built on Wheezy (7.1) with:
./autogen.sh --with-tcl=/usr/lib/tcl8.5 --enable-symbols
make
make