You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used System Informer to check the HTTPS commands sent by influxdb-client-csharp and found that the Token, which is sensitive information, was not promptly cleared from memory.
#642
Open
Shirley-Ji-59 opened this issue
Jun 20, 2024
· 1 comment
Thank you for using our client. As you’ve noted, the token is currently stored as a simple string within InfluxDB.Client.InfluxDBClientOptions.Token. Given that SecureString in .NET is deprecated and no longer recommended for new development, do you know better alternatives to enhance the security of sensitive data like tokens?
We are very much open to community contributions in this area. If you have ideas or are interested in developing a more secure method of handling tokens, we would be thrilled to review your proposal or pull request. Implementing a more secure storage mechanism could be an improvement to our client’s security posture.
If you’re interested, please feel free to submit your changes, and let us know if you need any specific information or guidance to get started.
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
Expected behavior:
the token sensitive information in memory is not visible.
Actual behavior:
the token sensitive information in memory is visible.
Specifications:
The text was updated successfully, but these errors were encountered: