change_password 4.2b - command line works, not web

[Christopher J. Hinkle-2]

Good evening --
 
System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with latest patches;
Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52; SELinux.  Relevant plugins:
Compatibility 2.0.11; change_password 4.2b from
http://www.linuxmail.info/change_passwd/, which I understood from a search
of the archives to be the latest version.  (I know SM 1.4.8 is older, but
it's the latest RPM released for RHEL4.)
 
I installed the change_password plugin today (and upgraded Compatibility)
after many requests for the feature from my users.  I ran into a few
problems, which I believe I've rectified... briefly:
    - SELinux was throwing errors accessing chpasswd; I updated the context
of the file to be the same as httpd and now the errors don't appear.
    - chpasswd was throwing a "Floating point exception" error.  I
recompiled it (without changes) from the chpasswd.c file that was included
in the plugin, and that error went away.
 
Presently I can change a user's password (while logged in as root) by using
the newly compiled chpasswd program from the command line.  I've verified
that it works as expected.  However, when I try to execute the change from
the web, I get this response: "Current password is incorrect" with a return
code of 9.  This only happens when I supply the correct old password and
good values for the new password.  If I supply a wrong old password, it
returns the error, "Your current password is not correct."  Slightly
different wording, and no return code from chpasswd.

An inspection of chpasswd.c shows that the line that seems to be failing is
line 155: if(strcmp(WOld_pw, (char *)crypt(Old_pw, WOld_pw)) != 0) {...}.
This condition is what would return the code 9 error I'm getting -- again,
only via the website.

Any ideas how to rectify this problem?  My search of the archives was
helpful to resolve other issues, but this one remains.

Thanks very much,
chris.

--
Christopher J. Hinkle                  ______  chinkle@...
Manager, Network Operations & Support  \    /  703/299-1580 x4 (w)
NetLink Resource Group, Inc.            \  /   703/338-3859 (c)
901A King Street, Alexandria, VA  22314  \/ http://www.netlinkrg.com 



-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Paul Lesniewski]

On Tue, Jul 1, 2008 at 3:52 PM, Christopher J. Hinkle
<chinkle@...> wrote:
> Good evening --
>
> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with latest patches;
> Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52; SELinux.  Relevant plugins:
> Compatibility 2.0.11; change_password 4.2b from
> http://www.linuxmail.info/change_passwd/, which I understood from a search
> of the archives to be the latest version.

The person who made that post was rather presumptuous about such and
had not bothered to search the archives to see that there has been a
4.2 version available offlist for quite a long time.  So, no, it's not
the official latest version, but I do believe either one should suit
your needs.

>  (I know SM 1.4.8 is older, but
> it's the latest RPM released for RHEL4.)
>
> I installed the change_password plugin today (and upgraded Compatibility)
> after many requests for the feature from my users.  I ran into a few
> problems, which I believe I've rectified... briefly:
>    - SELinux was throwing errors accessing chpasswd; I updated the context
> of the file to be the same as httpd and now the errors don't appear.
>    - chpasswd was throwing a "Floating point exception" error.  I
> recompiled it (without changes) from the chpasswd.c file that was included
> in the plugin, and that error went away.
>
> Presently I can change a user's password (while logged in as root) by using
> the newly compiled chpasswd program from the command line.  I've verified
> that it works as expected.  However, when I try to execute the change from
> the web, I get this response: "Current password is incorrect" with a return
> code of 9.  This only happens when I supply the correct old password and
> good values for the new password.  If I supply a wrong old password, it
> returns the error, "Your current password is not correct."  Slightly
> different wording, and no return code from chpasswd.
>
> An inspection of chpasswd.c shows that the line that seems to be failing is
> line 155: if(strcmp(WOld_pw, (char *)crypt(Old_pw, WOld_pw)) != 0) {...}.
> This condition is what would return the code 9 error I'm getting -- again,
> only via the website.
>
> Any ideas how to rectify this problem?  My search of the archives was
> helpful to resolve other issues, but this one remains.

I am not the author of that plugin, but you are welcome to try my
version 4.2-beta if you ask offlist.  No guarantees that it will fix
your issue.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Christopher J. Hinkle-2]

> On Tue, Jul 1, 2008 at 3:52 PM, Christopher J. Hinkle
<chinkle@...> wrote:
>> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with latest
>> patches; Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52; SELinux.
Relevant plugins:
>> Compatibility 2.0.11; change_password 4.2b from
>> http://www.linuxmail.info/change_passwd/, which I understood from a
>> search of the archives to be the latest version.
>
> The person who made that post was rather presumptuous about such and had
not
> bothered to search the archives to see that there has been a
> 4.2 version available offlist for quite a long time.  So, no, it's not the

> official latest version, but I do believe either one should suit your
needs.

I've now installed your 4.2-beta version (thank you), and continue to have
the same difficulty.  I did not need to recompile chpasswd this time, but
the results are largely the same.

More details as requested from the README file:
- User/group of webserver: apache/apache
- PHP version and config details: 4.3.9... please let me know what other
details are needed -- I'm not very familiar with PHP.
- Directory listing:
total 196
drwxrwxr-x   2 root root    4096 Jul  3 19:03 ./
drwxr-xr-x  32 root root    4096 Jul  3 17:42 ../
-rw-r--r--   1 root root    2481 Sep  8  2006 change_passwd.pot
-rwsr-x---   1 root apache 10868 Sep 12  2006 chpasswd*
-rw-rw-r--   1 root root    7360 Sep 12  2006 chpasswd.c
-rw-r--r--   1 root root    2906 Jul  3 19:03 config.php
-rw-rw-r--   1 root root    2906 Sep 10  2006 config.sample.php
-rw-rw-r--   1 root root   15802 Nov 28  2004 COPYING
-rw-rw-r--   1 root root     610 Nov 28  2004 exec_test.php
-rw-rw-r--   1 root root     881 Sep  8  2006 functions.php
-rwxrw-r--   1 root root     388 Nov 22  2005 getpot*
-rw-rw-r--   1 root root     486 Nov 28  2004 index.php
-rw-rw-r--   1 root root    2343 Sep 12  2006 INSTALL
-rwx------   1 root root    5793 Sep 12  2006 make_release.sh*
-rw-rw-r--   1 root root   17787 Sep  8  2006 options.php
-rw-rw-r--   1 root root   11232 Sep 12  2006 README
-rw-r--r--   1 root root    1221 Sep 12  2006 setup.php
-rw-rw-r--   1 root root      24 Sep 12  2006 version

- Verify that the permissions on chpasswd are correct: Verified.
- $seeOutput results:
Correct password yields:
        Your current password is not correct
        Command output:
        Current password is incorrect
        Return code: 9
 
Incorrect password yields:
        Your current password is not correct
- $debug results:
I was able to successfully change a user's password using the command syntax
returned by the Debug.  Further, the following was returned to the screen:
        Permissions of chpasswd executable are: 104750
        chpasswd has group ownership: apache
        Your web server is running under group: apache
        chpasswd is owned by: root

>> Presently I can change a user's password (while logged in as root) by
>> using the newly compiled chpasswd program from the command line.  I've
>> verified that it works as expected.  However, when I try to execute
>> the change from the web, I get this response: "Current password is
>> incorrect" with a return code of 9.  This only happens when I supply
>> the correct old password and good values for the new password.  If I
>> supply a wrong old password, it returns the error, "Your current
>> password is not correct."  Slightly different wording, and no return code
from chpasswd.
>>
>> An inspection of chpasswd.c shows that the line that seems to be
>> failing is line 155: if(strcmp(WOld_pw, (char *)crypt(Old_pw, WOld_pw))
!= 0) {...}.
>> This condition is what would return the code 9 error I'm getting --
>> again, only via the website.
>>
>> Any ideas how to rectify this problem?  My search of the archives was
>> helpful to resolve other issues, but this one remains.
>
> I am not the author of that plugin, but you are welcome to try my version
> 4.2-beta if you ask offlist.  No guarantees that it will fix your issue.

Unfortunately it didn't.  Do you have any recommendations of other things to
try?  The same line quoted above (the code, not the line number) seems to be
in your code as was in the other's, and still seems to be the source of the
returned error message when the correct password is provided.  However, this
other error that now constantly appears, "Your current password is not
correct," doesn't seem to stem from the chpasswd code.  Where might that
error originate?

Please let me know if I can provide further detailed information.

Thanks much,
chris.


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Paul Lesniewski]

>>> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with latest
>>> patches; Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52; SELinux.
> Relevant plugins:
>>> Compatibility 2.0.11; change_password 4.2b from
>>> http://www.linuxmail.info/change_passwd/, which I understood from a
>>> search of the archives to be the latest version.
>>
>> The person who made that post was rather presumptuous about such and had
> not
>> bothered to search the archives to see that there has been a
>> 4.2 version available offlist for quite a long time.  So, no, it's not the
>
>> official latest version, but I do believe either one should suit your
> needs.
>
> I've now installed your 4.2-beta version (thank you), and continue to have
> the same difficulty.  I did not need to recompile chpasswd this time, but
> the results are largely the same.
>
> More details as requested from the README file:
> - User/group of webserver: apache/apache
> - PHP version and config details: 4.3.9... please let me know what other
> details are needed -- I'm not very familiar with PHP.
> - Directory listing:
> total 196
> drwxrwxr-x   2 root root    4096 Jul  3 19:03 ./
> drwxr-xr-x  32 root root    4096 Jul  3 17:42 ../
> -rw-r--r--   1 root root    2481 Sep  8  2006 change_passwd.pot
> -rwsr-x---   1 root apache 10868 Sep 12  2006 chpasswd*
> -rw-rw-r--   1 root root    7360 Sep 12  2006 chpasswd.c
> -rw-r--r--   1 root root    2906 Jul  3 19:03 config.php
> -rw-rw-r--   1 root root    2906 Sep 10  2006 config.sample.php
> -rw-rw-r--   1 root root   15802 Nov 28  2004 COPYING
> -rw-rw-r--   1 root root     610 Nov 28  2004 exec_test.php
> -rw-rw-r--   1 root root     881 Sep  8  2006 functions.php
> -rwxrw-r--   1 root root     388 Nov 22  2005 getpot*
> -rw-rw-r--   1 root root     486 Nov 28  2004 index.php
> -rw-rw-r--   1 root root    2343 Sep 12  2006 INSTALL
> -rwx------   1 root root    5793 Sep 12  2006 make_release.sh*
> -rw-rw-r--   1 root root   17787 Sep  8  2006 options.php
> -rw-rw-r--   1 root root   11232 Sep 12  2006 README
> -rw-r--r--   1 root root    1221 Sep 12  2006 setup.php
> -rw-rw-r--   1 root root      24 Sep 12  2006 version
>
> - Verify that the permissions on chpasswd are correct: Verified.
> - $seeOutput results:
> Correct password yields:
>        Your current password is not correct
>        Command output:
>        Current password is incorrect
>        Return code: 9
>
> Incorrect password yields:
>        Your current password is not correct
> - $debug results:
> I was able to successfully change a user's password using the command syntax
> returned by the Debug.  Further, the following was returned to the screen:
>        Permissions of chpasswd executable are: 104750
>        chpasswd has group ownership: apache
>        Your web server is running under group: apache
>        chpasswd is owned by: root
>
>>> Presently I can change a user's password (while logged in as root) by
>>> using the newly compiled chpasswd program from the command line.  I've
>>> verified that it works as expected.  However, when I try to execute
>>> the change from the web, I get this response: "Current password is
>>> incorrect" with a return code of 9.  This only happens when I supply
>>> the correct old password and good values for the new password.  If I
>>> supply a wrong old password, it returns the error, "Your current
>>> password is not correct."  Slightly different wording, and no return code
> from chpasswd.
>>>
>>> An inspection of chpasswd.c shows that the line that seems to be
>>> failing is line 155: if(strcmp(WOld_pw, (char *)crypt(Old_pw, WOld_pw))
> != 0) {...}.
>>> This condition is what would return the code 9 error I'm getting --
>>> again, only via the website.
>>>
>>> Any ideas how to rectify this problem?  My search of the archives was
>>> helpful to resolve other issues, but this one remains.
>>
>> I am not the author of that plugin, but you are welcome to try my version
>> 4.2-beta if you ask offlist.  No guarantees that it will fix your issue.
>
> Unfortunately it didn't.  Do you have any recommendations of other things to
> try?  The same line quoted above (the code, not the line number) seems to be
> in your code as was in the other's, and still seems to be the source of the
> returned error message when the correct password is provided.  However, this
> other error that now constantly appears, "Your current password is not
> correct," doesn't seem to stem from the chpasswd code.  Where might that
> error originate?

The chpasswd code returns code 9, and the PHP code translates that to
the text you are seeing.

> Please let me know if I can provide further detailed information.

Dunno.  Something strange with how the password is being pulled from
PHP or the passwd file.  I am going to send you yet another newer
version of the plugin offlist.  When you get it, open chpasswd.c and
uncomment line 166 and recompile.  This will spill out the password
that PHP gave to it - make sure it is correct.  If it is the same as
the password that you use to log into SSH (what does the rest of that
output look like?), then there may be an issue with the crypt()
command on your system.  Oh, and I see you are running SELinux - make
sure you test it once with SELinux completely relaxed/disabled.  You
can also try step number 3 under Troubleshooting (new in the version I
am sending, and you can also try *TEMPORARILY* setting $confirmOldPass
to 0, and see what the output of the command is (while that line 166
is still uncommented).

Cheers,

 Paul

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Christopher J. Hinkle-2]

> Sent: Monday 07 July 2008 0:53
>>>> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with latest
>>>> patches; Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52; SELinux.
>> Relevant plugins:
>>>> Compatibility 2.0.11;
[..]
>> I've now installed your 4.2-beta version (thank you), and continue to
>> have the same difficulty.  I did not need to recompile chpasswd this
>> time, but the results are largely the same.
>>
>> More details as requested from the README file:
>> - User/group of webserver: apache/apache
>> - PHP version and config details: 4.3.9... please let me know what
>> other details are needed -- I'm not very familiar with PHP.
>> - Directory listing:
[..]

>>
>> - Verify that the permissions on chpasswd are correct: Verified.
>> - $seeOutput results:
>> Correct password yields:
>>        Your current password is not correct
>>        Command output:
>>        Current password is incorrect
>>        Return code: 9
>>
>> Incorrect password yields:
>>        Your current password is not correct
>> - $debug results:
>> I was able to successfully change a user's password using the command
>> syntax returned by the Debug.  Further, the following was returned to the

screen:

>>        Permissions of chpasswd executable are: 104750
>>        chpasswd has group ownership: apache
>>        Your web server is running under group: apache
>>        chpasswd is owned by: root
>>
>>>> Presently I can change a user's password (while logged in as root)
>>>> by using the newly compiled chpasswd program from the command line.  
>>>> I've verified that it works as expected.  However, when I try to
>>>> execute the change from the web, I get this response: "Current
>>>> password is incorrect" with a return code of 9.  This only happens
>>>> when I supply the correct old password and good values for the new
>>>> password.  If I supply a wrong old password, it returns the error,
>>>> "Your current password is not correct."  Slightly different wording,
>>>> and no return code from chpasswd.
>>>>
>>>> An inspection of chpasswd.c shows that the line that seems to be
>>>> failing is line 155: if(strcmp(WOld_pw, (char *)crypt(Old_pw,
>>>> WOld_pw)) != 0) {...}.
>>>> This condition is what would return the code 9 error I'm getting --
>>>> again, only via the website.
>>>>
>>>> Any ideas how to rectify this problem?  My search of the archives
>>>> was helpful to resolve other issues, but this one remains.
>>>
>>> I am not the author of that plugin, but you are welcome to try my
>>> version 4.2-beta if you ask offlist.  No guarantees that it will fix

your issue.

>>
>> Unfortunately it didn't.  Do you have any recommendations of other
>> things to try?  The same line quoted above (the code, not the line
>> number) seems to be in your code as was in the other's, and still
>> seems to be the source of the returned error message when the correct
>> password is provided.  However, this other error that now constantly
>> appears, "Your current password is not correct," doesn't seem to stem
>> from the chpasswd code.  Where might that error originate?
>
> The chpasswd code returns code 9, and the PHP code translates that
> to the text you are seeing.
>
>> Please let me know if I can provide further detailed information.
>
> Dunno.  Something strange with how the password is being pulled from
> PHP or the passwd file.  I am going to send you yet another newer
> version of the plugin offlist.  

Thanks for this.  I've installed the new compatibility and change_passwd
plugins you sent me.  I installed compatibility first and had no problems
(checked the website, looked fine, was functional).  Then I installed the
new change_passwd, and all of a sudden the Options page is blank.  I
disabled the change_passwd plugin with conf.pl, and the Options page came
back.  I know this happened once before, but I can't figure out what I did
to fix it -- it might've been that I installed a different version of
change_passwd and it came back on its own.  I've turned SELinux off and on
and it made no difference, and I'm not seeing any badness in the logs.  Any
idea there?  Despite this, I disabled the plugin in conf.pl and pushed on...

> When you get it, open chpasswd.c
> and uncomment line 166 and recompile.  

... to give feedback about this.  I wasn't able to recompile it straight on.
Output:
# make chpasswd
cc chpasswd.c -o chpasswd
/tmp/ccE3xlHn.o(.text+0x4b6): In function `main':
: undefined reference to `crypt'
/tmp/ccE3xlHn.o(.text+0x54f): In function `main':
: undefined reference to `crypt'
/tmp/ccE3xlHn.o(.text+0x5fa): In function `main':
: undefined reference to `crypt'
collect2: ld returned 1 exit status

But when I followed the INSTALL notes for a Solaris box (gcc -lcrypt -O -o
chpasswd chpasswd.c), it did compile.  Dunno if that might tell you
something about my system.

> This will spill out the
> password that PHP gave to it - make sure it is correct.  If it is
> the same as the password that you use to log into SSH (what does
> the rest of that output look like?), then there may be an issue
> with the crypt() command on your system.  Oh, and I see you are
> running SELinux - make sure you test it once with SELinux completely
> relaxed/disabled.  You can also try step number 3 under
> Troubleshooting (new in the version I am sending, and you can also
> try *TEMPORARILY* setting $confirmOldPass to 0, and see what the
> output of the command is (while that line 166 is still uncommented).

Right now I can't tell you about the output because of the Options page
problem, but...

I tried testing from the command line.  Both the original chpasswd and the
recompiled chpasswd worked the same.  They were effective and returned "The
password was modified successfully" after I supplied correct entries.

Troubleshooting #3 (exec_test.php) returns the following, and the results
are the same whether SELinux is enforced or not:

Testing exec()...
safe_mode =
safe_mode_exec_dir =

----------------------------------------------------------------------------
----
return value = 0

output:
Array
(
    [0] => COPYING
    [1] => INSTALL
    [2] => README
    [3] => change_passwd.pot
    [4] => chpasswd
    [5] => chpasswd.c
    [6] => chpasswd.orig
    [7] => config.php
    [8] => config.sample.php
    [9] => exec_test.php
    [10] => functions.php
    [11] => getpot
    [12] => index.php
    [13] => make_release.sh
    [14] => options.php
    [15] => setup.php
    [16] => version
)

Sorry for the delay in replying, but, well, you know how it goes. :)

Thanks,
chris.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Paul Lesniewski]

On Tue, Jul 22, 2008 at 5:47 PM, Christopher J. Hinkle
<chinkle@...> wrote:

>> Sent: Monday 07 July 2008 0:53
>>>>> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with latest
>>>>> patches; Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52; SELinux.
>>> Relevant plugins:
>>>>> Compatibility 2.0.11;
> [..]
>>> I've now installed your 4.2-beta version (thank you), and continue to
>>> have the same difficulty.  I did not need to recompile chpasswd this
>>> time, but the results are largely the same.
>>>
>>> More details as requested from the README file:
>>> - User/group of webserver: apache/apache
>>> - PHP version and config details: 4.3.9... please let me know what
>>> other details are needed -- I'm not very familiar with PHP.
>>> - Directory listing:
> [..]
>>>
>>> - Verify that the permissions on chpasswd are correct: Verified.
>>> - $seeOutput results:
>>> Correct password yields:
>>>        Your current password is not correct
>>>        Command output:
>>>        Current password is incorrect
>>>        Return code: 9
>>>
>>> Incorrect password yields:
>>>        Your current password is not correct
>>> - $debug results:
>>> I was able to successfully change a user's password using the command
>>> syntax returned by the Debug.  Further, the following was returned to the
> screen:
>>>        Permissions of chpasswd executable are: 104750
>>>        chpasswd has group ownership: apache
>>>        Your web server is running under group: apache
>>>        chpasswd is owned by: root
>>>
>>>>> Presently I can change a user's password (while logged in as root)
>>>>> by using the newly compiled chpasswd program from the command line.
>>>>> I've verified that it works as expected.  However, when I try to
>>>>> execute the change from the web, I get this response: "Current
>>>>> password is incorrect" with a return code of 9.  This only happens
>>>>> when I supply the correct old password and good values for the new
>>>>> password.  If I supply a wrong old password, it returns the error,
>>>>> "Your current password is not correct."  Slightly different wording,
>>>>> and no return code from chpasswd.
>>>>>
>>>>> An inspection of chpasswd.c shows that the line that seems to be
>>>>> failing is line 155: if(strcmp(WOld_pw, (char *)crypt(Old_pw,
>>>>> WOld_pw)) != 0) {...}.
>>>>> This condition is what would return the code 9 error I'm getting --
>>>>> again, only via the website.
>>>>>
>>>>> Any ideas how to rectify this problem?  My search of the archives
>>>>> was helpful to resolve other issues, but this one remains.
>>>>
>>>> I am not the author of that plugin, but you are welcome to try my
>>>> version 4.2-beta if you ask offlist.  No guarantees that it will fix
> your issue.
>>>
>>> Unfortunately it didn't.  Do you have any recommendations of other
>>> things to try?  The same line quoted above (the code, not the line
>>> number) seems to be in your code as was in the other's, and still
>>> seems to be the source of the returned error message when the correct
>>> password is provided.  However, this other error that now constantly
>>> appears, "Your current password is not correct," doesn't seem to stem
>>> from the chpasswd code.  Where might that error originate?
>>
>> The chpasswd code returns code 9, and the PHP code translates that
>> to the text you are seeing.
>>
>>> Please let me know if I can provide further detailed information.
>>
>> Dunno.  Something strange with how the password is being pulled from
>> PHP or the passwd file.  I am going to send you yet another newer
>> version of the plugin offlist.
>
> Thanks for this.  I've installed the new compatibility and change_passwd
> plugins you sent me.  I installed compatibility first and had no problems
> (checked the website, looked fine, was functional).  Then I installed the
> new change_passwd, and all of a sudden the Options page is blank.  I
> disabled the change_passwd plugin with conf.pl, and the Options page came
> back.  I know this happened once before, but I can't figure out what I did
> to fix it -- it might've been that I installed a different version of
> change_passwd and it came back on its own.  I've turned SELinux off and on
> and it made no difference, and I'm not seeing any badness in the logs.  Any
> idea there?  Despite this, I disabled the plugin in conf.pl and pushed on...

http://www.squirrelmail.org/wiki/BlankPage

>> When you get it, open chpasswd.c
>> and uncomment line 166 and recompile.
>
> ... to give feedback about this.  I wasn't able to recompile it straight on.
> Output:
> # make chpasswd
> cc chpasswd.c -o chpasswd
> /tmp/ccE3xlHn.o(.text+0x4b6): In function `main':
> : undefined reference to `crypt'
> /tmp/ccE3xlHn.o(.text+0x54f): In function `main':
> : undefined reference to `crypt'
> /tmp/ccE3xlHn.o(.text+0x5fa): In function `main':
> : undefined reference to `crypt'
> collect2: ld returned 1 exit status
>
> But when I followed the INSTALL notes for a Solaris box (gcc -lcrypt -O -o
> chpasswd chpasswd.c), it did compile.  Dunno if that might tell you
> something about my system.
>
>> This will spill out the
>> password that PHP gave to it - make sure it is correct.  If it is
>> the same as the password that you use to log into SSH (what does
>> the rest of that output look like?), then there may be an issue
>> with the crypt() command on your system.  Oh, and I see you are
>> running SELinux - make sure you test it once with SELinux completely
>> relaxed/disabled.  You can also try step number 3 under
>> Troubleshooting (new in the version I am sending, and you can also
>> try *TEMPORARILY* setting $confirmOldPass to 0, and see what the
>> output of the command is (while that line 166 is still uncommented).
>
> Right now I can't tell you about the output because of the Options page
> problem, but...
>
> I tried testing from the command line.  Both the original chpasswd and the
> recompiled chpasswd worked the same.  They were effective and returned "The
> password was modified successfully" after I supplied correct entries.
>
> Troubleshooting #3 (exec_test.php) returns the following, and the results
> are the same whether SELinux is enforced or not:
>
> Testing exec()...
> safe_mode =
> safe_mode_exec_dir =
>
> ----------------------------------------------------------------------------
> ----
> return value = 0
>
> output:
> Array
> (
>    [0] => COPYING
>    [1] => INSTALL
>    [2] => README
>    [3] => change_passwd.pot
>    [4] => chpasswd
>    [5] => chpasswd.c
>    [6] => chpasswd.orig
>    [7] => config.php
>    [8] => config.sample.php
>    [9] => exec_test.php
>    [10] => functions.php
>    [11] => getpot
>    [12] => index.php
>    [13] => make_release.sh
>    [14] => options.php
>    [15] => setup.php
>    [16] => version
> )
>
> Sorry for the delay in replying, but, well, you know how it goes. :)
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Christopher J. Hinkle-2]

 
Sent: Tuesday 22 July 2008 22:16
> On Tue, Jul 22, 2008 at 5:47 PM, Christopher J. Hinkle
<chinkle@...> wrote:

>>> Sent: Monday 07 July 2008 0:53
>>>>>> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with
>>>>>> latest patches; Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52;
>>>>>> PHP 4.3.9; SELinux.
>>>> Relevant plugins:
> Compatibility 2.0.12; change_passwd 4.3beta1
>> [..]
>>> Dunno.  Something strange with how the password is being pulled from
>>> PHP or the passwd file.  I am going to send you yet another newer
>>> version of the plugin offlist.
>>
>> Thanks for this.  I've installed the new compatibility and
>> change_passwd plugins you sent me.  I installed compatibility first
>> and had no problems (checked the website, looked fine, was
>> functional).  Then I installed the new change_passwd, and all of a
>> sudden the Options page is blank.  I disabled the change_passwd plugin
>> with conf.pl, and the Options page came back.  I know this happened
>> once before, but I can't figure out what I did to fix it -- it
>> might've been that I installed a different version of change_passwd
>> and it came back on its own.  I've turned SELinux off and on and it
>> made no difference, and I'm not seeing any badness in the logs.  
>> Any idea there?  Despite this, I disabled the plugin in conf.pl
>> and pushed on...
>
> http://www.squirrelmail.org/wiki/BlankPage

Thanks.

The relevant portion of error_log reads:
[client x.x.x.x] PHP Fatal error:  Call to undefined function:
sq_change_text_domain() in
/usr/share/squirrelmail/plugins/change_passwd/functions.php on line 26,
referer: http://mail.netlinkrg.com/src/right_main.php

>>> When you get it, open chpasswd.c
>>> and uncomment line 166 and recompile.
>>
>> ... to give feedback about this.  I wasn't able to recompile it straight
on.

>> Output:
>> # make chpasswd
>> cc chpasswd.c -o chpasswd
>> /tmp/ccE3xlHn.o(.text+0x4b6): In function `main':
>> : undefined reference to `crypt'
>> /tmp/ccE3xlHn.o(.text+0x54f): In function `main':
>> : undefined reference to `crypt'
>> /tmp/ccE3xlHn.o(.text+0x5fa): In function `main':
>> : undefined reference to `crypt'
>> collect2: ld returned 1 exit status
>>
>> But when I followed the INSTALL notes for a Solaris box (gcc -lcrypt
>> -O -o chpasswd chpasswd.c), it did compile.  Dunno if that might tell
>> you something about my system.
>>
>>> This will spill out the
>>> password that PHP gave to it - make sure it is correct.  If it is the
>>> same as the password that you use to log into SSH (what does the rest
>>> of that output look like?), then there may be an issue with the
>>> crypt() command on your system.  Oh, and I see you are running
>>> SELinux - make sure you test it once with SELinux completely
>>> relaxed/disabled.  You can also try step number 3 under
>>> Troubleshooting (new in the version I am sending, and you can also
>>> try *TEMPORARILY* setting $confirmOldPass to 0, and see what the
>>> output of the command is (while that line 166 is still uncommented).
>>
>> Right now I can't tell you about the output because of the Options
>> page problem, but...
>>
>> I tried testing from the command line.  Both the original chpasswd and
>> the recompiled chpasswd worked the same.  They were effective and
>> returned "The password was modified successfully" after I supplied

correct entries.

>>
>> Troubleshooting #3 (exec_test.php) returns the following, and the
>> results are the same whether SELinux is enforced or not:
>>
>> Testing exec()...
>> safe_mode =
>> safe_mode_exec_dir =
>>
>> ----------------------------------------------------------------------
>> return value = 0
>>
>> output:
>> Array
>> (
>>    [0] => COPYING
>>    [1] => INSTALL
>>    [2] => README
>>    [3] => change_passwd.pot
>>    [4] => chpasswd
>>    [5] => chpasswd.c
>>    [6] => chpasswd.orig
>>    [7] => config.php
>>    [8] => config.sample.php
>>    [9] => exec_test.php
>>    [10] => functions.php
>>    [11] => getpot
>>    [12] => index.php
>>    [13] => make_release.sh
>>    [14] => options.php
>>    [15] => setup.php
>>    [16] => version
>> )
>>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Paul Lesniewski]

On Tue, Jul 22, 2008 at 7:38 PM, Christopher J. Hinkle
<chinkle@...> wrote:

>
> Sent: Tuesday 22 July 2008 22:16
>> On Tue, Jul 22, 2008 at 5:47 PM, Christopher J. Hinkle
> <chinkle@...> wrote:
>>>> Sent: Monday 07 July 2008 0:53
>>>>>>> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with
>>>>>>> latest patches; Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52;
>>>>>>> PHP 4.3.9; SELinux.
>>>>> Relevant plugins:
>> Compatibility 2.0.12; change_passwd 4.3beta1
>>> [..]
>>>> Dunno.  Something strange with how the password is being pulled from
>>>> PHP or the passwd file.  I am going to send you yet another newer
>>>> version of the plugin offlist.
>>>
>>> Thanks for this.  I've installed the new compatibility and
>>> change_passwd plugins you sent me.  I installed compatibility first
>>> and had no problems (checked the website, looked fine, was
>>> functional).  Then I installed the new change_passwd, and all of a
>>> sudden the Options page is blank.  I disabled the change_passwd plugin
>>> with conf.pl, and the Options page came back.  I know this happened
>>> once before, but I can't figure out what I did to fix it -- it
>>> might've been that I installed a different version of change_passwd
>>> and it came back on its own.  I've turned SELinux off and on and it
>>> made no difference, and I'm not seeing any badness in the logs.
>>> Any idea there?  Despite this, I disabled the plugin in conf.pl
>>> and pushed on...
>>
>> http://www.squirrelmail.org/wiki/BlankPage
>
> Thanks.
>
> The relevant portion of error_log reads:
> [client x.x.x.x] PHP Fatal error:  Call to undefined function:
> sq_change_text_domain() in
> /usr/share/squirrelmail/plugins/change_passwd/functions.php on line 26,
> referer: http://mail.netlinkrg.com/src/right_main.php

Compatibility 2.0.7+ is not installed or you are not using SM 1.4.10+.
 I thought you upgraded to the newest?

>>>> When you get it, open chpasswd.c
>>>> and uncomment line 166 and recompile.
>>>
>>> ... to give feedback about this.  I wasn't able to recompile it straight
> on.
>>> Output:
>>> # make chpasswd
>>> cc chpasswd.c -o chpasswd
>>> /tmp/ccE3xlHn.o(.text+0x4b6): In function `main':
>>> : undefined reference to `crypt'
>>> /tmp/ccE3xlHn.o(.text+0x54f): In function `main':
>>> : undefined reference to `crypt'
>>> /tmp/ccE3xlHn.o(.text+0x5fa): In function `main':
>>> : undefined reference to `crypt'
>>> collect2: ld returned 1 exit status
>>>
>>> But when I followed the INSTALL notes for a Solaris box (gcc -lcrypt
>>> -O -o chpasswd chpasswd.c), it did compile.  Dunno if that might tell
>>> you something about my system.
>>>
>>>> This will spill out the
>>>> password that PHP gave to it - make sure it is correct.  If it is the
>>>> same as the password that you use to log into SSH (what does the rest
>>>> of that output look like?), then there may be an issue with the
>>>> crypt() command on your system.  Oh, and I see you are running
>>>> SELinux - make sure you test it once with SELinux completely
>>>> relaxed/disabled.  You can also try step number 3 under
>>>> Troubleshooting (new in the version I am sending, and you can also
>>>> try *TEMPORARILY* setting $confirmOldPass to 0, and see what the
>>>> output of the command is (while that line 166 is still uncommented).
>>>
>>> Right now I can't tell you about the output because of the Options
>>> page problem, but...
>>>
>>> I tried testing from the command line.  Both the original chpasswd and
>>> the recompiled chpasswd worked the same.  They were effective and
>>> returned "The password was modified successfully" after I supplied
> correct entries.
>>>
>>> Troubleshooting #3 (exec_test.php) returns the following, and the
>>> results are the same whether SELinux is enforced or not:
>>>
>>> Testing exec()...
>>> safe_mode =
>>> safe_mode_exec_dir =
>>>
>>> ----------------------------------------------------------------------
>>> return value = 0
>>>
>>> output:
>>> Array
>>> (
>>>    [0] => COPYING
>>>    [1] => INSTALL
>>>    [2] => README
>>>    [3] => change_passwd.pot
>>>    [4] => chpasswd
>>>    [5] => chpasswd.c
>>>    [6] => chpasswd.orig
>>>    [7] => config.php
>>>    [8] => config.sample.php
>>>    [9] => exec_test.php
>>>    [10] => functions.php
>>>    [11] => getpot
>>>    [12] => index.php
>>>    [13] => make_release.sh
>>>    [14] => options.php
>>>    [15] => setup.php
>>>    [16] => version
>>> )
>>>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Christopher J. Hinkle-2]

Paul Lesniewski Sent: Tuesday 22 July 2008 23:15
>On Tue, Jul 22, 2008 at 7:38 PM, Christopher J. Hinkle
<chinkle@...>

