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

fixed jirav1 detector email pattern #3826

Merged

Conversation

kashifkhan0771
Copy link
Contributor

Description:

This PR fixes the github issue #3818

Checklist:

  • Tests passing (make test-community)?
  • Lint passing (make lint this requires golangci-lint)?

@kashifkhan0771 kashifkhan0771 requested a review from a team as a code owner December 31, 2024 12:50
@kashifkhan0771 kashifkhan0771 linked an issue Dec 31, 2024 that may be closed by this pull request
@@ -16,7 +16,7 @@ var (
invalidTokenPattern = "Z7VoI?J0K4rF#LBfkhO&LAWX"
validDomainPattern = "hereisavalidsubdomain.heresalongdomain.com"
invalidDomainPattern = "?y4r3fs1ewqec12v1e3tl.5Hcsrcehic89saXd.ro@"
validEmailPattern = "[email protected]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kashifkhan0771 Not sure but the old input is also valid email and should pass the user case.

Copy link
Contributor Author

@kashifkhan0771 kashifkhan0771 Jan 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our common email pattern is not configured to capture capital letters. I guess we need a small enhancement in the common email pattern. Including flag (?i) in start will work.
Thoughts @abmussani @zricethezav @ahrav ?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh wow, I didn't realize the common email pattern regex was case sensitive. I think making it insensitive is the right approach. 👍

@kashifkhan0771 kashifkhan0771 self-assigned this Jan 10, 2025
@zricethezav zricethezav merged commit 71b341c into trufflesecurity:main Jan 13, 2025
13 checks passed
@rgmz rgmz mentioned this pull request Jan 13, 2025
@kashifkhan0771 kashifkhan0771 deleted the fix/github-issue-3818 branch January 14, 2025 05:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

JiraToken v1 detector is subtly broken
4 participants