[SOLVED] SquirrelMail Plugin broked

[bitstorm]

Guys, something has changed in ISPCP/MySQL on latest version?

I had two systems Debian Etch/ISPCP_RC2 and Debian Etch/ISPCP_RC3. After upgrade to Debian Lenny/ISPCP_1.0 this weekend my change_pass plugin of squirrelmail broked... I get this error while trying to change an password:

Quote:Problem detected: 0 accounts found
Your old password does not match

In time: The old password given is correct!

And when I enable "$csp_debug" I get:

Quote:Password query result is: 0
Query was: SELECT DISTINCT t1.`mail_id` FROM `mail_users` t1 LEFT JOIN `domain` t2 USING ( `domain_id` ) LEFT JOIN `domain_aliasses` t3 USING ( `domain_id` ) LEFT JOIN `subdomain` t4 USING ( `domain_id` ) WHERE t1.`mail_acc` = 'teste' AND t1.`mail_pass` = '123teste' AND (( t1.`mail_type` = 'normal_mail' AND t2.`domain_name` = 'teste.com.br' ) OR ( t1.`mail_type` = 'alias_mail' AND t3.`alias_name` = 'teste.com.br' AND t3.`alias_id` = t1.`sub_id` ) OR ( t1.`mail_type` = 'subdom_mail' AND CONCAT( t4.`subdomain_name`, '.', t2.`domain_name` ) = 'brasmoto.com.br' AND t4.`subdomain_id` = t1.`sub_id` ) )

I installed this plugin following this howto from documentation: change_webmailpass
And works well until this upgrade... any light?

[BeNe]

The Passwords are now crypted!
The Community created a working Version in RoundCube --> http://www.isp-control.net/documentation...r_optional

Greez BeNe

[kilburn]

Here's a working version of the change_sqlpass plugin. Usage:

1. Backup your current plugin, just in case...
2. Unzip the attached .tar.gz to the squirrelmail's plugins directory
3. Replace the mysql user/password by the correct ones in the $csp_dns variable inside config.php
4. Change any other options you want in this config.php file
5. Enable the plugin in the squirrel's config
6. ...
7. Profit!

I've no time to explain the modifications that I've made, but you can easily see them diff'ing against the old version.

Cheers!

[bitstorm]

Wow.... WORKS!!!! Tons of thanks to you, kilburn!!!!!

Its an good idea to update the tutorial at "How-to" wiki... will help many fingerless sysadmins as I am!

Obs.: BeNe, roundcube is an good option, but my users(+4k) loves squirrelmail...

[soho]

Thanks kilburn!!

I'm working with ispCp 1.0 and your mod change_sqlpass worked perfect.

[BeNe]

Killburn, do you see a way to get this feature in the trunk without big problems ?

Greez BeNe

[kilburn]

There are two tasks I can think of to make this upstream:
1) We must create a new mysql user that only has permission to read the mail-related tables and write to the password field (and setup the module accordingly)
2) We should come up with a way to synchronize the module restrictions regarding allowed passwords (must have alphanumeric characters, numbers, etc.) with the one chosen in the panel.

Any ideas?

[BeNe]

Quote:1) We must create a new mysql user that only has permission to read the mail-related tables and write to the password field (and setup the module accordingly)

This will make it more secure. We can create the MySQL-User, something like "vmail" during the install. But we need this also in the Upgrade Script. So there is a check needed.

Quote:2) We should come up with a way to synchronize the module restrictions regarding allowed passwords (must have alphanumeric characters, numbers, etc.) with the one chosen in the panel.

You mean the Strong Password Option, right ?

Greez BeNe

[soho]

(05-06-2009 03:43 PM)BeNe Wrote:  ...

Quote:2) We should come up with a way to synchronize the module restrictions regarding allowed passwords (must have alphanumeric characters, numbers, etc.) with the one chosen in the panel.

You mean the Strong Password Option, right ?

Greez BeNe

I think this is the case, but in change_sqlpass should be adjusted too. The standard is set that is more demanding than the ispCP. It required a combination containing characters in uppercase characters to lowercase, and numbers.

[kilburn]

Yeah, I meant synchronizing this module with the restrictions enforced by the "Strong Passwords" option. By the way, the whole module could use some serious revision, because if we adapt it and ship our own version there's no need for customizable queries and such.

I'll take a closer look at it...