Il giorno dom, 30/10/2011 alle 13.27 +0000, Jeroen van Meeuwen (Kolab Systems) ha scritto: > You could use the "primary" account password to encrypt the > "secondary" > IMAP account(s) password(s) with, and store that encrypted version, > perhaps.
Good idea, I think that this approach is safe. Anyway, today I edited some Roundcube script: first I deleted completely the $IMAP global variable (ok this is going to break functionality, please read bottom), then I modified the RCMAIL::$imap attribute from object (rcube_imap) to array (of rcube_imap), then I added the attribute RCMAIL::$serverIndex to use as server index. For now I'm forcing $serverIndex to zero, so we have only one connection. I've downloaded the latest trunk revision. My edits in the attached diff. Please note that this approach will break plugin (and more) that use rcmail::$imap object. I've modified everything in the Subversion repository directory "roundcubemail" (under trunk) except for "installer", but we have dozen of external plugin that can be affected by this change. If we need to be backward compatible even for RCMAIL::$imap object, the approach need to be different (maybe RCMAIL::$imap should be the selected IMAP connection picked from the array). Please tell me what do you think ;-) Enrico --- 8< --- detachments --- 8< --- The following attachments have been detached and are available for viewing. http://detached.gigo.com/rc/Kj/OQiEvoH0/rctest.diff.gz http://detached.gigo.com/rc/Kj/OQiEvoH0/signature.asc Only click these links if you trust the sender, as well as this message. --- 8< --- detachments --- 8< ---
_______________________________________________ List info: http://lists.roundcube.net/dev/ BT/8f4f07cd
