Skip to content
This repository has been archived by the owner on Mar 22, 2021. It is now read-only.

Consider supporting RHEL? #35

Open
jlebon opened this issue Apr 27, 2017 · 2 comments
Open

Consider supporting RHEL? #35

jlebon opened this issue Apr 27, 2017 · 2 comments

Comments

@jlebon
Copy link
Collaborator

jlebon commented Apr 27, 2017

Right now, there's no support for provisioning RHEL-based hosts/containers and registering them. By its very nature, redhat-ci is more targeted at upstream work, which usually means Fedora/CentOS anyway. Though there could be use cases for provisioning RHEL userspaces too.

I've been avoiding this because I didn't want to deal with the risk factor of leaking subscription data, though there might be safe ways to do this, e.g. creating temporary stage accounts that last the duration of the test run.

@cevich
Copy link
Contributor

cevich commented Apr 27, 2017

leaking subscription data

Perhaps the duration of the subscription only lasts until build/test commands start. In other words, package install is permitted, but then the system is unsubscribed and unregistered. Then the only place it's possible to run commands (that could expose the subscription or host certs) is from a script embedded in an RPM. However, those certs. would soon be invalidated when the packaging section ended (or there was an error or timeout).

Otherwise, the only thing you need to protect is any logs of the 'subscription-manager' command itself. That's easily done by feeding it's --username, --password, and --org parameters with values from short-lived files or env. vars. Then, to be safe, kill root's .bash_history (from a separate shell).

I think there's even a subscription-manager "reset" option that will wipe out all traces of the system's cert. Combine all that with your short-lived credentials idea, and there's multiple-layers of protection against leaks.

@cevich
Copy link
Contributor

cevich commented May 30, 2017

Saw a demo that made me think this issue is solved, no?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants