On 5/25/18 3:20 PM, Alexander Bluhm wrote: > On Tue, May 22, 2018 at 07:32:29AM +0200, Harald Dunkel wrote: >> Do you think this is worth a syspatch? > > You are asking this question for three times. The answer is no. >
Twice, IIRC. My apologies. Thanx for your answer. I am glad that I could help to verify the fix. > Errata and syspatch are for security issues that can be triggered > remotely or by a local non-root user. Surely I have not your insight into the internals, so I am glad to learn that this problem cannot be triggered remotely. > If we would fix every panic > in stable, we could not concentrate on developing OpenBSD current. > Doing errata involves at least five people who could spend their > time on creating new features instead. We provide security fixes, > may handle stability issues, but will not bug fix old releases. > > Bugs like this one show lack of release testing. So instead of > asking to repair old stuff, please help us to make new things better. > By testing snapshots and diffs on production or production-like > systems, the community can improve OpenBSD releases. > I am running OpenBSD stable on my gateway at home. Surly I can move it to the current version. However, I am not allowed to put the production environment of a mid size company at risk. In this context OpenBSD 6.3 is not "the old stuff", but the stable version released just a few weeks ago. Its *the* version I should run. The syspatches help me to keep downtimes as short as possible. IMU the syspatch support is a major improvement of OpenBSD. Of course I highly appreciate the work of all OpenBSD developers and maintainers. Regards Harri
