A bug was found in the way slocate processes very long paths. A local user could create a carefully crafted directory structure that would prevent updatedb from completing its file system scan, resulting in an incomplete slocate database. The Common Vulnerabilities and Exposures project has assigned the name CAN-2005-2499 to this issue. See http://rhn.redhat.com/errata/RHSA-2005-346.html Technically, I'm not sure this is a security issue, although it does allow a non-root user to stop slocate from working, so I guess we should consider it. Any thoughts one way or the other on if FL should patch this?