#1839 [libimobiledevice] backport sha256 support for the libimobiledevice stack | rhbz#2357573
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2357573 **
Information from BlockerBugs App:
2357573

Current vote summary

Commented but haven't voted yet: dcavalca, lbrabec

The votes have been last counted at 2025-04-07 18:07 UTC and the last processed comment was #comment-964625

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


As said by dcavalca: This will allow users to connect and pair iOS devices without having to downgrade the crypto policies.

FinalFE +1

We've been shipping like this since F40, why can't this be a post release update?

FinalFE -1

We've been shipping like this since F40, why can't this be a post release update?

F40 was fine to be clear, the bug was introduced in F41. This could go in a post release update, but I figured it'd be good to have it fixed out of the box, as the failure mode is not obvious, and we probably don't want to encourage users to mess with the crypto policies.

I guess I can be:
FinalFE +1
as this is something I can see someone maybe doing from a live image.

Discussed during the 2025-04-07 blocker review meeting [1]:

  • AGREED: 2357573 - Accepted FreezeException - Connecting a mobile device to a Live image is a scenario that we can imagine, even though it might be rare. We're accepting this assuming the change is only related to the library in question and not affecting the rest of the OS.

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-04-07/f42-blocker-review.2025-04-07-16.01.log.html

AGREED AcceptedFinalFE

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F42 is no longer tracked by BlockerBugs, closing this ticket.

Log in to comment on this ticket.

Metadata