Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The only reserved rule left is TMP31-C, which is awaiting decision from RCS. -pdc 5/1

TMP33-C and , MEM36-C are marked for deletion, and one of FIO43/STR35 should be deleted... so they would become "reserved" once deleted... - alevx 5/6 

...

  • integrate the concerns of TMP33-C. Temporary files must be removed before the program exits into TMP30-C. Temporary files must be created with unique and unpredictable file names by reiterating the need to clean up after temp files
    • done, but someone else should make sure they like the way I addressed this before deleting TMP33
    • then delete it as it is way redundant
  • Be clear that there is no good solution for cleaning up after abnormal termination other than using a /tmp directory, but then that violates TMP00-A. Do not create temporary files in shared directories
    • There is a trade-off here... use a shared directory and worry more about security, or use a private directory and worry about cleanup
  • We need more work on TMP00-A. Do not create temporary files in shared directories
    • Explain all the downsides to chroot jail (copying over DLLs, portability, how it is a HUGE mess, etc)
    • Demonstrate a good to way to create a private directory that is not as hard as a jail
    • Resolve the contradictions inherent between this rec and TMP33.. we say use }}{{{}{}{}{}{}{}{}{} tempnam in one, but say not to use }}{{{}{}{}{}{}{}{}{} tmpnam in another, moreover, our rule to use }}{{{}{}{}{}{}{}{}{} mkstemp or }}{{{}{}{}{}{}{}{}{} tmpfile_s contradicts TMP00 since neither guarantee a non-shared directory
      • use mkstemp and remember to clean up, then everyone is happy

...