[pdf-devel] Filesystem module and temporary files.

[jemarch]

   Hi.

   I made a change in the filesystem module that modifies its public
   API.  The filesystem function pdf_fsys_get_temp_path_name
   introduces a security hole, since no one guarantees that a
   filesystem item with the returned name is not created by other
   application.

   So I removed pdf_fsys_get_temp_path_name and introduced a new function
   pdf_fsys_file_open_tmp:

    -- Function: pdf_status_t pdf_fsys_file_open_tmp (const pdf_fsys_t
          FILESYSTEM, pdf_fsys_file_t *FILE)
     Create a temporary file in FILESYSTEM and open it.

     The temporary file is opened with mode PDF_FSYS_OPEN_MODE_RW and stored
     in FILE.  The file will be automatically deleted when it is closed.  The
     filesystem implementation may also delete the file when the client
     application exits, but it is not guaranteed.
     

    *Parameters*

         FILESYSTEM
               A filesystem. If `NULL' the default filesystem is used.

         FILE
               The output file variable.

    *Returns*
          A PDF status value:
         `PDF_OK'
               The file was successfully opened and stored in the FILE
               variable.  If the filesystem implementation does not support
               this functionality then NULL is stored in FILE.

         `PDF_ENOMEM'
               Not enough memory.

         `PDF_ERROR'
               It was not possible to create the temporary file.

   I updated the documentation and the disk filesystem implementation.

   I also imported the stdio-safer related functions from gnulib and used them
   in the disk filesystem, along with a general gnulib update.

-- 
Jose E. Marchesi  <address@hidden>
                  http://www.jemarch.net
GNU Project       http://www.gnu.org