diff options
Diffstat (limited to 'detekt-baselines/autofill-parser.xml')
| -rw-r--r-- | detekt-baselines/autofill-parser.xml | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/detekt-baselines/autofill-parser.xml b/detekt-baselines/autofill-parser.xml index 80d2ae0f..a7726c93 100644 --- a/detekt-baselines/autofill-parser.xml +++ b/detekt-baselines/autofill-parser.xml @@ -24,7 +24,6 @@ <ID>MagicNumber:AutofillScenario.kt$AutofillScenario$26</ID> <ID>MagicNumber:AutofillScenario.kt$ClassifiedAutofillScenario$26</ID> <ID>MagicNumber:AutofillScenario.kt$GenericAutofillScenario$26</ID> - <ID>MagicNumber:AutofillStrategy.kt$26</ID> <ID>MagicNumber:AutofillStrategyDsl.kt$26</ID> <ID>MagicNumber:AutofillStrategyDsl.kt$AutofillRule$26</ID> <ID>MagicNumber:AutofillStrategyDsl.kt$AutofillStrategy$26</ID> @@ -34,8 +33,6 @@ <ID>MagicNumber:FeatureAndTrustDetection.kt$26</ID> <ID>MagicNumber:FeatureAndTrustDetection.kt$28</ID> <ID>MagicNumber:FormField.kt$FormField$26</ID> - <ID>MagicNumber:FormField.kt$FormField$6</ID> - <ID>MagicNumber:FormField.kt$FormField$8</ID> <ID>MagicNumber:FormField.kt$FormField.Companion$26</ID> <ID>MagicNumber:PublicSuffixListCache.kt$29</ID> <ID>MaxLineLength:FeatureAndTrustDetection.kt$/* In order to add a new browser, do the following: 1. Obtain the .apk from a trusted source. For example, download it from the Play Store on your phone and use adb pull to get it onto your computer. We will assume that it is called browser.apk. 2. Run aapt dump badging browser.apk | grep package: | grep -Eo " name='[a-zA-Z0-9_\.]*" | cut -c8- to obtain the package name (actually, the application ID) of the app in the .apk. 3. Run apksigner verify --print-certs browser.apk | grep "#1 certificate SHA-256" | grep -Eo "[a-f0-9]{64}" | tr -d '\n' | xxd -r -p | base64 to calculate the hash of browser.apk's first signing certificate. Note: This will only work if the apk has a single signing certificate. Apps with multiple signers are very rare, so there is probably no need to add them. Refer to computeCertificatesHash to learn how the hash would be computed in this case. 4. Verify the package name and the hash, for example by asking other people to repeat the steps above. 5. Add an entry with the browser apps's package name and the hash to TRUSTED_BROWSER_CERTIFICATE_HASH. 6. Optionally, try adding the browser's package name to BROWSERS_WITH_SAVE_SUPPORT and check whether a save request to Password Store is triggered when you submit a registration form. 7. Optionally, try adding the browser's package name to BROWSERS_WITH_MULTI_ORIGIN_SUPPORT and check whether it correctly distinguishes web origins even if iframes are present on the page. You can use https://fabianhenneke.github.io/Android-Password-Store/ as a test form. */</ID> @@ -48,6 +45,7 @@ <ID>ReturnCount:PublicSuffixListData.kt$PublicSuffixListData$private fun findExceptionMatch(labels: List<ByteArray>, wildcardMatch: String?): String?</ID> <ID>ReturnCount:PublicSuffixListData.kt$PublicSuffixListData$private fun findMatchingRule(domainLabels: List<String>): List<String></ID> <ID>TooGenericExceptionCaught:AutofillScenario.kt$AutofillScenario.Companion$e: Throwable</ID> + <ID>TopLevelPropertyNaming:PublicSuffixListLoader.kt$private const val PUBLIC_SUFFIX_LIST_FILE = "publicsuffixes"</ID> <ID>UnusedPrivateMember:AutofillStrategy.kt$private inline fun <T> Pair<T, T>.none(predicate: T.() -> Boolean)</ID> <ID>UnusedPrivateMember:FormField.kt$FormField$// Ignored for now, see excludedByHints private val excludedByAutocompleteHint = htmlAutocomplete == "off"</ID> </CurrentIssues> |