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

282 - Fix Implicit Intent Vulnerability #283

Merged
merged 1 commit into from
Jun 14, 2022

Conversation

latin-panda
Copy link
Contributor

Description

This PR:

  • Adds package name to make intents explicit.

Ticket: #282

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

@latin-panda latin-panda requested a review from garethbowen June 9, 2022 08:25
@latin-panda
Copy link
Contributor Author

@garethbowen In theory, it should be enough by just setting the package name, the intent will only be accessible inside the package and fixes the concerns in the "vulnerability" criteria. I found another 2 intents that could be considered as implicit, I fixed those as well, I tested that they still work fine.

I couldn't find a lint option to catch this, so I opened a question in stackoverflow.

  1. Should this be ATed?
  2. Is this going to be released as production or beta in Play Store?
  3. Would this be a v1.0.1?
  4. Do we want to wait for this work and release everything together?

Thanks

@garethbowen
Copy link
Contributor

@latin-panda Have you managed to verify that this change still functions the way we expect? It was added as part of #163 so it should be possible to try and recreate the issue.

Should this be ATed?

Yes, to make sure it hasn't regressed.

Is this going to be released as production or beta in Play Store?

I think now that we have the production track going we should keep it going.

Would this be a v1.0.1?

I think that'd be good, yes. We've fixed a bug without changing functionality so a service pack bump is appropriate.

Do we want to wait for #281 and release everything together?

If they line up perfectly that's fine, but otherwise each should be released as soon as possible.

@latin-panda
Copy link
Contributor Author

latin-panda commented Jun 10, 2022

@garethbowen Yes, I've tested the areas that changed and they are working fine.
Once approved, I'll move the ticket to AT and notify QA for second pair of eyes, before starting the minor release.

@latin-panda latin-panda linked an issue Jun 10, 2022 that may be closed by this pull request
@latin-panda
Copy link
Contributor Author

latin-panda commented Jun 10, 2022

@garethbowen since this is a patch release, do we want to still make release notes and update CHANGELOG.md? Just like bigger release process

@garethbowen
Copy link
Contributor

@latin-panda Yes, it's best to update the changelog for every release.

Copy link
Contributor

@garethbowen garethbowen left a comment

Choose a reason for hiding this comment

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

Nice one!

@latin-panda latin-panda merged commit b879663 into master Jun 14, 2022
@latin-panda latin-panda deleted the 282-Fix_Implicit_Intent_Vulnerability branch June 14, 2022 02:24
njogz pushed a commit that referenced this pull request Jun 16, 2022
Ticket: #282

This commit:
- Adds package name to make intents explicit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix Implicit Intent Vulnerability
2 participants