full-disclosure - automated vulnerability testing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <200311301948.hAUJm200013290@caligula.anu.edu.au>
From: avalon at caligula.anu.edu.au (Darren Reed)
Subject: automated vulnerability testing

In some mail from Choe.Sung Cont. PACAF CSS/SCHP, sie said:
> 
> Bill Royds wrote:
> > If you are truly interested in security, you won't use C as the
> programming
> > language. 
> You must be shitting me..  C does have its inherent flaws but that doesn't
> mean that there cannot be a secure application written in C.  This statement
> represents FUD at its highest level.

In a sense, he is right.  The effort you need to go to with C in order
to code "securely" is obscene.  Programming should evolve to a point
where programmers don't need to worry about crap like that unless they're
writing bootstrap code for an OS loader (or similar).  Sooner or later,
C needs to become obsolete.

That aside, I can program more easily and securely in Java than I can
with C, any time.  The "more securely" comes from it being easier to
understand by others as much as anything else.

Darren