full-disclosure - Coding securely, was Linux (in)security

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: <200310270419.h9R4JP11006164@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Coding securely, was Linux (in)security 

On Mon, 27 Oct 2003 14:35:02 +1100, Brett Hutley said:

> CALL STACK:
> 1: accept_user_input(); /* validate user input here */
> 2: processing_loop_with_user_input(); /* rather than here */

Of course, validating in (1) rather than (2) introduces race conditions and
the like (all sorts of TOCTOU issues, filesystem races, and the like), so
you need to also be sure that what's validated in (1) is what's used in (2).

Remember that most symlink races work *because* the checking is done in (1).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20031026/503e9a62/attachment.bin