Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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):
brasero-3.4.1-1.el7.x86_64
How reproducible:
100%
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.
Actual results:
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
Expected results:
I'd expect SHA1 to be used instead of md5.
Additional info:
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.