Current RDS Hash Sets

RDS Verion 2.74 - September 2021

NOTE: As of RDS 2.74, the NSRL has split the iOS RDS set into a modern and a legacy set. The regularly published iOS RDS set now contains hashes from iOS mobile applications downloaded and processed by the NSRL starting in July 2021. The legacy iOS RDS set contains hashes from iOS mobile applications dating back to 2016 and 2017. This set was not updated frequently, and contained hashes from mobile applications, not all collected directly by the NSRL. Moving forward, the modern iOS RDS set will contain hashes from iOS mobile applications collected and processed directly by the NSRL.

For legacy iOS mobile application hashes, please use the iOS hash set in RDS 2.73.1.

ISO 9660 images of RDS CDs

If you have a fast Internet connection, you may download ISO 9660 image files and burn your own copy of the RDS CDs.

Be aware that the ISO image files range between 500MB to nearly 4GB in size, and may take time to download.

NOTE: This current distribution of the RDS is being served from the amazon cloud. You may receive a notice that you are leaving the NSRL website.

• Current NSRL README.txt 
• Current RDS Hash Counts
• SHA-1 and Version details 
• Modern RDS (microcomputer applications from 2010 to present) 
• Modern RDS (minimal) 
• Modern RDS (unique) 
• Android RDS - Contains modern Android mobile applications. For older Android apps, use the previous Android RDS version 2.65
• iOS RDS - Contains modern iOS mobile applications. For older iOS apps, use the previous iOS RDS Version 2.73.1
• Legacy RDS (microcomputer applications from 2009 and earlier) 

The difference in the Modern sets are as follows:

1. Modern RDS (microcomputer applications) - contains the comprehensive set of ALL appearances of files in  modern applications; many file entries are duplicated
2. Modern RDS  (minimal) - contains the set of DISTINCT appearances of files in  modern applications; no file entries are duplicated
3. Modern RDS  (unique) - contains the set of file entries that appear ONLY ONCE  in the entire NSRL collection; these are unique to each off the applications that are in the collection

If a file exists with SHA1 value "024DD2A428CF0B450E461ED2A2EB6A1666CF392B" :

• Set #1 can list ALL of the applications that contain the file.
• Set #2 can list the fact that at least one application has that file.
• Set #3 can list the single application that file with which that file must be associated (to the limit that NSRL has encountered it).

The most common use is set #2.

If you are interested in earlier releases of the RDS contact us. 
 

Hash Converter Windows GUI tool

The MD5, SHA1 and SHA256 file signatures for these files are available here.

There is a Windows GUI tool HashConverter.zip that the NSRL is allowed to redistribute.

You can pick up the NSRL Perl conversion code at rds2hk.zip
When you unpack the zip file, there is one file, "rds2hk.pl".

enter:  perl rds2hk.pl -h
and you will get the help output:  Usage : rds2hk.pl [-h] -f format [-d RDS_directory] [-l logfile] [-p product_id] [-u]
-h : help with command line options
-f format : one of hk , 1.5 , 2.0 (MANDATORY)
-l logfile : print log info to a file
-d dir : directory holding NSRLProd.txt, NSRLFile.txt NSRLOS.txt and NSRLMfg.txt
-u : guarantee a unique product line in hk output
Enter the command:  perl rds2hk.pl -f hk -d SOME_DIR
and you'll get two files, "outfile.hke" and "outfile.hsh" that you can rename and pull into Hashkeeper.