Task #2959

tests for adding repos with fingerprints

Added by hans almost 4 years ago. Updated over 2 years ago.

Status:NewStart date:02/13/2014
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


write tests for adding repos, it should test things like:

  • add a repo with a fingerprint, then compare it to the actual key
  • add a repo that conflicts with an existing repo
  • add a repo with off-by-one fingerprints

These can be included in the Android Test Project in fdroidclient/test

Related issues

Related to Bazaar - Task #2896: write tests for F-Droid HTTPS chain verifier Closed 01/22/2014

Associated revisions

Revision 1018cad3
Added by Hans-Christoph Steiner over 3 years ago

Utils tests: formatFingerprint() and calcFingerprint(String)

Prevent another stupid bug like what is fixed by commit

refs #2959 https://dev.guardianproject.info/issues/2959

Revision 8395472f
Added by Hans-Christoph Steiner over 3 years ago

test index.jar signature checking

I got scared by seeing the Android docs' version of JarFile.getInputStream,
which didn't mention SecurityException or the signature checking. But it
seems that even tho its not in the Android docs, Android implements it the
same as Java does. It is good to have these tests in place anyhow, since
this is an essential piece of the security process of FDroid.

refs #2627 https://dev.guardianproject.info/issues/2627
refs #2959 https://dev.guardianproject.info/issues/2959


#1 Updated by hans over 3 years ago

  • Target version changed from improved security/usability to Integrate Kerplapp into FDroid

#2 Updated by hans over 3 years ago

  • Target version changed from Integrate Kerplapp into FDroid to 134

#3 Updated by hans over 2 years ago

  • Target version deleted (134)

Also available in: Atom PDF