...
| Wiki Markup |
|---|
A bunch of pages have screwed-up formatting, where some character, such as \[ (open-brace) is backslashed. This defeats its purposes of indicating a link. I've also seen this on open-braces. Someone needs to traverse the rules and clean these up. \-5/9 started cjohns (got as far as FIO05-A) |
FIO43-C. Do not copy data from an unbounded source to a fixed-length array and STR35-C. Do not copy data from an unbounded source to a fixed-length array are the same rule, what's the deal? -alexv
should we delete FIO43 and move something into its place (like FIO46)? it seems to me like the issue is mostly a string problem, and only a FIO issue because of i/o's heavy relience on strings... -alexv 5/14
sure looks like we should get rid of FIO43. It does appear to be almost identical to STR35-C except STR35-C seems to be fixed up a little more in some places. i recommend moving to the void, and then back filling with FIO43-C. Temporary files must be dealt with in a secure manner as you suggest.
will do - alexv 5/15
One further problem, a bunch of FIO rules are labeled "fio", meaning they show up on the cross reference for the FIO section. i think the solution is to remove the fio tags from any FIO rules. - rCs
my bad, will fix - alexv
...
The Risk Assessment Summary tables for each section need to be updated (they are out of date with the actual rules). - I got as far as EXP07, which still has the risk assessment for EXP10
i went through on 4/15 and checked to make sure the section tables matched the rules... are we confident that the risk summaries in the rules are correct? -alexv 4/17
- FLP02 is missing a risk assessmentDCL31 is missing a risk assessment
...