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

Race condition in sensitive data masking #3440

Closed
droyad opened this issue Apr 24, 2017 · 2 comments
Closed

Race condition in sensitive data masking #3440

droyad opened this issue Apr 24, 2017 · 2 comments
Assignees
Milestone

Comments

@droyad
Copy link
Contributor

droyad commented Apr 24, 2017

A customer (private link) has encountered a race condition in the sensitive data masking area. The problem causes the process to crash due to an unhandled exception.

Sample stack trace:

at System.Collections.Generic.Queue`1+Enumerator[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Linq.Enumerable.Any[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<System.__Canon>)
at Octopus.Shared.Security.Masking.SensitiveDataMask.ProcessDeferred()
at Octopus.Shared.Diagnostics.LogContext.Flush()
at Octopus.Shared.Tasks.OctoThreadClosure`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Execute()
@droyad droyad self-assigned this Apr 24, 2017
@droyad droyad closed this as completed Apr 27, 2017
@octoreleasebot octoreleasebot added this to the 3.12.8 milestone Apr 27, 2017
@octoreleasebot
Copy link

Release Note: Fixed a race condition in sensitive variable masking that caused the process to crash

@lock
Copy link

lock bot commented Nov 24, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants