mirror of
https://pagure.io/fedora-kickstarts.git
synced 2025-02-07 12:17:19 +00:00
6ba647a663
Best practice is to use unprivileged service daemons inside Docker containers. But with this hardcoded root password, in the case of remote code execution, an attacker could trivially escalate their privileges to root/uid 0. And while that's uid 0 inside a container, that's a much larger attack surface. Instead, do the same thing we're doing for the Cloud images: lock the root password, create a user to make Anaconda happy, then delete the user in %post. https://bugzilla.redhat.com/show_bug.cgi?id=1175997
The master branch is where development takes place: - it may contain kickstart files that are broken, or - spin concepts that are in the process of being approved by the Board (trademark approval), or - spin concepts that are in the process of being approved by the Spins SIG The release specific branches contain spin concepts that: - are approved (both by Board and Spin SIG) - maintained for the remainder of the release cycle git clone ssh://git.fedorahosted.org/git/spin-kickstarts.git spin-kickstarts cd spin-kickstarts # If you need a specific branch other than master: git checkout BRANCHNAME # No tag has been added yet tag HEAD with git tag VERSION git push --tags make # Publish the released tar ball make publish # Clean up the generated files: make clean