nion's blog

I occasionally make use of the report function in opera in case it crashes (which happens quite often on 64bit for me), but if it crashes right when receiving the response
of the crash reporting website you really start to HATE that piece of software.


(notice Last visited URL)

FAIL! (using 0.60-6351)

There are a lot of discussions out there whether functions like strcpy are dangerous and shouldn't be used in C programs.
But Heise security made my day:

The problem is caused by the use of the unsafe C function printf in crypto_recv in ntpd/ntp_crypto.c.

Beware of the evil printf!

Im rather disappointed by the overall quality of the heise security news anyway but of course they seem to have misread the original advisory and the bug report. They mean sprintf

EDIT: they fixed it

A lot of people start throwing mud in the direction of Debian and especially the maintainer of openssl because of high impact security issue that was released today: DSA-1571.

Please notice that this was indeed discussed in 2006 with the openssl people before patching the package and it was an openssl.org guy who ACKed this patch after the maintainer asked for their opinion. So please stop blaming random people. Thanks!
Such things happen, so better use your time to fix your systems instead



UPDATE: people complaining about the "fact" that the "wrong" list was used to contact the openssl people, please read this

Stefan Esser announced a new extension for Suhosin.

There is a new suhosin.server.strip extension which will replace all < < ' " and `characters by ? in PHP_SELF, PATH_INFO and PATH_TRANSLATED and thus preventing XSS attacks.

The second new neat feature is suhosin.server.encode which scan for the above characters in REQUEST_URI and QUERY_STRING because not every browser (IE for example) will encode the characters before sending them.

Both are enabled by default in Suhosin in version 0.9.21. This is really neat!

[via Stefan Esser]

Another nice piece of code made by ESR you know, the guy who writes books about "The art of UNIX programming" for example

From sink.c:


This code will segfault if the fopen call in line 4 fails, sinkfp will become NULL then which leads
to a segfault when writing more than once into it with fprintf/fputs.

What I find funny now is the check in line 17 to test the error indicator for the stream pointed to by sinkfp AFTER actually writing into it.
But what is even more funny is that also the check would segfault in this case since ferror will if it gets a NULL pointer.