On Tue, 11 Sep 2012 09:45:22 -0700
buh...@lothlorien.nfbcal.org (Brian Buhrow) wrote:
provide further results. I assume a fix would want to be pulled
up,assuming I find it, on the grounds that it's a security fix. I'll also
see about trying -current and NetBSD-6, but I'm guessing those are
On Tue, 6 May 2014 07:56:22 -0700
Brian Buhrow buh...@nfbcal.org wrote:
hello. There was a fix implemented for the original problem by Chuck
Silvers and tested by me. I'll look to see if I can find the commits.
I'm not sure if it was documented in a pr or not or if it got pulled up to
On Mon, Sep 10, 2012 at 03:20:34PM -0700, Brian Buhrow wrote:
hello. I have a server which was, up until yesterday, running
NetBSD-4.0-stable. After I updated it to NetBSD-5.1 with sources from July
18 2012, I find my binaries from NetBSD-0.9A no longer run. The problem
seems to be
hello. It turns out this problem ismore sinister than I first
thought. I have another such binary that hangs the system entirely -- even
running ldd(1), which I assume runs through the same bad code causes the
system to become completely unresponsive -- no ping, no shell control-t,
hard
hello. I have a server which was, up until yesterday, running
NetBSD-4.0-stable. After I updated it to NetBSD-5.1 with sources from July
18 2012, I find my binaries from NetBSD-0.9A no longer run. The problem
seems to be that the file loader doesn't flag them as being a.out
executables,
