-
Notifications
You must be signed in to change notification settings - Fork 125
Support for Encrypting Log Files #71
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
Comments
There is some discussion on compression in #48, which very much relates to file encryption. Like compression, there are 2 approaches to encrypting files:
For encryption, you would generally want the 1st option, to ensure the plaintext was never written to disk in the first place. I have a fork that allows wrapping the output stream here. The use case being demonstrated was compression, but I had encryption in mind too - the point is that wrapping the output stream is an extensible approach that allows for a variety of use cases. |
Note this may be covered by #80. |
I think we should close this as "optimistically, enabled by #80", which is now on NuGet in the -dev preview package. If it turns out the file lifecycle hooks we currently support are inadequate, we can open a new ticket and follow on from there. Let us know if you take a shot at this, @DenisDolgunov - happy to help with the details. |
@DenisDolgunov now #80 is in
|
If have some plans to add encrypting files in the project, what's best practice for do it?
The text was updated successfully, but these errors were encountered: