Changes To Experiment: mmmv_silkexec
Not logged in

Changes to "Experiment: mmmv_silkexec" between 2017-01-07 17:29:02 and 2017-01-07 17:30:11

    34     34   they might use some component, software package, at some security wise
    35     35   extremely critical role, while being very rigorous at the construction of their
    36     36   software component.<br>
    37     37   </p>
    38     38   
    39     39   <p>Given that
    40     40   <a href="http://martin.softf1.com/g/yellow_soap_opera_blog/the-future-of-security-audits-episode-0">the
    41         -only proper way to verify/review code is a fully automated way</a>, there has
    42         -to be a way to subscribe to the testing/verification system of the trusted
    43         -parties. To avoid a Denial of Service attack by hacking into the
    44         -testing/verification systems of one of the trusted parties, the local settings
    45         -of the mmmv_silkexec should treat a test failure of a formerly accepted
    46         -component as a timed warning, where the warning state moves to a blocked/failed
    47         -state with a delay. The delay gives the trusted party time to handle the hack.</p>
           41  +only proper way to verify/review code is a fully automated way</a><i>(<a href="https://archive.is/h3HJ4">archival
           42  +copy</a>)</i>, there has to be a way to subscribe to the testing/verification
           43  +system of the trusted parties. To avoid a Denial of Service attack by hacking
           44  +into the testing/verification systems of one of the trusted parties, the local
           45  +settings of the mmmv_silkexec should treat a test failure of a formerly
           46  +accepted component as a timed warning, where the warning state moves to a
           47  +blocked/failed state with a delay. The delay gives the trusted party time to
           48  +handle the hack.</p>
    48     49   
    49     50   <p><br>
    50     51   </p>