Bug 1387869

Summary:	RFE: fake flash detection
Product:	[Fedora] Fedora	Reporter:	Chris Murphy <bugzilla>
Component:	mediawriter	Assignee:	Jan Grulich <jgrulich>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jgrulich
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Chris Murphy 2016-10-22 20:19:53 UTC

Description of problem:

There's a lot of fake flash out there. It'd be useful to incorporate the abbreviated test that GNOME Multiwriter is using.
https://blogs.gnome.org/hughsie/2015/01/28/detecting-fake-flash/

In terms of UI/UX, the options seem to be:

a. Always first do the test before writing the image.
b. Only do the test if image verification fails.
c. Offer the user a toggle to test the flash first.
d. Offer the user a separate feature to test the flash, decoupled from image writing.

I think maybe option b? That's the easiest to incorporate and requires UI only to present the user an explanation for the image verification failure: i.e. Image verification failed. This tool has determined the device's reported capacity is incorrect, i.e. it is likely counterfeit."

Comment 1 Martin Bříza 2016-10-24 09:48:40 UTC

Hello,

this is a good suggestion. However I don't think I'll have enough time to invest in implementing this in near future. So far, I think just having a media check after writing the image is enough. As it always goes with opensource, patches welcome!

If anybody steps up to implement this, I agree with you Chris that option B would probably be best. Option A doesn't seem bad either.