Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 2 > Tips/Tricks/Mods

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 17th May 2006, 17:00
sfrank sfrank is offline
Junior Member
 
Join Date: May 2006
Posts: 22
Thanks: 0
Thanked 4 Times in 1 Post
Default squirrelmail virtual username solution proposal

hi everyone.

digging the mail archive and the forum i realized that many of us prefer squirrelmail as the webmail option to provide easy access to our customers to their mails using their browsers. i also realized that at this moment ISPConfig developers are way too busy to develop support to squirrelmail in a form so that users don't need to use their 'ugly' web[WEBID]-user format username but username@domain.tld format.

giving it some time i thought of an idea of creating a pam module which translates user@domain.tld according to postfix's virtualuser.db database to real username's with which the client can be authenticated.

please (ISPConfig developers) let me know if there's need for such a feature. i'd not like to work in parallel with you guys.

thanks.
frank

ps: the reason i'm not thinking of writing a squirrelmail auth plugin because in the pam module case other services can make use of this method, such as ftp or imap/pop daemons.
Reply With Quote
Sponsored Links
  #2  
Old 17th May 2006, 17:05
sfrank sfrank is offline
Junior Member
 
Join Date: May 2006
Posts: 22
Thanks: 0
Thanked 4 Times in 1 Post
Default

even better. i have not looked at the mysql database of ISPConfig yet, but if we can keep all the info in mysql (username, password, shell, home dir, etc) leaving /etc/passwd intact we could easily use mysql pam module so none of the existing apps would need to know where they are getting the auth info from.

was this idea already inspected and discarded for performance reasons or other?
Reply With Quote
  #3  
Old 17th May 2006, 21:06
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,741 Times in 2,575 Posts
Default

Quote:
Originally Posted by sfrank
even better. i have not looked at the mysql database of ISPConfig yet, but if we can keep all the info in mysql (username, password, shell, home dir, etc) leaving /etc/passwd intact we could easily use mysql pam module so none of the existing apps would need to know where they are getting the auth info from.

was this idea already inspected and discarded for performance reasons or other?
The passwords aren't stored in the ISPConfig database, they are in /etc/shadow, that's why this solution won't work.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #4  
Old 17th May 2006, 23:07
sfrank sfrank is offline
Junior Member
 
Join Date: May 2006
Posts: 22
Thanks: 0
Thanked 4 Times in 1 Post
Default

Quote:
Originally Posted by falko
The passwords aren't stored in the ISPConfig database, they are in /etc/shadow, that's why this solution won't work.
Any intentions to make it that way in future releases? It'd not be difficult to write a script which copies/moves the already existing user info into the database if an upgrade occures.

But again, if for any reasons you're not a fan of such a solution I accept that. Shall I ask you to comment my first post in this topic too?

Thx in advance.
Frank
Reply With Quote
  #5  
Old 18th May 2006, 07:54
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 36,177
Thanks: 829
Thanked 5,414 Times in 4,257 Posts
 
Default

Quote:
Originally Posted by sfrank
even better. i have not looked at the mysql database of ISPConfig yet, but if we can keep all the info in mysql (username, password, shell, home dir, etc) leaving /etc/passwd intact we could easily use mysql pam module so none of the existing apps would need to know where they are getting the auth info from.

was this idea already inspected and discarded for performance reasons or other?
We have chosen to not store the passwords in mySQL for security reasons.

Also if you keep the passwords in two places you might get problems with synchronization if a password is changed on the shell.

If storing the passwords in DB can be disabled, it will be fine to have a additional PAM module for accessing the data from squirrelmail and other applications.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Virtual users, domains Postfix.. & Squirrelmail laser144 HOWTO-Related Questions 6 4th May 2006 23:23
Squirrelmail on Suse 9.3 rfburn Technical 5 18th February 2006 12:13
postfix config jmroth Installation/Configuration 6 18th September 2005 15:58


All times are GMT +2. The time now is 00:46.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.