On Wed, Nov 15, 2023 at 01:48:19PM +0200, Vitaly Shevtsov wrote:
> Even arcticfox cannot be built due to the same reason.
Christos fixed it - cvs update and rebuild, and check you have
# nm -g /lib/libc.so | grep ssp
00055136 T __ssp_protected_getcwd
0005512
t; > io.c:(.text+0x22d6): undefined reference to `__ssp_protected_read'
> > ld: io.o: in function `after_beginfile':
> > io.c:(.text+0x27c7): undefined reference to `__ssp_protected_read'
> > ld: io.o: in function `redirect_string':
> > io.c:(.text+0x55e7): undefined r
Even arcticfox cannot be built due to the same reason.
--
Vitaly
Talking of SSP, what can you do once a detection happens?
I see in /var/log/messages:
Nov 15 06:59:32 mail -: mail.example.com exim - - - stack overflow detected;
terminated
I have:
kern.coredump.setid.dump = 1
kern.coredump.setid.path = /var/crash/%n.core
erride _FORTIFY_SOURCE with CFLAGS in pkgsrc, because SSP is
enforced through wrappers. Minimal reproducer:
#define _FORTIFY_SOURCE 2
#include
ssize_t (*myread)(int d, void *buf, size_t nbytes);
int main(void) {
char c;
myread =
return myread(STDIN_FILENO, , sizeof(c));
}
: in function `get_a_record':
> io.c:(.text+0x22d6): undefined reference to `__ssp_protected_read'
> ld: io.o: in function `after_beginfile':
> io.c:(.text+0x27c7): undefined reference to `__ssp_protected_read'
> ld: io.o: in function `redirect_string':
> io.c:(.text+0x55e7): undefined
p_protected_read'
ld: io.o:io.c:(.text+0x5606): more undefined references to
`__ssp_protected_read' follow
If I simply edit /usr/include/ssp/ssp.h to remove the __gnu_inline__ from
the definition of__ssp_inline and make it static again, then gawk builds,
i.e., reverting
-/* $NetBSD: ssp.h,v
On Tuesday, November 14th, 2023 at 8:48 AM, Vitaly Shevtsov
wrote:
> Hello!
>
> What if you put -D_FORTIFY_SOURCE=0 into Makefile, will it help?
Won't know until I try :)
Will have to wait a bit, though ... currently building firefox.
If someone else can try before tomorrow, it would be
same as reported here,
> https://mail-index.netbsd.org/pkgsrc-users/2023/11/13/msg038461.html
>
> I can now confirm that downgrading userland to Nov. 8 2023 allows the build
> to complete successfully.
> It's highly likely the issue is related to the changes introduced to ssp on
> Nov. 10 2023
>
> Regards,
>
--
Vitaly
the build to
complete successfully.
It's highly likely the issue is related to the changes introduced to ssp on
Nov. 10 2023
Regards,
Hi!
A user tried following the ssp man page and got unexpected results.
I'd like to know if the man page is wrong or implementation.
Here's his translated message:
Take any program using stdio.h, say
#include
#include
as the only lines, and use gcc as described in ssp(3):
gcc -I/usr
In article <20151126114027.gw12...@danbala.tuwien.ac.at>,
Thomas Klausner <w...@netbsd.org> wrote:
>Hi!
>
>A user tried following the ssp man page and got unexpected results.
>I'd like to know if the man page is wrong or implementation.
>
>Here's his translated mess
With up-to-date sources, I'm seeing the following error on multiple
ports (including evbcf, evbppc, mac68k, sun2, vax)
cc1: warnings being treated as errors
/build/netbsd-local/src/tests/lib/libc/ssp/h_stpncpy.c: In function 'main':
/build/netbsd-local/src/tests/lib/libc/ssp/h_stpncpy.c:44
13 matches
Mail list logo
