Bug 1464899

Summary:	url to disa srgs dead
Product:	Red Hat Enterprise Linux 7	Reporter:	Marek Haicman <mhaicman>
Component:	scap-security-guide	Assignee:	Watson Yuuma Sato <wsato>
Status:	CLOSED ERRATA	QA Contact:	Marek Haicman <mhaicman>
Severity:	medium	Docs Contact:	Ioanna Gkioka <igkioka>
Priority:	medium
Version:	7.4	CC:	lmiksik, mhaicman, mpreisle, openscap-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	scap-security-guide-0.1.36-1.el7	Doc Type:	Known Issue
Doc Text:	URL to DISA SRGs is incorrect The SCAP Security Guide (SSG) rules refer to Defense Information Systems Agency Security Requirement Guides (DISA SRGs). Connecting to the URL fails with an 404 - not found error. As a consequence, users have no direct reference to SRGs. To work around the problem, use the new URL: http://iase.disa.mil/stig/os/general/Pages/index.aspx/	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 12:20:33 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:

Description Marek Haicman 2017-06-26 08:29:36 UTC

Description of problem:
SCAP Security Guide refers to DISA SRG in the rules. The link is dead, though

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.33-5.el7.noarch

How reproducible:
reliably

Steps to Reproduce:
1. open guide with USGCB profile, or results.html of the same
2. try to click SRG reference in one of the rules
3.

Actual results:
404

Expected results:
Relevant page is opened

Additional info:

Comment 1 Watson Yuuma Sato 2017-11-13 14:48:48 UTC

This is the upstream patch: https://github.com/OpenSCAP/scap-security-guide/pull/2345

Comment 4 Marek Haicman 2018-01-05 21:36:47 UTC

Verified no disa links referenced in the shipped datastreams of version scap-security-guide-0.1.36-6.el7.noarch are dead.

Comment 7 errata-xmlrpc 2018-04-10 12:20:33 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0761