Secunia has published following advisory regarding inotify-tools: http://secunia.com/advisories/26825/ A vulnerability has been reported in inotify-tools, which can potentially be exploited by malicious users to compromise an application using the library. The vulnerability is caused due to a boundary error within the "inotifytools_snprintf()" function in src/inotifytools.c. This can be exploited to cause a buffer overflow by e.g. creating a file with an overly long filename in a specific directory. Successful exploitation may allow the execution of arbitrary code with privileges of the application using the affected library. NOTE: The programs shipped with inotify-tools are reportedly not affected. The vulnerability is reported in versions prior to 3.11.
Dawid: Do you need any help with doing the update? Or is there any other reason this is not updated?
Packages were built few weeks ego: http://koji.fedoraproject.org/koji/buildinfo?buildID=19441 http://koji.fedoraproject.org/koji/buildinfo?buildID=19436 I requested updating immediately after RPMs were ready: https://admin.fedoraproject.org/updates/F7/pending/inotify-tools-3.11-1.fc7 I'm not sure why they were in pending state so long. I thought that someone will push them to the updates repo. Updating process was a bit easier in FC6.
Dawid: Thanks for the update. You did everything you should have done for the updates, it probably takes so long because we still need one person to sign the packages, situation will improve when signing server is finished. Everytime you think that something is wrong with any of your updates, especially security ones, please complain on mailing list, irc channel, etc.). It might be that there is a bug in the update system, or something like that. In case of security updates, feel free to write to fedora-security-list or anyone from Fedora Security Team, and we'll try the best we can to help you solve the problem.
OK, thanks for the clarification. :)
inotify-tools-3.11-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.