Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I am not big fan of running rake task in the RPM post section. First of all its slow, second it can fail if any of our ruby dependencies does not match version.
So I am adding this:
sed -i "s/^Src::Application.config.secret_token = '.*'/Src::Application.config.secret_token = '$(</dev/urandom tr -dc A-Za-z0-9 | head -c128)'/" config/initializers/secret_token.rb
It also generates BASE64-like string instead of simple hexa string. This is more secure.
1) I can confirm the string does not have to be hexa. It works with any
(base64 etc) encoded string.
2) Rake use Bundler and we were facing many issues with incorrect
dependencies (discussed on the ruby sig list). I tend not to use
Bundler-based things in the RPM postun sections, because even when deps
would be incorrect, I would like to have the RPM to be properly
installed. Therefore we generate the same using tr and sed tools.
http://git.fedorahosted.org/git/?p=katello.git;a=commitdiff;h=738bf1479390ba3d2df88ba24d43b9fbd118b160
It's also much faster.
3) Since the secret_token file is distributed, MD5 RPM validation fails.
I don't think this is an issue.
$ rpm -qV katello-common
5..T..... /usr/share/katello/config/initializers/secret_token.rb
738bf14 766939 - security_token.rb should be regenerated on each install