I took a look at line 362 (http://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/view/head:/src/libecryptfs/cmd_ln_parser.c#L362) and line 371 (see http://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/view/head:/src/libecryptfs/cmd_ln_parser.c#L371). I have no clue about what kind of case we will run into this bug ("tok_str" is not terminating with "\0"). Can you give some extreme cases that may cause SEGFAULT. Thank you.
I took a look at line 362 (http:// bazaar. launchpad. net/~ecryptfs/ ecryptfs/ trunk/view/ head:/src/ libecryptfs/ cmd_ln_ parser. c#L362) and line 371 (see http:// bazaar. launchpad. net/~ecryptfs/ ecryptfs/ trunk/view/ head:/src/ libecryptfs/ cmd_ln_ parser. c#L371). I have no clue about what kind of case we will run into this bug ("tok_str" is not terminating with "\0"). Can you give some extreme cases that may cause SEGFAULT. Thank you.