- User Since
- May 10 2014, 4:26 AM (370 w, 6 d)
Wed, Jun 16
Tue, Jun 15
Mon, Jun 14
Sun, Jun 6
Fri, Jun 4
Thu, Jun 3
Tue, Jun 1
Mon, May 31
Building WITHOUT_OPENSSL doesn't make it far enough to test wpa build, libradius needs a little love:
Tue, May 25
Sun, May 23
Fri, May 21
Thu, May 20
May 18 2021
May 17 2021
May 10 2021
May 7 2021
Commit message in my D30159 branch (--pretty-fuller):
If you don't mind, I'll make the two minor corrections and commit it. Is that ok?
May 6 2021
May 5 2021
This is certainly an improvement over the original.
Apr 29 2021
Apr 28 2021
I will do a little more testing and commit.
The work around works on my sandbox machine today but does not on the laptop when PIE is enabled on both. Without PIE and with ASLR there is no need for the workaround.
Apr 27 2021
This is probably the only solution, as it works with PIE enabled, regardless of whether ASLR is enabled or not. See discussion at D29832.
Having done a couple of reboots since enabling PIE and increasing stack to 200, now after this last reboot about an hour ago it now fails regardless of how much stack I give it (even obscene amounts). Increasing stack to 200, 1024, 20000, 200000, all of which I've tried, will not work after this latest reboot.
Juxtapositioned to this is that enabling PIE causes firefox to segfault but that's for another review.
Adjusting the stack to 200, like OpenBSD does, resolves this issue when PIE is enabled.
Ok, I can finally reproduce the problem with kern.elf64.aslr.pie_enable=1. PIE introduces a new set of problems that were not addressed by procctl() at the time.
Apr 26 2021
This is already done at line 447 of ntpd.c. Why do we need this?