Perhaps my wording was off. I didn't mean to imply that developers don't care about writing secure software or that security isn't in mind when developing but rather that if it comes down to implementing feature X or writing SELinux policy chances are feature X is going to be implemented first. Unless you have someone who's job it is to keep track of what is changing in your project and update your SELinux policy accordingly, your policy will be an afterthought. I'd be glad to be proved wrong on this but sadly based on what I've seen this seems to be the case.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds