Received: (qmail 1542 invoked by uid 2012); 17 Feb 1998 18:59:56 -0000 Message-Id: <19980217185956.1541.qmail@hyperreal.org> Date: 17 Feb 1998 18:59:56 -0000 From: Timothy VanFosson Reply-To: timv@ccad.uiowa.edu To: apbugs@hyperreal.org Subject: problem with uudecode() when optimizations turned on X-Send-Pr-Version: 3.2 >Number: 1824 >Category: os-irix >Synopsis: problem with uudecode() when optimizations turned on >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Feb 17 11:00:00 PST 1998 >Last-Modified: Wed May 20 03:28:13 PDT 1998 >Originator: timv@ccad.uiowa.edu >Organization: >Release: 1.2.5 >Environment: IRIX 6.2, 64-bit Compiler version 6.2 Compiler options: -Iregex -O2 -n32 -DIRIX -DSTATUS >Description: The uudecode() function seems to fail for some authorization strings when the optimization level is set to "-O2". uudecode() only returns the user id and the first four letters of the decoded password entry. This causes the authorization attempt to fail even if the user enters the correct password. >How-To-Repeat: Create both a group and a password file. The group file contains one group entry with three users. Use a require-group to reference this group entry. Try accessing the directory protected by the directive using the id of the second of the three users in the group entry. >Fix: In the course of trying to track this down I found that putting in fprintf()s in the uudecode() function caused the in correct behavior to cease. I suspect that it is either stack-related in the code or the compiler. Turning off the optimizations also "cured" the incorrect behavior. I have not tried it using newer compilers >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: brian State-Changed-When: Wed May 20 03:28:13 PDT 1998 State-Changed-Why: Yeah, sounds like a buggy compiler. Your note will always be available in the bug database here for future reference - thanks for the report. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]