mirror of
				https://github.com/f-droid/fdroidserver.git
				synced 2025-11-03 22:20:28 +03:00 
			
		
		
		
	🔍 add scanner_signature_sources config option
				
					
				
			This adds the option to configure which set of signatures `fdroid scanner` should use, by configuring it in `config.yml`. It allows fetching signatures in our custom json format. It also adds 3 additional sources: 'suss', 'exodus', 'etip'
This commit is contained in:
		
							parent
							
								
									46d077292c
								
							
						
					
					
						commit
						24d88705fa
					
				
					 4 changed files with 102 additions and 17 deletions
				
			
		| 
						 | 
				
			
			@ -355,3 +355,19 @@
 | 
			
		|||
# lint_licenses:
 | 
			
		||||
#   - Custom-License-A
 | 
			
		||||
#   - Another-License
 | 
			
		||||
 | 
			
		||||
# `fdroid scanner` can scan for signatures from various sources. By default
 | 
			
		||||
# it's configured to only use F-Droids official SUSS collection. We have
 | 
			
		||||
# support for these special collections:
 | 
			
		||||
#  * 'exodus' - official exodus-privacy.org signatures
 | 
			
		||||
#  * 'etip' - exodus privacy investigation platfrom community contributed
 | 
			
		||||
#           signatures
 | 
			
		||||
#  * 'suss' - official F-Droid: Suspicious or Unwanted Software Signatures
 | 
			
		||||
# You can also configure scanner to use custom collections of signatures here.
 | 
			
		||||
# They have to follow the format specified in the SUSS readme.
 | 
			
		||||
# (https://gitlab.com/fdroid/fdroid-suss/#cache-file-data-format)
 | 
			
		||||
#
 | 
			
		||||
# scanner_signature_sources:
 | 
			
		||||
#   - suss
 | 
			
		||||
#   - exodus
 | 
			
		||||
#   - https://example.com/signatures.json
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue