Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Support securefifo on Windows #18

Open
byo opened this issue Dec 22, 2022 · 0 comments
Open

[Bug] Support securefifo on Windows #18

byo opened this issue Dec 22, 2022 · 0 comments

Comments

@byo
Copy link
Contributor

byo commented Dec 22, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant