ispCP Omega 1.0.6 Release

[RatS]

The ispCP Team would like to announce the immediate availability of ispCP ω 1.0.6. This release fixes two vulnerabilities:

- Users are able to change into other user's phpMyAdmin account and browse, manipulate or delete their databases and
- ispCP Omega's database password can be looked up from logs.

Make sure you install this update to keep your server secure.
In addition delete all log files within /var/log/ispcp/ispcp-*.

ispCP Omega is an open source solution to all your web hosting needs. You can download the latest stable release from the downloads section. Before you download ispCP, please browse through our comprehensive ispCP documentation section and review the System Requirements, Installing ispCP, Frequently Asked Questions and HowTo's.

We would like to thank our community for all the support. We are constantly looking for developers, translators and maintainers for the various distros supported by ispCP Omega.

1. Maintainers: ispCP Omega is available for CentOS, Debian, Fedora, FreeBSD, Gentoo, OpenBSD, OpenSuse, RedHat, Slackware, Suse and Ubuntu. We require experts with knowledge of the distros above who can help us maintain ispCP for each and every release. If you want to join a dynamic open source project as a maintainer, please make your intention known at the forum.

2. Translators: ispCP Omega is already available in a variety of native languages. We are still seeking experts to help us in translating ispCP to many more languages. We also ask the community to review existing translations and help us make any corrections or amendments via the forum.

3. Developers: ispCP Omega is a large project with ambitious goals and milestones. We are always on the hunt for talented developers to join our family of programmers, administrators and future visionaries. We need developers competent in the following technologies: AJAX, C, CGI, Perl, PHP, MySQL. If you want to join a growing team of professional volunteers working on ispCP, please approach us via our forum.

4. Supporter: Support ispCP with your donations. Every amount helps us towards our hosting fees, legal and public relations budget as well as setting up special events and workshops.

[Rafioso]

You realy mean "/var/log/ispcp/ispcp-*", or mean you "/var/log/ispcp/ispcp_*".

[Nuxwin]

Code:

# rm /var/log/ispcp/*

Will work too. Don't take care about the warn.

[Rafioso]

Done, thx

[joximu]

hm... I'd rather leave the *.prev files - I think they are used for the counting...

so a rm /var/log/ispcp* should be okay...

/J

[Nuxwin]

log *.prev in /var/log/ispcp ? are you sure ?

[kilburn]

Quote:hm... I'd rather leave the *.prev files - I think they are used for the counting...

Not anymore. The *prev files can be safely removed, as ispcp doesn't use them since 1.0.5. This release introduced a lot of stats-related improvements, and uses a single /var/log/ispcp/logdb file to manage the whole counting stuff. Hence, if you don't want to re-count the last day's stats, keep this file when cleaning up the folder

[Nuxwin]

(08-09-2010 06:02 PM)kilburn Wrote:  

Quote:hm... I'd rather leave the *.prev files - I think they are used for the counting...

Not anymore. The *prev files can be safely removed, as ispcp doesn't use them since 1.0.5. This release introduced a lot of stats-related improvements, and uses a single /var/log/ispcp/logdb file to manage the whole counting stuff. Hence, if you don't want to re-count the last day's stats, keep this file when cleaning up the folder

[joximu]

thanx for clearing this killburn!

[kingxerxes]

i though that 1.0.6 was going to fix the issues with manual DNS entries?