https://bugs.kde.org/show_bug.cgi?id=473925
--- Comment #2 from gudvinr+...@gmail.com --- Hard coding for limited set of images is a terrible solution. It's not sustainable simply because maintainers can switch to other verification methods at any time. Also has zero scalability because each and every change requires to rebuild an app. I am suggesting opposite of trying to find any kind of pattern across distro images simply because verification process has nothing to do with ISO and doesn't care about content of the file. And FILE verification (as opposed to ISO verification) more often than not follows quite strict rule since utils that produce hashes have pretty standard output format (sha256sum, md5sum, etc). So, there's no need to guess and if file with given pattern exist then use it. If it doesn't then allow user to provide some sort of signature. -- You are receiving this mail because: You are watching all bug changes.
