cacert/cacert-policies
9
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

recommend 7.3 be blank, refer to SM

Browse source 
git-svn-id: http://svn.cacert.org/CAcert/Policies@1892 14b1bab8-4ef6-0310-b690-991c95c89dfd
This commit is contained in:
Ian Grigg 2010-05-03 02:05:34 +00:00
parent 2c407bc68b
commit 18b68bd6aa
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
SecurityPolicy.html
View file

@ -952,7 +952,9 @@ The primary tasks for Application Engineers are:
<h3 id="s7.3"> 7.3. Repository </h3>
<p>
<p class="q"> As we are still unsure how to do Repository, I recommend we make this section blank. Therefore, it is handled in Security Manual. <i>Iang, 20100502</i>.</p>
<p class="strike">
The application code and patches are maintained
in a central repository that is run by the
software assessment team.
@ -960,18 +962,16 @@ software assessment team.
<ul class="q">
<li> is this something that can be and is being run by Systems Administration team? </li>
<li> Or are their two, the test one and the critical one? </li>
<li> Like this: </li>
<li> Alternative, also struck: </li>
</ul>
<p class="change">
<p class="strike">
The development code and testing patches are maintained
in a central development repository that is run by the
software assessment team.
</p>
<p class="change">
<p class="strike">
The production code is maintained in a secure production repository
within the critical systems that is run by the
Systems Administation team.