Bug 588 - Verify exist cache for a uid
Verify exist cache for a uid
Status: RESOLVED FIXED
Product: Sudo
Classification: Unclassified
Component: Sudo
1.7.4
PC Linux
: low normal
Assigned To: Todd C. Miller
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-13 09:03 MST by christophe.sabattier
Modified: 2013-02-13 09:39 MST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description christophe.sabattier 2013-02-13 09:03:49 MST
sudo: unable to cache group DOMAIN\Group , already exists.
This is a randomly problem and i think it is a problem with the 'likewise-open' cache.
I can't debug anything on this server because we lost the root of the virtual machine and they are no way to restart it with a backup cd for many reasons and root is deactivate...
Anyways, first condition for the verify existing cache is in "sudo-1.7.4p5/pwutil.c"
line 242
 if (rbinsert(pwcache_byname, (void *) pw) != NULL)
            errorx(1, "unable to cache user %s, already exists", name);


I want to know if is dangerous to remove they cache checking conditions or / and can you create a warning function instead the errorx function who have been effect to crash sudo when we have a 'likewise-open' cache problem.

Thank you for your answer.
Comment 1 Todd C. Miller 2013-02-13 09:39:25 MST
This was fixed in sudo 1.7.5, here's the relevant entry from the NEWS file:

 * Password and group entries are now cached using the same key
   that was used to look them up.  This fixes a problem when looking
   up entries by name if the name in the retrieved entry does not
   match the name used to look it up.  This may happen on some systems
   that do case insensitive lookups or that truncate long names.

You could just ignore the error but I'd suggest you simply update to a more recent version of sudo.  The current version of sudo 1.7.x is 1.7.10p6