Vault 7: Projects
This publication series is about specific projects related to the Vault 7 main publication.
STATUS_NO_SUCH_FILE.
The calling process must use BadMFS_WRITE as part of
the dwAccessFlags.
handle [out]
A handle created to keep track of the file opened/created by bmfsCreateFile.
This handle will
be used by any method which accesses the file.
Return Value
NTSTATUS will be returned to describe on success or failure.
If the method completes successfully the handle will contain a valid
BadMFS_HANDLE.
Remarks
The BadMFS version of bmfsCreateFile, unlike the Windows API version of
CreateFile, is specifically for the creation of files only. It cannot currently be
used for different types of I/O.
When an application is finished with the handle created by bmfsCreateFile it
is responsible for calling bmfsCloseHandle to clean up after itself. If this is
not done the handle will remain open, potentially blocking other I/O on that
file, until BadMFS is shutdown.
Directories are not currently supported, BadMFS has a flat file structure and
everything is within the “root directory”. This may be expanded upon at a
later date.
bmfsCloseHandle
Closes a specified file handle. Assists with keeping track of how many instances
have access to a handle for a unique file.
NTSTATUS bmfsCloseHandle( [in] BadMFS_HANDLE *handle );
Parameters
handle [in]
A handle to the file that was opened/created by bmfsCreateFile.
Return Value
If this function succeeds the NTSTATUS code STATUS_SUCCESS will be
returned.
Remarks
bmfsCloseHandle will attempt to clean up the file handle specified. This
includes decrementing
any read count associated with it, if there are multiple open handles to the
BadMFS_Developer_Guide.pdf