Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Nov 2014 11:48:40 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 195128] Memory leaks in lib/libpam/modules due to memory handling with login_getcapstr, et al
Message-ID:  <bug-195128-8-qApSuVeprU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195128-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-195128-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195128

--- Comment #3 from darius@dons.net.au ---
The man page lies :(

login_getcapstr et al call cgetstr but don't track the allocation from it to
free later  from login_close.

Some of the things are freed (class, style, cap) but if you call
login_getcapstr, login _getcaptime, login_getcapnum or login_getcapsize there
is no tracking. There are also a few login_* functions which call
login_getcapstr and so will also leak.

I am working on a patch to track them and free later but it's pretty
prototypical at this stage.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-195128-8-qApSuVeprU>