Potential memory leak in sshd [detected by melton]

[Zhenbo Xu]

What about this report
http://lcs.ios.ac.cn/~xuzb/bugsfound/memleak/openssh-5.9p1/realbugs/sshd/report-uWzwb1.html#EndPath
?
At the end of the function server_accept_loop, fdset leaks. It means each
time the master sshd accept a new connection, it create a new space for
fdset but no free it. Or it is a false positive?

2012/2/4 Dan Kaminsky <dan at doxpara.com>

> ssh uses a unique process for each connection, and sshd forks for each new
> connection, so the only memory leaks that are "in scope" are those that
> apply to the master sshd.  I don't think that applies to any of these bugs.
>
> Melton looks rather cool though.
>
> On Fri, Feb 3, 2012 at 9:02 PM, Zhenbo Xu <zhenbo1987 at gmail.com> wrote:
>
>> By the way, I submitted this report in bugzilla a few days ago, but there
>> is no response.
>> Should I report bugs in this mailing list rather than in bugzilla?
>>
>> 2012/2/4 Zhenbo Xu <zhenbo1987 at gmail.com>
>>
>> > Hi all,
>> >
>> > After the memory leaks (bug 1967 <
>> https://bugzilla.mindrot.org/show_bug.cgi?id=1967>) I reported in
>> bugzilla are fixed,
>>
>> >
>> > I also applied melton(http://lcs.ios.ac.cn/~xuzb/melton.html)
>> >
>> > to detect the potential bugs in sshd (openssh-5.9p1).
>> >
>> >
>> > The url below is the index of bug reports that are checked as real bugs
>> manually.
>> >
>> >
>> http://lcs.ios.ac.cn/~xuzb/bugsfound/memleak/openssh-5.9p1/realbugs/sshd/index.html
>> >
>> >
>> > Shall we fix these bugs? Or just let them go since they are not so
>> serious?
>> >
>> > Hope for your replies!
>> >
>> >
>> > --
>> > Zhenbo Xu
>> >
>>
>>
>>
>> --
>> Zhenbo Xu
>> _______________________________________________
>> openssh-unix-dev mailing list
>> openssh-unix-dev at mindrot.org
>> https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
>>
>
>


-- 
Zhenbo Xu