Current implementation of securefifo only works on posix-compilant FS-es and OS-es.
In order to ensure that no external process can open a temporary file storing the data, that temporary file, while still being open in the cinode process, is deleted on the filesystem thus it can not be accessed by filename by any external process.
On Windows systems however, there's no such option and a file opened by any process is protected against removal.
Current implementation assumes posix-compilant behavior and thus fails on Windows system.
To fix the issue, an alternative implementation that does not delete the file on Windows should be provided.
The original implementation for posix-compilant OS-es should remain unchanged though. The suggested approach would be to use os-specific implementations either through build tags or through filename suffixes.
Current implementation of securefifo only works on posix-compilant FS-es and OS-es.
In order to ensure that no external process can open a temporary file storing the data, that temporary file, while still being open in the cinode process, is deleted on the filesystem thus it can not be accessed by filename by any external process.
On Windows systems however, there's no such option and a file opened by any process is protected against removal.
Current implementation assumes posix-compilant behavior and thus fails on Windows system.
To fix the issue, an alternative implementation that does not delete the file on Windows should be provided.
The original implementation for posix-compilant OS-es should remain unchanged though. The suggested approach would be to use os-specific implementations either through build tags or through filename suffixes.