| d0c7f6ea4f4c5bf9e1e21b67231e5b1a88020501 |
|
05-Feb-2013 |
Eric Paris <eparis@redhat.com> |
libsemanage: fcontext_record: do not leak on error in semanage_fcontext_key_create
If the strdup failed, we would return without freeing tmp_key. This is
obviously a memory leak. So free that if we are finished with it.
Signed-off-by: Eric Paris <eparis@redhat.com>
/external/selinux/libsemanage/src/fcontext_record.c
|
| c4f415c2444874488e9a9ae2e02a7cbeea583ba2 |
|
29-May-2012 |
Sven Vermeulen <sven.vermeulen@siphos.be> |
libsemanage: use after free in python bindings
In python 3.2 we hit a problem where the fconext was garbage. We didn't
see this in python 2.7. The reason is because python3.2 would free and
reuse the memory and python 2.7 just happened to leave it alone.
Instead of using memory that python might use for something else, use
strdup() to get a local copy which we can free when we are finished with
it.
Signed-off-by: Eric Paris <eparis@redhat.com>
Acked-by: Dan Walsh <dwalsh@redhat.com>
/external/selinux/libsemanage/src/fcontext_record.c
|
| 13cd4c8960688af11ad23b4c946149015c80d549 |
|
19-Aug-2008 |
Joshua Brindle <method@manicmethod.com> |
initial import from svn trunk revision 2950
/external/selinux/libsemanage/src/fcontext_record.c
|