[SC-L] How Can You Tell It Is Written Securely?

[Stephen Craig Evans]

"... and demand that they deliver code that is so locked down that it
cannot misbehave".

Your premise is so incorrect that I advise that if you are truly
interested in answering your questions (as opposed to a purely
academic or other exercise), then you should hire a security
specialist to help you out, or use google search :-)

Cheers,
Stephen

On Thu, Nov 27, 2008 at 10:03 AM, Mark Rockman <mrockman at acm.org> wrote:
> OK.  So you decide to outsource your programming assignment to Asia and
> demand that they deliver code that is so locked down that it cannot
> misbehave.  How can you tell that what they deliver is truly locked down?
> Will you wait until it gets hacked?  What simple yet thorough inspection
> process is there that'll do the job?  Doesn't exist, does it?
>
>
> MARK ROCKMAN
> MDRSESCO LLC
> _______________________________________________
> Secure Coding mailing list (SC-L) SC-L at securecoding.org
> List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l
> List charter available at - http://www.securecoding.org/list/charter.php
> SC-L is hosted and moderated by KRvW Associates, LLC (http://www.KRvW.com)
> as a free, non-commercial service to the software security community.
> _______________________________________________
>
>