Red Hat Bugzilla – Bug 848205
brasero ignoring File/Image Checksum type
Last modified: 2015-09-08 16:16:24 EDT
Description of problem:
If I set the File Checksum or Image Checksum plugins in brasero to use something other than md5 (SHA1 and SHA256 are nominally supported), I see no evidence of anything other than md5 being used for anything.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch brasero
2. Edit -> Plugins
3. File Checksum, Configure -> Select SHA1
4. Image Checksum, Configure -> Select SHA1
5. Create a data project, and add any regular file to it.
6. Burn an image of the project.
7. Mount the resultant ISO.
1. A file /tmp/brasero_tmp_[six random characters].md5 is generated
2. The ISO has a .checksum.md5 file with the md5sum of the file that was included in the data project
I'd expect SHA1 to be used instead of md5.
SHA256 doesn't work, either.
It's possible I'm missing something here, and it's intentionally hardcoded to use md5 for these things and uses SHA1 somewhere else that I'm unaware of, in which case this bug should be closed, but from here, it looks like this setting is ignored.
Created attachment 665016 [details]
Silly patch that fixes the issue, but I don't like it.
Still reproducible in brasero-3.12.0-1.el7.
IT seems unlikely that we will get a fix for this unless it appears upstream.