Date: Thu, 14 Nov 2019 02:16:43 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 241960] ASLR impacted ports Message-ID: <bug-241960-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241960 Bug ID: 241960 Summary: ASLR impacted ports Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: cy@FreeBSD.org Reporter: dewayne@heuristicsystems.com.au Assignee: cy@FreeBSD.org Flags: maintainer-feedback?(cy@FreeBSD.org) I've created this PR to help others avoiding the time losses in tracking do= wn problems with ports that are adversely impacted when ASLR is enabled; specifically when the following sysctl's are set: kern.elf64.aslr.enable=3D1 kern.elf64.aslr.pie_enable=3D1 kern.elf64.aslr.stack_gap=3D1 kern.elf32.aslr.enable=3D1 kern.elf32.aslr.pie_enable=3D1 kern.elf32.aslr.stack_gap=3D1 When there is a problem, a workable solution is to disable ASLR for that particular process with, for example: proccontrol -m aslr -s disable $Dir/$Image; for example proccontrol -m aslr -s disable /usr/local/sbin/clamd which results in=20 # proccontrol -m aslr -q -p 64596 not forced, not active. net/ntp - fails to reliably start. With ASLR enabled it may take up to 60 attempts to start, when it does, it functions correctly. security/clamd - often starts first time, but when it doesn't, it usually results in messages which fill the logging disk with: LibClamAV Error: mpool_malloc(): Can't allocate memory (16781312 bytes). adjusting memorylock in login.conf is futile, that is not the problem. Other reports include: firefox/thunderbird ref:=20 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228964=20 Please feel free to add to this PR (might be better as a wiki). The intent= ion is to provide a vehicle where we can identify which ports have a problem, so that we can save time. I'd spent four hours reviewing clamd and freshclam = only to recall a prior change to kern.elf32...(a human memory swapout!) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241960-7788>