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

Explain how you need to protect the signing key for releasing an app #971

Closed
commjoen opened this issue Aug 14, 2018 · 5 comments
Closed
Assignees
Labels
close? Issue can potentially be closed according to the new approach. MASVS-CODE

Comments

@commjoen
Copy link
Collaborator

Given the update in 1.1.1 of the MASVS (regarding control 7.1), we need to extend our coverage on the MSTG if it comes to securing the signing key.

Methods could include, but should not be limited to:

@commjoen commjoen added this to the 1.1 Release milestone Aug 14, 2018
@cldrn
Copy link
Collaborator

cldrn commented Jun 6, 2019

Where would this sections be? I think we should definitely mention the new App Signing method hosted/managed by Google (https://support.google.com/googleplay/android-developer/answer/7384423?hl=en-GB).

@commjoen
Copy link
Collaborator Author

commjoen commented Jun 6, 2019

we should! 0x5a and 0x6a

@commjoen
Copy link
Collaborator Author

@cldrn : do you have any updates on this?

@cpholguera
Copy link
Collaborator

Hola Paulino, any news on this one? :) Thanks!

@cldrn
Copy link
Collaborator

cldrn commented Dec 17, 2019

Hi guys,

Wrapping up Q4 on the 19th and then I will be free to work on this one, the one for disabling keyboard cache in kotlin and updating the checklist in Spanish.

:)

@cpholguera cpholguera added the close? Issue can potentially be closed according to the new approach. label Oct 16, 2022
@cpholguera cpholguera closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
close? Issue can potentially be closed according to the new approach. MASVS-CODE
Projects
None yet
Development

No branches or pull requests

5 participants