On Tue, Mar 31, 2015 at 02:47:21PM +0200, Willem Jan Withagen wrote: > On 31-3-2015 13:02, Slawa Olhovchenkov wrote: > > On Tue, Mar 31, 2015 at 12:28:04PM +0200, Willem Jan Withagen wrote: > > > >>>> Slawa, > >>>> > >>>> I can't tell you that, but it is in r202209. And you can ask the one > >>>> that removed it (ed@). :) > >>>> Like r202209 says 5 years ago: > >>>> Maybe we can address this in the future if it turns out to be a > >>>> real issue. > >>> > >>> What about issue talk? > >>> Opened file outside chroot? /dev/null and /var/run/logpriv still opened. > >>> Disabling logging for chrooted accounts? Realy?! > >> > >> Read the submit message!? The reason is there, nothing with security as > >> I read it, but it just did not fit into the way the new lib for wtmp > >> worked/works. > > > > I read it. And I don't understund it. May be I don't know somewere. > > Or missed. Can you explain? > > In 9.0 the utmp stuff got rewritten, IIRC by Ed Schouten. But with the > consequence that the API changed. And now it is no longer possible > * to open a file at init, > * keep it open while chrooting. > * write records when needed. > The interface is just completely different. > > Check: > man utempter_add_record > > If you want the old behaviour, you have to dig into the code, and DIY.
I understund, thanks. > > Bluntly put: I don't think anybody is going to fix YOUR problem. If only > because in 5 years time nobody had an issue with it. Now I see root of problem. I can choose what do: patch ftpd, do nothing or something else. _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
