full-disclosure - Evidence of a ISC being hacked?

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]

From: peak at argo.troja.mff.cuni.cz (Pavel Kankovsky)
Subject: Evidence of a ISC being hacked? 

On Thu, 24 Jun 2004 Valdis.Kletnieks@...edu wrote:

> It's easier to just #define the critter than to re-re-invent the C code
> for vsnprintf() (which isn't always trivial, as your vsnprintf() has to play
> nice with the vendor's stdio - this can be .. umm... "interesting" if the
> innards of the vendor stdio are more bizzare than usual...

vsnprintf() does not have to "play nice" with stdio. It does not have to
play with stdio at all. You don't need to mess with stdio in order to
stuff some characters into an array.

> Go ahead - go and re-write a vsnprintf, and compare that to the time it
> takes to do the #define

It is rather easy as long as everything you need are common string and
integer directives. Indeed, floats are tricky. Exotic C99 is even more
tricky. But I think the set of printf features required by dhcpd and
similar programs is (or should be) pretty small.

--Pavel Kankovsky aka Peak  [ Boycott Microsoft--http://www.vcnet.com/bms ]
"Resistance is futile. Open your source code and prepare for assimilation."