Is slocate (secure locate) still maintained?
 

http://slocate.trakker.ca/ seems to have been down for a few years (last backup).

Google searches for "secure locate Kevin Lindsay" and "secure locate source" do not show any signs of ongoing maintenance, but do bring up a few security advisories related, afaict, to memory corruption. If it's a Google problem, sorry in advance to the maintainer.

Just because there are security advisories does not mean that the slocate project is active. It just means that they were found. If you are worried about them, how about getting the source and attempt to fix it yourself? :rolleyes:

I think that withered a while back.
These days you should really be using mlocate - has significant performance benefits as it implement the inotify API.

Edit: - didn't notice this was the Slack forum. I wondered some time back why Pat wasn't including mlocate. It that still the case ?.

13.1 has slocate 3.1 only; what about the current? mlocate does look better: offers more options, is actively maintained, is compatible with slocate and (mostly) GNU locate. On the bright side of this issue, a heap-related bug appears to have been fixed back in version 2.5 of slocate and there were no vulnerability reports since then.

I have not been using mlocate. How does it deal with filesystems without inotify support (such as NFS v3)?

I imagine it implements inotify (if available) - I doubt it would require it. Been a while since I looked into it though I must admit - just been using it. I don't use NFS3 though.

I don't believe either implementation of locate uses inotify: none of them have daemons. The index is manually rebuilt with updatedb, which runs from cron.daily in Slackware 13.1. Any filesystem can be indexed if it's mounted while updatedb is running.