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 1033334
Summary: | [RFE] Allow easy registration with SAM/Satellite through subscription manager | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Matt Reid <mreid> |
Component: | subscription-manager | Assignee: | candlepin-bugs |
Status: | CLOSED WONTFIX | QA Contact: | John Sefler <jsefler> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | CC: | alikins, bkearney, dgoodwin, khowell |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | 7.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-22 15:46:59 UTC | Type: | Bug |
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: | 1121117 |
Description
Matt Reid
2013-11-21 21:27:18 UTC
*** Bug 857269 has been marked as a duplicate of this bug. *** *** Bug 857271 has been marked as a duplicate of this bug. *** Acking 7.1 I would consider this a subset of "autodiscovery/autoconfiguration". The main gap is discovering where to ask for the information, and how to verify it can be trusted. I would like to add some support for auto discovering the sat6 server via DNS serv records, amahi/bonjour, or even just a predictable hostname ("sat6server" in local name resolving domain). That get's you pointing at the host and url, now you need to be able to trust it. A few potential: 1) As part of sat6 sync/manifests, provide some form of Red Hat signed version of this info (via an RPM seems straightforward.). Then we ship a gpg pub used by yum/rpm that can verify the rpm as being provided by us. It doesn't id it as being from precisely from that sat6 server, but it's much closer. 2) bootstrap trust chain from tpm of some sort Both of those involve a ton of trust/crypto/process however. bootstrap.py implements the spirit of this request. |