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.

Sign up for GitHub

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

Jump to bottom

investigate need and cost of logging potentially malicious behaviour as error or warning #4685

Open
jiceatscion opened this issue Jan 24, 2025 · 0 comments
Open

investigate need and cost of logging potentially malicious behaviour as error or warning #4685

jiceatscion opened this issue Jan 24, 2025 · 0 comments
Labels
i/needs investigation Issues/proposals that need to be confirmed/explored workitem Something needs doing

Comments

@jiceatscion
Copy link
Contributor

There was a conversation about that in #4683

It would be good to figure out how costly that may be, how the cost can be mitigated, and how desirable it may be to pay the price in order to make attacks and issues more visible.
@jiceatscion jiceatscion added i/needs investigation Issues/proposals that need to be confirmed/explored workitem Something needs doing labels Jan 24, 2025
@jiceatscion jiceatscion mentioned this issue Jan 24, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
i/needs investigation Issues/proposals that need to be confirmed/explored workitem Something needs doing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jiceatscion