Opened 15 years ago
Last modified 10 years ago
#285 new defect
IZ1849: Quote parser allows unmatched quotes
Reported by: | templedf | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | sge | Version: | 5.3 |
Severity: | Keywords: | clients | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=1849]
Issue #: 1849 Platform: All Reporter: templedf (templedf) Component: gridengine OS: All Subcomponent: clients Version: 5.3 CC: None defined Status: NEW Priority: P4 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: roland (roland) QA Contact: roland URL: * Summary: Quote parser allows unmatched quotes Status whiteboard: Attachments: Issue 1849 blocks: Votes for issue 1849: Opened: Wed Oct 26 10:11:00 -0700 2005 ------------------------ The string_list() routine, which is used to parse strings into lists for many of the qsub/qalter/et al utilities, does not complain about unmatched quotes. For example, the following is possible: % qalter -ac "'bob" 737 modified context of job 737 % qstat -j 737 | grep context context: 'bob and % qalter -ac \"bob 738 modified context of job 738 % qstat -j 738 | grep context context: "bob This issue is in the same bit of code as Issue 1762 and Issue 1555. Since this issue has not yet proven to be a problem for a customer, I'm setting it as a P4. ------- Additional comments from templedf Wed Oct 26 10:11:45 -0700 2005 ------- Changed the affected platform. ------- Additional comments from templedf Wed Oct 26 11:54:43 -0700 2005 ------- In the case of an unmatched quote, the behavior is as though the matching quote were placed at the end of the argument. For example: qsub -ac "test='1,2,3" -N \"bob sleeper.sh will set the value of test to '1,2,3 and the name to "bob, but from a functional perspective, that's ok. Running: qalter -dc test 123 will delete the full contents of test, as though the closing quote were present.
Note: See
TracTickets for help on using
tickets.