Description of problem: No validation is performed on bind adress and accept range. Values are just written into postgre config, resulting in failure during postgre start. Version-Release number of selected component (if applicable): How reproducible: always/deterministic Steps to Reproduce: 1. install.pl --managed-db 2. when asked about network related stuff, just go ahead and type some nonsense there 3. continue in process as usual Actual results: Obviously wrong data is accepted and passed to config, starting postgre fails. Expected results: Data are re-requested in case they are obviously wrong. Additional info: Sanity checking should take into account both IPv4 and IPv6 addresses. Also bind-address might be checked against available interfaces...
commit 994dad50270bd3db8d4abee482b782a9a1e14696 Spacewalk
spacewalk.git 75b53687ee82bdbe09f0fbea32f8beead098b5b7
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state. The Satellite 5.7 GA Errata: - https://rhn.redhat.com/errata/RHSA-2015-0033.html Satellite 5.7 Release Notes: - https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html Satellite Customer Portal Blog announcement for release: - https://access.redhat.com/blogs/1169563/posts/1315743 Cliff