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

Remove secret location from report when scanning confluence #33

Closed
cx-monicac opened this issue Mar 31, 2023 · 4 comments · Fixed by #58
Closed

Remove secret location from report when scanning confluence #33

cx-monicac opened this issue Mar 31, 2023 · 4 comments · Fixed by #58
Assignees

Comments

@cx-monicac
Copy link
Contributor

No description provided.

@cx-monicac cx-monicac self-assigned this Mar 31, 2023
@baruchiro
Copy link
Contributor

baruchiro commented May 1, 2023

The Location is the secret.StartColumn and secret.EndColumn, so it is related to the secret and not to Confluence.

But I agree, it gives no value, not for Confluence and not for Discord. Most of the time it is enough to get the page that contains the secret, and the secret itself.

@cx-monicac
Copy link
Contributor Author

cx-monicac commented May 2, 2023 via email

@baruchiro
Copy link
Contributor

@cx-monicac Sorry, for now, I removed the Location (#58), since it is not relevant for both Confluence and Discord.

We need to think about how to control the visibility of the location field, since when we calculate it, we are not in the context of any plugin, but in the context of the secrets, which is implemented generically for all the plugins.

@cx-monicac
Copy link
Contributor Author

cx-monicac commented May 2, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants