Very interesting

Aperta
#110 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
android, java

Direzione di ricerca

Start by running the reported info -signatures command with APKEditor 1.3.8 on both the original and modified APKs; the APK file itself is not attached. Compare the signature information and investigate why the original reports null despite installing, and why the modified APK fails verification. Done means the behavior is explained and the issue includes enough information to reproduce it.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

good first issue

Describe the bug
So I've been learning quite a bit about signatures the past few months and have barely scratched the surface it seems, so please bare with me. I've been trying to manipulate user installed apks that have the sharedUserId="android.uid.system" flag set. This one happens to have the sharedUserId="android.uid.shell". I'm mainly trying to get the debuggable flag set to true and preserve the signature. Obviously it uses the platform sig. It installs no problem on its own without anything done to it yet. In my experimentation one of my attempts was this: "apksigner sign --debuggable-apk-permitted --append-signature --ks platform.p12 --verbose LabelChecker_1.0.apk". The platform.p12 I use is another cert and private key that match the regular platform sig in quite a few areas, mainly these:

"X509v3 Subject Key Identifier:
93:2C:3A:F7:0B:62:7A:0C:76:10:B5:A0:E7:42:7D:6C:FA:EA:3F:1E
X509v3 Authority Key Identifier:
keyid:93:2C:3A:F7:0B:62:7A:0C:76:10:B5:A0:E7:42:7D:6C:FA:EA:3F:1E
DirName:/C=KR/ST=South Korea/L=Suwon City/O=Samsung Corporation/OU=DMC/CN=Samsung Cert/[email protected]
serial:D2:09:95:A7:9C:0D:AA:D6".

Except the private key doesn't match because of key rotation I believe. Anyways, after I use that first command I get this output using your tool:

"java -jar APKEditor-1.3.8.jar info -signatures -i downloads/LabelChecker_1.0.apk"

"Certificates="1"
Subject: [email protected], CN=Samsung Cert, OU=DMC, O=Samsung Corporation, L=Suwon City, ST=South Korea, C=KR
Issuer: [email protected], CN=Samsung Cert, OU=DMC, O=Samsung Corporation, L=Suwon City, ST=South Korea, C=KR
Validity FROM: Wed Jun 22 12:25:12 GMT 2011, TO: Sun Nov 07 12:25:12 GMT 2038, PERIOD: 864000000000
Serial: 0xd20995a79c0daad6
OID: 1.2.840.113549.1.1.5"

Looks great, but fails verification since it didn't preserve the original signature. Now with the same command on the original app that does install I get this output:

"java -jar APKEditor-1.3.8.jar info -signatures -i downloads/LabelChecker_1.0.apk"

"certificates="null""

It's pretty strange behavior and was hoping I might be able to get the reasons why the original apk isn't recognizing the signature at even even though it is signed and installs with no issues. I'll be available if you need anymore information at all. Thank you.

To Reproduce
Steps to reproduce the behavior:

  1. Use the apksigner command
  2. Check the signature using APKEditor
  3. Check the signature of the original unedited apk
  4. Output is "null"
  1. Used version '1.3.8'
  2. Operating system 'samsung s22 android 14'
  3. Command 'java -jar APKEditor-1.3.8.jar info -signatures -i "LabelChecker_1.0.apk"'

Log/Stacktrace
I'm not sure what logcat command I could use for this. Please provide an appropriate one and I'll give the output afterwards.

Used apk file
Github won't allow me to attach an apk.

Additional context
Add any other context about the problem here.

Lingua principale
Java
Stelle
2.3k
Fork
417
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di REAndroid/APKEditor

Tutte le issue di REAndroid/APKEditor

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.