Custom Query (1542 matches)

SanDisk SD7SN6S-(128|256|512)G-1006

OEM Version of the SanDisk X300: kb.sandisk.com/app/answers/detail/a_id/19208/~/sandisk-x300-ssd-firmware-update

Intel SSDSC2BB240G7

Links:

​http://www.intel.com/content/www/us/en/solid-state-drives/solid-state-drives-dc-s3520-series.html ​http://ark.intel.com/products/93012/Intel-SSD-DC-S3520-Series-240GB-2_5in-SATA-6Gbs-3D1-MLC

The update-smart-drivedb script does not authenticate the downloaded drivedb.h file. At least the smartmontools packages from Debian and Ubuntu do no longer provide this script due to security concerns (see ​Debian Bug 804299).

A check with GnuPG could be added as follows:

• Add missing drivedb branches for recent release (e.g. RELEASE_6_5_DRIVEDB) and for current trunk (RELEASE_6_6_DRIVEDB). Then the fallback to a download from trunk is no longer needed.

• Create a new signing key for drive database files.

• Add signature files drivedb.h.raw.asc to each maintained branch. These are generated from versions of drivedb.h with unexpanded SVN "$Id$" strings. No such file is needed for the trunk.

• Modify the update-smart-drivedb script such that it downloads drivedb.h and drivedb.h.raw.asc always from the correct branch and then verifies the signature with GPG. The public key could be kept in the script itself.

When changes to the trunk version of the database are later merged to all maintained branches, the signature files could be updated with the same commit. Only these commits will require access to the private key.