Difference between revisions of "DPI908 Research Paper"
Chris Tyler (talk | contribs) (→DPI908 Research Paper Checklist) |
Chris Tyler (talk | contribs) (→General Overview of the Fedora Build and Release process) |
||
| Line 9: | Line 9: | ||
* Getting Program source files | * Getting Program source files | ||
| − | * Building locally from source using the | + | * Building locally from source using the rpmbuild system |
* Building locally using the mock built system | * Building locally using the mock built system | ||
| Line 18: | Line 18: | ||
* Software release process | * Software release process | ||
| + | ** rpm signing | ||
| + | ** rpm repository | ||
* Software update process | * Software update process | ||
| − | |||
| − | |||
== For each phase of the build and release processes == | == For each phase of the build and release processes == | ||
Latest revision as of 10:34, 27 November 2012
Contents
DPI908 Research Paper Checklist
For the 2012 Fall Semester, your research paper should investigate how Fedora secures its Build and Release system. The research paper should be about 20 pages long typed document and must include at least the following Sections:
General Overview of the Fedora Build and Release process
- Getting Program source files
- Building locally from source using the rpmbuild system
- Building locally using the mock built system
- Using the koji build system
- rpm package review process
- Software release process
- rpm signing
- rpm repository
- Software update process
For each phase of the build and release processes
- identify what security measures has been taken to safeguard the integrity of the software
- comment on the advantage/disadvantage/weakness of the security measure
Report on
- your findings
- your comments
- your recommendations
Conclusion
Summarize the overall security state of the Fedora Build and Release process, qualifying the risks you have identified to provide an overall risk assessment.
Citation
Cite all sources used in MLA style.
Submission
Please upload your research report in PDF format to Blackboard on or before your 0.3 release due date.
