From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: [SEMANAGE(tool)] Fix many issues
Date: Sat, 14 Jan 2006 00:02:23 -0700 [thread overview]
Message-ID: <43C8A1FF.8090605@cornell.edu> (raw)
In-Reply-To: <43C89A43.3020105@cornell.edu>
>
> Further notes:
> - Multiple roles don't seem to work - I get the usage() printout
> - Modifying with -R doesn't work properly - it adds roles on top of
> the current ones, when it should clear the current role set first -
> you can use the del_role function, or better, the set_roles function
> (not sure if it will work, let joshua know if the swig typemaps create
> problems for that case).
> - I would recommend a message be printed out after a delete() that
> leaves a policy object behind (do exists check again), that says:
> "Deleted local modifications to <object>, falling back to policy
> default". This describes what the delete function really does in that
> case.
Another thing - I am still not clear on memory management vs python.
I don't see a single thing being freed in the python semanage - is that
a problem? Valgrind certainly prints a full 10 screens of errors that
complain about uninitialized value and invalid read on PyObject_Free,
but I'm not sure I understand what's going on.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-01-14 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 6:29 [SEMANAGE(tool)] Fix many issues Ivan Gyurdiev
2006-01-14 7:02 ` Ivan Gyurdiev [this message]
2006-01-14 7:41 ` Ivan Gyurdiev
2006-01-14 7:44 ` Ivan Gyurdiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C8A1FF.8090605@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.