"threat model"

Well, I understand that I should explicitly state what do I consider as a threat and what not but that in itself is to difficult for me now. Besides when I am asked if this code can be trusted, usually the person who asks this has even less understanding than I do. Which, you might guess, is really little.

So I go back thinking about the issue at hand.

I guess we have an advantage here that we have the source code so we don't necessarily need to check the behavior. We can check the source code.

In the code that raised the whole question one of the modules only contains some variables. most of the code is just looks like this:

# number of carnivores in the beginning $NUM_CARNIVORES = 30;
I am not a security expert but I think we can easily agree that such code in itself cannot be dangerous even though we are talking about carnivores here.

That means if I want to evaluate the code - regardless of my threat model or lack of it I can disregard those line when I am checking the source code.

OTOH if I see code like this:

use Carnivores;
that should immediately raise the red flag and tell me to look for the Carnivores.pm file to see what dangers might lurk in there.


In reply to Re^2: Is this code secure, can I test it on my machine? by szabgab
in thread Is this code secure, can I test it on my machine? by szabgab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.