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

Event logs should have the name of the operator who initiated the action when applicable. #481

Open
MrStonedOne opened this issue Feb 19, 2018 · 1 comment
Open

Event logs should have the name of the operator who initiated the action when applicable. #481

MrStonedOne opened this issue Feb 19, 2018 · 1 comment
Labels
Client Issue with the .NET client library Feature Request Requested functionality Laid to Rest We honestly don't plan to fix this issue but it still represents an active problem with the software Priority: High Fix as soon as possible Security Issue pertaining to Authentication/Authorization or NTC (Never Trust the Client) V3 Things labelled with this probably won't be fixed ever in suite version 3

Comments

@MrStonedOne
Copy link
Member

In fact, a generic command issued event with this info might be the most appropriate.
@MrStonedOne MrStonedOne added Client Issue with the .NET client library Security Issue pertaining to Authentication/Authorization or NTC (Never Trust the Client) Priority: High Fix as soon as possible Feature Request Requested functionality labels Feb 19, 2018
@Cyberboss
Copy link
Member

Every set of actions a user takes is preceded by an audit entry in the logs saying "Access from X". Another one of these only pops up when a different user takes an action. I agree though, it should be attached directly to the individual logs.

@MrStonedOne MrStonedOne added this to the Bugs to fix before announcing tgs3 to the greater byond community milestone Jun 25, 2018
@Cyberboss Cyberboss added V3 Things labelled with this probably won't be fixed ever in suite version 3 and removed V3 Things labelled with this probably won't be fixed ever in suite version 3 labels Aug 29, 2018
@Cyberboss Cyberboss added the Backlog Issue to be scheduled for addressing label Sep 6, 2018
@Cyberboss Cyberboss removed their assignment Apr 28, 2020
@Cyberboss Cyberboss added Laid to Rest We honestly don't plan to fix this issue but it still represents an active problem with the software and removed Backlog Issue to be scheduled for addressing labels Jul 10, 2020
@Cyberboss Cyberboss removed this from the Bugs to fix before announcing tgs3 to the greater byond community milestone Oct 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Client Issue with the .NET client library Feature Request Requested functionality Laid to Rest We honestly don't plan to fix this issue but it still represents an active problem with the software Priority: High Fix as soon as possible Security Issue pertaining to Authentication/Authorization or NTC (Never Trust the Client) V3 Things labelled with this probably won't be fixed ever in suite version 3
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MrStonedOne @Cyberboss