Re: Including STRTOK_R in a LSM

2007-07-16 Thread Z. Cliffe Schreuders
Casey Schaufler wrote: --- "Z. Cliffe Schreuders" <[EMAIL PROTECTED]> wrote: What I need is to ignore double delimiters such as (::). This can be done trivially with a string comparison to check for "\0". What I want to know is if it is ok to include the strtok_r code in my security module

Re: Including STRTOK_R in a LSM

2007-07-16 Thread Casey Schaufler
--- "Z. Cliffe Schreuders" <[EMAIL PROTECTED]> wrote: > What I need is to ignore double delimiters such as (::). This can be > done trivially with a string comparison to check for "\0". What I want > to know is if it is ok to include the strtok_r code in my security > module, or if strtok was

Re: Including STRTOK_R in a LSM

2007-07-16 Thread Z. Cliffe Schreuders
What I need is to ignore double delimiters such as (::). This can be done trivially with a string comparison to check for "\0". What I want to know is if it is ok to include the strtok_r code in my security module, or if strtok was removed for a very good reason. I am porting a lot of existing

Re: Including STRTOK_R in a LSM

2007-07-16 Thread Jan Engelhardt
On Jul 16 2007 16:52, Z. Cliffe Schreuders wrote: > > I am aware strtok was removed from the kernel in 2002. However strtok_r is > more > desirable than strsep as I do not want to know about 'blank fields' (2 > consecutive delimiters). Is it acceptable to simply include the strtok_r code > in my

Including STRTOK_R in a LSM

2007-07-16 Thread Z. Cliffe Schreuders
I am aware strtok was removed from the kernel in 2002. However strtok_r is more desirable than strsep as I do not want to know about 'blank fields' (2 consecutive delimiters). Is it acceptable to simply include the strtok_r code in my security module? or should I create a wrapper for strsep to