>>>> Sent: Monday 07 July 2008 0:53
>>>>>>> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with
>>>>>>> latest patches; Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52;
>>>>>>> PHP 4.3.9; SELinux.
>>>>>> Relevant plugins:
>>> Compatibility 2.0.12; change_passwd 4.3beta1
>>>> [..]
>>>>> Dunno.  Something strange with how the password is being pulled
>>>>> from PHP or the passwd file.  I am going to send you yet another
>>>>> newer version of the plugin offlist.
>>>>
>>>> Thanks for this.  I've installed the new compatibility and
>>>> change_passwd plugins you sent me.  I installed compatibility first
>>>> and had no problems (checked the website, looked fine, was
>>>> functional).  Then I installed the new change_passwd, and all of a
>>>> sudden the Options page is blank.  I disabled the change_passwd
>>>> plugin with conf.pl, and the Options page came back.  I know this
>>>> happened once before, but I can't figure out what I did to fix it --
>>>> it might've been that I installed a different version of
>>>> change_passwd and it came back on its own.  I've turned SELinux off
>>>> and on and it made no difference, and I'm not seeing any badness in the

logs.

>>>> Any idea there?  Despite this, I disabled the plugin in conf.pl and
>>>> pushed on...
>>>
>>> http://www.squirrelmail.org/wiki/BlankPage
>>
>> Thanks.
>>
>> The relevant portion of error_log reads:
>> [client x.x.x.x] PHP Fatal error:  Call to undefined function:
>> sq_change_text_domain() in
>> /usr/share/squirrelmail/plugins/change_passwd/functions.php on line
>> 26,
>> referer: http://mail.netlinkrg.com/src/right_main.php
>
> Compatibility 2.0.7+ is not installed or you are not using SM 1.4.10+.
> I thought you upgraded to the newest?

My current versions are up at the top of the email.  I upgraded the
compatibility, but not SM.  I'm using the RedHat RPM, and they haven't
released a version later than 1.4.8 for my platform, AFAIK.

Sure wish there was a way around putting all these > quotes in manually in
Outlook just so I don't top-post.

chris.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Paul Lesniewski]

On Tue, Jul 22, 2008 at 8:22 PM, Christopher J. Hinkle
<chinkle@...> wrote:

> Paul Lesniewski Sent: Tuesday 22 July 2008 23:15
>>On Tue, Jul 22, 2008 at 7:38 PM, Christopher J. Hinkle
> <chinkle@...>
>>>>> Sent: Monday 07 July 2008 0:53
>>>>>>>> System: SquirrelMail 1.4.8 on RedHat Enterprise Linux 4 with
>>>>>>>> latest patches; Postfix 2.2.10; Dovecot 0.99.11; Apache 2.0.52;
>>>>>>>> PHP 4.3.9; SELinux.
>>>>>>> Relevant plugins:
>>>> Compatibility 2.0.12; change_passwd 4.3beta1
>>>>> [..]
>>>>>> Dunno.  Something strange with how the password is being pulled
>>>>>> from PHP or the passwd file.  I am going to send you yet another
>>>>>> newer version of the plugin offlist.
>>>>>
>>>>> Thanks for this.  I've installed the new compatibility and
>>>>> change_passwd plugins you sent me.  I installed compatibility first
>>>>> and had no problems (checked the website, looked fine, was
>>>>> functional).  Then I installed the new change_passwd, and all of a
>>>>> sudden the Options page is blank.  I disabled the change_passwd
>>>>> plugin with conf.pl, and the Options page came back.  I know this
>>>>> happened once before, but I can't figure out what I did to fix it --
>>>>> it might've been that I installed a different version of
>>>>> change_passwd and it came back on its own.  I've turned SELinux off
>>>>> and on and it made no difference, and I'm not seeing any badness in the
> logs.
>>>>> Any idea there?  Despite this, I disabled the plugin in conf.pl and
>>>>> pushed on...
>>>>
>>>> http://www.squirrelmail.org/wiki/BlankPage
>>>
>>> Thanks.
>>>
>>> The relevant portion of error_log reads:
>>> [client x.x.x.x] PHP Fatal error:  Call to undefined function:
>>> sq_change_text_domain() in
>>> /usr/share/squirrelmail/plugins/change_passwd/functions.php on line
>>> 26,
>>> referer: http://mail.netlinkrg.com/src/right_main.php
>>
>> Compatibility 2.0.7+ is not installed or you are not using SM 1.4.10+.
>> I thought you upgraded to the newest?
>
> My current versions are up at the top of the email.  I upgraded the
> compatibility, but not SM.  I'm using the RedHat RPM, and they haven't
> released a version later than 1.4.8 for my platform, AFAIK.

1.4.8 is OK, as long as the Compatibility plugin is there.  If it is,
I don't know what to tell you.  Make sure that missing function is
actually in the Compatibility plugin you have installed by grepping
for it and put some test code in to make sure that file is being
included correctly, etc.

> Sure wish there was a way around putting all these > quotes in manually in
> Outlook just so I don't top-post.

There should be a setting to change from HTML format to plain text for
outgoing messages, but it's been ages since I've used LookOut(TM).

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins