seems there is also a patch available instead of installing an Update ...
http://roundcube.net/news/2013…rity-updates-095-and-087/
Posts by fulltilt
-
-
DESCRIPTION:
A vulnerability has been reported in RoundCube Webmail, which can be
exploited by malicious users to manipulate certain data.The vulnerability is caused due to an error when handling the
"_session" parameter (steps/utils/save_pref.inc) during saving
preferences and can be exploited to overwrite configuration settings
and subsequently e.g. conduct SQL injection attacks.Note: This can be exploited to execute arbitrary code in versions
prior to 0.8.7.The vulnerability is reported in versions prior to 0.8.7 and 0.9.5.
SOLUTION:
Update to version 0.8.7 or 0.9.5.PROVIDED AND/OR DISCOVERED BY:
Reported by the vendor.ORIGINAL ADVISORY:
http://roundcube.net/news/2013…rity-updates-095-and-087/ -
Hello Nuxwin,
/etc/php5/conf.d/imap.ini does not exist but php5-imap is installed, this is a standard migration drom ispcp 1.0.7 without any additional packages## edit ##
I have reinstalled php5-imap now it works
apt-get --purge remove php5-imap
apt-get install php5-imap -
what distro are you using? Normally, if you updated correctly, you should have the php5-imap package installed, which is required.yep, php5-imap is available - tested on debian squeeze with RC 4.4
Regards
-
-
It seem that you user cannot longer connect to the MySQL database. If you need online support, PM me.thank you, I have deleted this DB and User now it works ...
tested with latest RC 4.4, great Idea with choosing the rootkit apps -
hier nochmal der ganze Teil des logfiles ...
Code- [Tue Oct 22 13:31:45 2013] [debug] iMSCP::Execute::execute: Execute /usr/bin/dialog --yes-label Continue --backtitle 'i-MSCP - internet Multi Server Control Panel' --title 'i-MSCP 1.1.0-rc4.3 migration dialog' --colors --no-label Abort --msgbox '
- \Z1\ZuispCP database is corrupted\Zn
- Please fix the following errors and try again:
- DBI connect('\''database=;host=localhost'\'','\''pgk_sql '\'',...) failed: Access denied for user '\''pgk_sql '\''@'\''localhost'\'' (using password: YES) at /var/www/imscp/engine/setup/../PerlLib/iMSCP/Database/mysql/mysql.pm line 101
- ' 21 78
- [Tue Oct 22 13:31:58 2013] [debug] iMSCP::Execute::getExitCode: External command exited with value 0
- [Tue Oct 22 13:31:58 2013] [error] main::databaseIntegrityTests:
- DBI connect('database=;host=localhost','pgk_sql ',...) failed: Access denied for user 'pgk_sql '@'localhost' (using password: YES) at /var/www/imscp/engine/setup/../PerlLib/iMSCP/Database/mysql/mysql.pm line 101
- [Tue Oct 22 13:31:58 2013] [debug] iMSCP::Execute::execute: Execute /usr/bin/dialog --yes-label Continue --backtitle 'i-MSCP - internet Multi Server Control Panel' --title 'i-MSCP 1.1.0-rc4.3 migration dialog' --colors --no-label Abort --msgbox '
- \Z1[ERROR]\Zn
- Error while performing step:
- Checking for database integrity
- Error was:
- \Z1main::databaseIntegrityTests:
- DBI connect('\''database=;host=localhost'\'','\''pgk_sql '\'',...) failed: Access denied for user '\''pgk_sql '\''@'\''localhost'\'' (using password: YES) at /var/www/imscp/engine/setup/../PerlLib/iMSCP/Database/mysql/mysql.pm line 101
- \Zn
- Please, post on http://i-mscp.net/forum to get any help.
- ' 21 78
- [Tue Oct 22 13:32:01 2013] [debug] iMSCP::Execute::getExitCode: External command exited with value 0
- [Tue Oct 22 13:32:01 2013] [error] iMSCP::Debug::END: Exit code: 1
-
anfangs fing alles mit Facebook Mails an, diese wurden von PW geblockt, habe dann die Mailadresse und Wildcard Domain in die Whitelist gesetzt:
notification+[email protected] OK
*@facebook.com OK
*.facebook.com OK
mx-out.facebook.com OK
outmail036.prn2.facebook.com OKpostmap hash:recipient_access
steht ganz oben:
smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/recipient_access
....
reject_non_fqdn_recipient,
....
das ging auch ein paar Tage gut, dann wurde es wieder blockiert ...
mitlerweile blockiert es auch meine beiden anderen Server die ebenfalls in der Whitlist stehen (keine sys. mails z.b. von monit usw mehr möglich).Es scheint das policyd-weight die whitlist einfach ignoriert ...
hat noch jemand eine Idee oder bleibt nur PW aus der main.cf rauszunehmen?
[hr]
habs hinbekommen, hoffe ichdie alte /etc/policyd-weight.conf gelöscht
policyd-weight defaults > /etc/policyd-weight.conf
/etc/init.d/policyd-weight restart
/etc/init.d/postfix reloaddiese configs waren beide gleich ... warum auch immer, jetzt geths wieder
-
Von welcher auf welche version???Hi Goover, ich habe von gestern das Git Master verwendet und ispcp 1.0.7
ist in der aktuellen RC das gefixte Migrationsscript bereits enthalten? -
teste gerade ebenfalls eine ispcp Migration mit dem Master, dabei kommt es nach Schritt 2 zu folgendem Fehler:
ist das Problem bekannt?