Bug 63359
Summary: | rhnreg_ks cryptedpassword does not function properly | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <joelmoses> |
Component: | rhn_register | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | gafton, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-02 21:33:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2002-04-12 22:19:08 UTC
Er, anyone out there on this one? This bug is holding up a few things on our side, and not knowing exactly what crypt method is accepted by RHN standards is keeping us from doing it ourselves. Just noticed that the "crypted" items have been removed from rhnreg_ks in 7.3 (seems to be commented out in the script). I'm assuming this is because this feature isn't ready within RHN yet? Or is it not going to be implemented? Yeah, it was never implemented. Were moving to a token/onetimepass type of mechanism for this in the future instead, so the options were removed in 7.3. Oo. I'd be curious as to how that would work with automated installations. I need to be able to make a kickstart file that force-registers a system that I've had to reload really quick via NFS. If it's a one-time-password situation, then I'd hope that the mechanism would still allow me to register the system using rhnreg_ks _without_ touching the kickstart file (our recovery process depends on that). If it's a token that I have to get from the RHN site FIRST, then that would be really difficult to manage. I was just hoping for crypted support so we don't leave our passwords in the clear in the kickstart file itself. |