Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1976334 (yescrypt_accountsservice) - Needs patch to support yescrypt hash method
Summary: Needs patch to support yescrypt hash method
Keywords:
Status: CLOSED ERRATA
Alias: yescrypt_accountsservice
Product: Fedora
Classification: Fedora
Component: accountsservice
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: yescrypt_shadow
TreeView+ depends on / blocked
 
Reported: 2021-06-25 19:21 UTC by Björn 'besser82' Esser
Modified: 2021-06-27 21:37 UTC (History)
4 users (show)

Fixed In Version: accountsservice-0.6.55-7.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-27 21:37:11 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Björn 'besser82' Esser 2021-06-25 19:21:51 UTC 
Description of problem:

  accountsservice needs patch to support yescrypt hash method.


Version-Release number of selected component (if applicable):

  any


How reproducible:

  100%


Additional info:

  upstream PR:   https://gitlab.freedesktop.org/accountsservice/accountsservice/-/merge_requests/74
  downstream PR: https://src.fedoraproject.org/rpms/accountsservice/pull-request/4

  This bug is for tracking purposes.
Comment 1 Fedora Update System 2021-06-27 21:34:32 UTC 
FEDORA-2021-2891ddb4ba has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2891ddb4ba
Comment 2 Fedora Update System 2021-06-27 21:37:11 UTC 
FEDORA-2021-2891ddb4ba has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.