<HTML><BODY>
<BR>
<BR>
Thanks for the information Jan!<BR>
<BR>
On step number 2 below, I don’t see the option to create a branch. Does my account need permission to do so?<BR>
<BR>
Best regards,<BR>
<BR>
<BR>
Trey Henefield, CISSP<BR>
Senior IAVA Engineer<BR>
<BR>
Ultra Electronics<BR>
Advanced Tactical Systems, Inc.<BR>
4101 Smith School Road<BR>
Building IV, Suite 100<BR>
Austin, TX 78744 USA<BR>
<BR>
<a href="mailto:Trey.Henefield@ultra-ats.com">Trey.Henefield@ultra-ats.com</a><BR>
Tel: +1 512 327 6795 ext. 647<BR>
Fax: +1 512 327 8043<BR>
Mobile: +1 512 541 6450<BR>
<BR>
<a href="http://www.ultra-ats.com" target="_blank">www.ultra-ats.com</a><BR>
<BR>
-----Original Message-----<BR>
From: <a href="mailto:scap-security-guide-bounces@lists.fedorahosted.org">scap-security-guide-bounces@lists.fedorahosted.org</a> [mailto:scap-security-guide-bounces@lists.fedorahosted.org] On Behalf Of Jan Lieskovsky<BR>
Sent: Tuesday, December 09, 2014 3:30 PM<BR>
To: SCAP Security Guide<BR>
Subject: Re: SCAP Content Submission ...<BR>
<BR>
----- Original Message -----<BR>
> From: "Trey Henefield" <trey.henefield@ultra-ats.com><BR>
> To: "SCAP Security Guide" <scap-security-guide@lists.fedorahosted.org><BR>
> Sent: Tuesday, December 9, 2014 7:04:00 PM<BR>
> Subject: RE: SCAP Content Submission ...<BR>
> <BR>
> <BR>
> <BR>
> Thanks Jan!<BR>
> <BR>
> I have setup a github account today and am getting familiarized with <BR>
> the process. It is all new to me.<BR>
<BR>
Some basic info about the GH workflow:<BR>
[1] <a href="https://guides.github.com/introduction/flow/index.html" target="_blank">https://guides.github.com/introduction/flow/index.html</a><BR>
[2] <a href="http://scottchacon.com/2011/08/31/github-flow.html" target="_blank">http://scottchacon.com/2011/08/31/github-flow.html</a><BR>
<BR>
The GitHub help page might be helpful too:<BR>
[3] <a href="https://help.github.com/" target="_blank">https://help.github.com/</a><BR>
<BR>
> <BR>
> Is there some sort of reference you can point me to that describes the <BR>
> check-out check-in process?<BR>
> <BR>
> I have created a fork, pulled the fork locally, but can't figure out <BR>
> how to commit my changes back to my fork to generate a pull request.<BR>
<BR>
The simplified flow (once you have read [1], [2]) is as follows:<BR>
1) for the repository,<BR>
2) create a branch for the new feature (via browser):<BR>
<a href="https://github.com/blog/1377-create-and-delete-branches" target="_blank">https://github.com/blog/1377-create-and-delete-branches</a><BR>
<BR>
3) checkout that branch (assuming 'my_feature' is branch name)<BR>
<BR>
$ git clone -b my_feature git@github.com:your_GH_(user|nick)name_here/scap-security-guide.git<BR>
<BR>
4) make the changes & commit them:<BR>
<BR>
$ git add file*.txt<BR>
$ git commit<BR>
<BR>
5) find out the current status:<BR>
<BR>
$ git status<BR>
<BR>
6) once all changes committed, push the changes to the branch<BR>
<BR>
$ git push origin my_feature<BR>
<BR>
It's possible to see the settings by inspecting ".git/config" content<BR>
<BR>
7) return back to the browser & create a pull request:<BR>
<a href="https://help.github.com/articles/creating-a-pull-request/" target="_blank">https://help.github.com/articles/creating-a-pull-request/</a><BR>
<BR>
See how new PR entry is created / added here:<BR>
<a href="https://github.com/OpenSCAP/scap-security-guide/pulls" target="_blank">https://github.com/OpenSCAP/scap-security-guide/pulls</a><BR>
<BR>
& wait for it to be reviewed / accepted.<BR>
<BR>
Once that PR accepted & merged be sure to keep your fork synced with master repo (to be able to repeat the whole process from 1) - IOW to contribute other changes) =><BR>
a) configure a remote for a fork:<BR>
<a href="https://help.github.com/articles/configuring-a-remote-for-a-fork/" target="_blank">https://help.github.com/articles/configuring-a-remote-for-a-fork/</a><BR>
b) sync the fork:<BR>
<a href="https://help.github.com/articles/syncing-a-fork/" target="_blank">https://help.github.com/articles/syncing-a-fork/</a><BR>
<BR>
Hope this helps<BR>
<BR>
Thank you && Regards, Jan.<BR>
--<BR>
Jan iankko Lieskovsky / Red Hat Security Technologies Team <BR>
<BR>
> <BR>
> Best regards,<BR>
> <BR>
> <BR>
> Trey Henefield, CISSP<BR>
> Senior IAVA Engineer<BR>
> <BR>
> Ultra Electronics<BR>
> Advanced Tactical Systems, Inc.<BR>
> 4101 Smith School Road<BR>
> Building IV, Suite 100<BR>
> Austin, TX 78744 USA<BR>
> <BR>
> <a href="mailto:Trey.Henefield@ultra-ats.com">Trey.Henefield@ultra-ats.com</a><BR>
> Tel: +1 512 327 6795 ext. 647<BR>
> Fax: +1 512 327 8043<BR>
> Mobile: +1 512 541 6450<BR>
> <BR>
> <a href="http://www.ultra-ats.com" target="_blank">www.ultra-ats.com</a><BR>
> <BR>
> -----Original Message-----<BR>
> From: <a href="mailto:scap-security-guide-bounces@lists.fedorahosted.org">scap-security-guide-bounces@lists.fedorahosted.org</a><BR>
> [mailto:scap-security-guide-bounces@lists.fedorahosted.org] On Behalf <BR>
> Of Jan Lieskovsky<BR>
> Sent: Tuesday, December 09, 2014 11:53 AM<BR>
> To: SCAP Security Guide<BR>
> Subject: Re: SCAP Content Submission ...<BR>
> <BR>
> Hello Simon, Trey, folks,<BR>
> <BR>
> ----- Original Message -----<BR>
> > From: "Simon Lukasik" <isimluk@fedoraproject.org><BR>
> > To: "SCAP Security Guide" <BR>
> > <scap-security-guide@lists.fedorahosted.org><BR>
> > Sent: Tuesday, December 9, 2014 2:01:05 PM<BR>
> > Subject: Re: SCAP Content Submission ...<BR>
> > <BR>
> > Hello Trey,<BR>
> > <BR>
> > Thanks for sharing!<BR>
> > <BR>
> > There seems to be a lot of changes. However, it is rather tricky to <BR>
> > merge them to the main development branch. Usually contribution to <BR>
> > opensource project is made as a series of pull requests.<BR>
> <BR>
> Well, while this is definitely the way of SCAP content development we <BR>
> would like to follow, from time to time there are exceptions when it's <BR>
> worthy to step down from explicit requiring of following of this <BR>
> process / development model.<BR>
> <BR>
> > <BR>
> > Is there any chance that you would create git pull request for the <BR>
> > reposotory?<BR>
> <BR>
> We have been previously privately contacted by Trey regarding <BR>
> providing the contribution in the form of a zip tarball. Given the <BR>
> scope of the change (& enhancements it will bring to current SCAP <BR>
> Security Guide<BR>
> content,) we agreed to accept the contribution in this form & perform <BR>
> the PR creation on our own resources.<BR>
> <BR>
> This is definitely not a signal to the community that the patch <BR>
> proposal & management process should be moved to the mailing list <BR>
> again. But given (due to the scope of the contribution) the fact the <BR>
> Trey's change started to exits / started to be created in the moment <BR>
> SCAP Security Guide repository got moved to GitHub (IOW given there <BR>
> was some transition period of uncertainty which of the repository <BR>
> storage providers will SSG use at the end), we decided to accept the change for this time.<BR>
> <BR>
> Long story short, I have created issue ticket for this:<BR>
> [1] <a href="https://github.com/OpenSCAP/scap-security-guide/issues/347" target="_blank">https://github.com/OpenSCAP/scap-security-guide/issues/347</a><BR>
> <BR>
> & unless someone beats me to it, will get to it within this week.<BR>
> <BR>
> Thank you && Regards, Jan.<BR>
> --<BR>
> Jan iankko Lieskovsky / Red Hat Security Technologies Team<BR>
> <BR>
> > <BR>
> > Thanks,<BR>
> > ~Š.<BR>
> > <BR>
> > On 12/04/2014 06:45 PM, Trey Henefield wrote:<BR>
> > > <BR>
> > > <BR>
> > > Greetings,<BR>
> > > <BR>
> > > I have some content I would like to contribute to the SSG community.<BR>
> > > <BR>
> > > The content is attached in a zip file and should be extracted <BR>
> > > directly into the repo.<BR>
> > > <BR>
> > > The summary of these changes are as follows:<BR>
> > > <BR>
> > > -New content has been included to address DISA STIGs for:<BR>
> > > <BR>
> > > oFirefox<BR>
> > > <BR>
> > > oJava<BR>
> > > <BR>
> > > oRed Hat 5 (This content addresses the Red Hat 5 STIG requirements <BR>
> > > for Red Hat 5, Red Hat 4, CentOS 5, and CentOS 4)<BR>
> > > <BR>
> > > oWebmin<BR>
> > > <BR>
> > > -Modified shared/transforms/combinechecks.py to include an actual <BR>
> > > timestamp in the oval content when it gets created.<BR>
> > > <BR>
> > > -Added shared/transforms/stats.sh to display statistics when <BR>
> > > building content. The statistics identify the total number of <BR>
> > > requirements, as indicated in the stig_overlay.xml document for <BR>
> > > each STIG, the number of checks addressed by STIG requirements, <BR>
> > > and the number of fixes addressed by each STIG requirement. In <BR>
> > > addition, it also pulls in the DISA STIG information from the <BR>
> > > references folder (e.g. RHEL/5/references) and compares it with <BR>
> > > the STIG requirements in the stig_overlay.xml to support <BR>
> > > identifying differences (i.e. STIG requirements removed or added).<BR>
> > > <BR>
> > > -Added shared/transforms/stig_refs.sh to support pulling <BR>
> > > information (CCI, CCE, Severity, SVkey, SVrelease, IA controls, <BR>
> > > and title) from the DISA STIG and automatically populating that <BR>
> > > information into the SCAP content for consistency. There could <BR>
> > > probably be a better way to script this capability, but given the <BR>
> > > large number a requirements in the RHEL5 STIG, it was a great <BR>
> > > help. This capability is not called at build time, but on an as <BR>
> > > needed basis. When executed, it should be called from within the SCAP content directory (e.g.<BR>
> > > RHEL/5) and also requires the DISA STIG XCCDF file to be available <BR>
> > > in the references folder of the SCAP content directory (e.g.<BR>
> > > RHEL/5/references). Example: `cd RHEL/5; <BR>
> > > ../../shared/transforms/stig_refs.sh`<BR>
> > > <BR>
> > > Happy SCAPing!<BR>
> > > <BR>
> > > Best regards,<BR>
> > > <BR>
> > > Trey Henefield, CISSP<BR>
> > > <BR>
> > > Senior IAVA Engineer<BR>
> > > <BR>
> > > Ultra Electronics<BR>
> > > <BR>
> > > Advanced Tactical Systems, Inc.<BR>
> > > <BR>
> > > 4101 Smith School Road<BR>
> > > <BR>
> > > Building IV, Suite 100<BR>
> > > <BR>
> > > Austin, TX 78744 USA<BR>
> > > <BR>
> > > <a href="mailto:Trey.Henefield@ultra-ats.com">Trey.Henefield@ultra-ats.com</a><BR>
> > > <BR>
> > > Tel: +1 512 327 6795 ext. 647<BR>
> > > <BR>
> > > Fax: +1 512 327 8043<BR>
> > > <BR>
> > > Mobile: +1 512 541 6450<BR>
> > > <BR>
> > > <a href="http://www.ultra-ats.com" target="_blank">www.ultra-ats.com</a><BR>
> > > <BR>
> > > <BR>
> > <BR>
> > <BR>
> > --<BR>
> > Simon Lukasik<BR>
> > Security Technologies, Red Hat, Inc.<BR>
> > --<BR>
> > SCAP Security Guide mailing list<BR>
> > <a href="mailto:scap-security-guide@lists.fedorahosted.org">scap-security-guide@lists.fedorahosted.org</a><BR>
> > <a href="https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide</a><BR>
> > <a href="https://github.com/OpenSCAP/scap-security-guide/" target="_blank">https://github.com/OpenSCAP/scap-security-guide/</a><BR>
> --<BR>
> SCAP Security Guide mailing list<BR>
> <a href="mailto:scap-security-guide@lists.fedorahosted.org">scap-security-guide@lists.fedorahosted.org</a><BR>
> <a href="https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide</a><BR>
> <a href="https://github.com/OpenSCAP/scap-security-guide/" target="_blank">https://github.com/OpenSCAP/scap-security-guide/</a><BR>
> <BR>
> <BR>
> <BR>
> <BR>
> Disclaimer<BR>
> The information contained in this communication from <BR>
> <a href="mailto:trey.henefield@ultra-ats.com">trey.henefield@ultra-ats.com</a> sent at 2014-12-09 13:04:07 is private<BR>
> and may be legally privileged or export controlled. It is intended <BR>
> solely for use by <a href="mailto:scap-security-guide@lists.fedorahosted.org">scap-security-guide@lists.fedorahosted.org</a> and<BR>
> others authorized to receive it. If you are not <BR>
> <a href="mailto:scap-security-guide@lists.fedorahosted.org">scap-security-guide@lists.fedorahosted.org</a> you are hereby notified<BR>
> that any disclosure, copying, distribution or taking action in <BR>
> reliance of the contents of this information is strictly prohibited and may be unlawful.<BR>
> <BR>
> <BR>
> --<BR>
> SCAP Security Guide mailing list<BR>
> <a href="mailto:scap-security-guide@lists.fedorahosted.org">scap-security-guide@lists.fedorahosted.org</a><BR>
> <a href="https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide</a><BR>
> <a href="https://github.com/OpenSCAP/scap-security-guide/" target="_blank">https://github.com/OpenSCAP/scap-security-guide/</a><BR>
--<BR>
SCAP Security Guide mailing list<BR>
<a href="mailto:scap-security-guide@lists.fedorahosted.org">scap-security-guide@lists.fedorahosted.org</a><BR>
<a href="https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide</a><BR>
<a href="https://github.com/OpenSCAP/scap-security-guide/" target="_blank">https://github.com/OpenSCAP/scap-security-guide/</a><BR>
<BR>
<BR>
<p><font size="1"><b><font color="#666666" face="Verdana, Arial, Helvetica, sans-serif">Disclaimer</font></b><font color="#666666" face="Verdana, Arial, Helvetica, sans-serif"><br/>
The information contained in this communication from </font></font><font color="#666666" size="1" face="Verdana, Arial, Helvetica, sans-serif"><b>
trey.henefield@ultra-ats.com
</b> sent at
2014-12-10
08:45:58
is private and may be legally privileged or export controlled. It is intended solely for
use by <b>
scap-security-guide@lists.fedorahosted.org
</b> and others
authorized to receive it. If you are not <b>
scap-security-guide@lists.fedorahosted.org
</b> you are hereby notified that any disclosure, copying, distribution or
taking action in reliance of the contents of this information is strictly
prohibited and may be unlawful.</font><br>
<br>
</BODY></HTML>