Bug 2054043
| Summary: | [RFE] No package provides /usr/bin/mkpasswd | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Mattias Ellert <mattias.ellert> |
| Component: | whois | Assignee: | Petr Menšík <pemensik> |
| Status: | CLOSED ERRATA | QA Contact: | Petr Sklenar <psklenar> |
| Severity: | high | Docs Contact: | Šárka Jana <sjanderk> |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | bstinson, jorton, jwboyer, ppisar, psklenar |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | whois-5.5.9-4.el9 | Doc Type: | Enhancement |
| Doc Text: |
.The password encryption function is now available in `whois`
The `whois` package now provides the `/usr/bin/mkpasswd` binary, which you can use to encrypt a password with the `crypt` C library interface.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-15 10:18:23 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2058423 | ||
| Deadline: | 2022-05-16 | ||
|
Description
Mattias Ellert
2022-02-14 05:27:44 UTC
Oh, indeed. mkpasswd were provided by expect in RHEL8, but it has renamed to mkpasswd-expect in later packages. However mkpasswd in whois is disabled on RHEL 8 and 9. It seems not required, because it only depends on libxcrypt library available also on RHEL9. It seems nothing blocks us from building also mkpasswd. Enabling it is just matter of enabling bcond whois_enables_mkpasswd for RHEL 9+. Then release engineering has to ensure it would end in correct repository. I would say AppStream is optimal target repository. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (whois bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:8079 |