Quoting Paul Moore ([email protected]): > Hello all, > > I'm polling the list to see what everyone thinks about a change in the > libseccomp API, moving away from keeping any internal state in the library > and > instead passing an opaque context pointer/handle created by seccomp_init()? > > Example: > > int rc; > scmp_handle_t hndl; > > hndl = seccomp_init(SCMP_ACT_KILL); > > rc = seccomp_rule_add(hndl, SCMP_ACT_ALLOW, SCMP_SYS(open), 0); > > rc = seccomp_load(hndl); > > Thoughts?
No objections from me. (Looking into the lxc container exploitation of libseccomp right now) -serge ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libseccomp-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libseccomp-discuss
