On 2011-01-24 at 17:34 -0500, Luke S Crawford wrote: > Right, but it sounds like the hole was quite possibly in the closed-source > binaries they are running. a re-install, without fixing the hole, will > just result in a new compromise. it seems to me like the owner of > those closed-source binaries needs to be involved in that, to me.
This is the point at which swallowing the pain of dealing with SELinux might become worthwhile -- if you can track what access those binaries ever normally need and can get confirmation that's all they need, then you can lock it down so that the app can't, eg, make outbound network connections, right? -Phil _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
