https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c1 Karl Eichwalder changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #1 from Karl Eichwalder 2013-10-28 12:37:40 CET --- From: Bernhard Voelker

On October 27, 2013 at 6:24 PM dieter wrote: findutils-locate was replaced by mlocate.

Why do you think so? findutils [1] is still shipped with locate(1) and the update(1) job for cron. [1] https://build.opensuse.org/package/show/openSUSE:13.1:Update/findutils =========================================================================== Please check it again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c3 Tomáš Chvátal changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |tchvatal@suse.com InfoProvider|suse-beta@cboltz.de | --- Comment #3 from Tomáš Chvátal 2013-10-28 17:16:40 UTC --- Yea I added mlocate as replacement for findutils because it is way faster in both search and logging. FWIW the group issue should be solved but I am bit torn about the solution. 1) Upstream uses sgid which lets you to read the whole file and determine what you can see and what not. And our security won't let this happen altho all other distros just go with it and are happy about :( 2) We have the group while locate command itself does not show files you can't access you still can read the db file completely because you are in the group. 3) We can reduce the scope of usability to index only as nobody:nobody and thus allow everyone to read our file, but then nothing of importance would be there which severly impacts the actual usability of the thing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c5 Karl Eichwalder changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |tchvatal@suse.com --- Comment #5 from Karl Eichwalder 2013-10-29 09:06:24 CET --- (In reply to comment #3)

Yea I added mlocate as replacement for findutils because it is way faster in both search and logging.

FWIW the group issue should be solved but I am bit torn about the solution.

The more it mimics locate, the better ;) As long as it is mostly similar to locate, we do not need a release notes entry. If if would hide more than locate, we should probably provide a release notes snippet telling the user how he can work around the restriction.

1) Upstream uses sgid which lets you to read the whole file and determine what you can see and what not. And our security won't let this happen altho all other distros just go with it and are happy about :( 2) We have the group while locate command itself does not show files you can't access you still can read the db file completely because you are in the group. 3) We can reduce the scope of usability to index only as nobody:nobody and thus allow everyone to read our file, but then nothing of importance would be there which severly impacts the actual usability of the thing.

Ok, unfortunately, I cannot decide about it. I personally would vote to make all the files available to the user that he could see using 'find' ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c7 Karl Eichwalder changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #7 from Karl Eichwalder 2013-10-30 10:24:37 CET --- ok, thanks. In this case, no RN entry is needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c9 Karl Eichwalder changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |ke@suse.com, | |lnussel@suse.com Resolution|WORKSFORME | AssignedTo|ke@suse.com |tchvatal@suse.com --- Comment #9 from Karl Eichwalder 2013-11-12 14:29:27 CET --- (In reply to comment #6)

Ah I wrote bug not bnc in the changelog so it was not picked.

https://build.opensuse.org/request/show/205109

No groups, default settings same as old locate, only the locate db changed format and was moved, not sure what to do about that.

After updating to the current 13.1 GM candidate with yast, I -- as the regular user 'ke' -- can no longer use it: locate Document bash: /usr/bin/locate: Permission denied Maybe, your fix still sits in the update area? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c11 Benjamin Brunner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #11 from Benjamin Brunner 2013-11-12 17:48:33 CET --- The update for 13.1 is released now. Resolved fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c13 Karl Eichwalder changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED --- Comment #13 from Karl Eichwalder 2013-11-13 12:29:37 CET --- Here is my proposal: <title>Locate: Replacing findutils-locate by mlocate</title> <para> The <command>mlocate</command> tool is the replacement for <command>findutils-locate</command>. In the default configuration <command>mlocate</command> behave the same as <command>findutils-locate</command>. Because of an improved permission handling, it could take up to 24 hours, until the database file will become available to regular users. </para> <para> In case you encounter a "Permission denied" message, and want to speed up the access to the database file, consider to remove <filename>cron.daily</filename> (do not do this if you run sensible tasks via the <filename>cron.daily</filename> mechanism): </para> <screen>rm /var/spool/cron/lastrun/cron.daily</screen> <para> Within the next 15 minutes the daily cron routine will start and build a proper mlocate file. </para> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c15 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #15 from Christian Boltz 2013-11-14 13:29:24 CET --- (In reply to comment #13)

Here is my proposal: [...] In case you encounter a "Permission denied" message, and want to speed up the access to the database file, consider to remove <filename>cron.daily</filename> (do not do this if you run sensible tasks via the <filename>cron.daily</filename> mechanism): </para> <screen>rm /var/spool/cron/lastrun/cron.daily</screen> <para> Within the next 15 minutes the daily cron routine will start and build a proper mlocate file. </para>

Why don't you recomment to just run /etc/cron.daily/mlocate.cron as root once? That's easier to explain, faster (you don't have to wait 15 minutes) and avoids the possible side effects of an additional cron.daily run. Proposal: In case you encounter a "Permission denied" message shortly after installing mlocate, run /etc/cron.daily/mlocate.cron as root once. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847801 https://bugzilla.novell.com/show_bug.cgi?id=847801#c17 --- Comment #17 from Swamp Workflow Management 2013-11-15 18:08:18 UTC --- openSUSE-RU-2013:1697-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 847801 CVE References: Sources used: openSUSE 13.1 (src): mlocate-0.26-4.5.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.