the files in the backup directory have chmod 0640 also not visible for the user they should have 0644 to be visible and downloadable for the user
What version you are using ? I cannot confirm with latest master:
the files in the backup directory have chmod 0640 also not visible for the user they should have 0644 to be visible and downloadable for the user
What version you are using ? I cannot confirm with latest master:
On other side, if you have an older backup for your domain data, you can still restore them via FTP and use PhpMyAdmin for databases. About the automation for backup, I think we must let the door closed to prevent any security issues. But right again, is not the subject here.
Hello folks;
SSL with optional SNI support is on the road and is planned for RC1. It's the hard task for Daniel (sci2tech) for our next release. We talked a lot about it implementation yesterday on IRC.
Note: SNI support will still optional since like you said: "is supported by the major browsers/client-side SSL libraries and servers, with the notable exception of IE on Windows XP (Vista or later is working)"
Its not useless since normally, with permissions set to root:root 0755 you can reach the directory via Ftp. Those permissions are restricted here to prevent user to remove the directory.
Thanks for report. We will check and fix ASAP.
It's with great pleasure that we announce the immediate availability of the <strong>i-MSCP 1.0.1.5</strong> version that is our fifth beta release. This new release comes with a lot of improvement such as complete rewrite of engine.
<strong>New features and enhancements in this release:</strong>
<ul class="bulletlist">
<li>Auto-installer (including both tree builder and setup based on Dialog)</li>
<li>Dovecot Support</li>
<li>Engine rewrite including the following new features:
<ul>
<li>Ability to turn off one or many services/servers such as Apache, bind9, Postfix...</li>
<li>Ability to setup DNS service (Bind9) as Master or Slave server</li>
<li>New logger (one file per operation)</li>
<li>php.ini per user account (default), or per domain entity (vhost)</li>
</ul>
<li>IPv6 support</li>
<li>PHP directives editor</li>
</ul>
Furthermore, several bugs and security issues were fixed, and all language files were synchronized with the last available versions on <a href="https://www.transifex.net/projects/p/i-MSCP/resource/imscppot/"><strong>Transifex</strong></a>.
To learn more about bugs and other issues fixed in this release, please consult the <a href="https://github.com/i-MSCP/imscp/blob/151d40110d5e7ab329c5280afa7c4d248d06a259/CHANGELOG" target="_blank"><strong>CHANGELOG</strong></a>.
We would like to remind you that this version should not be used in a production environment, and that any bugs found should be reported on our issues tracker.
Feel free to test this new version and get in touch with us about any improvement that you would like see integrated.
You can download i-MSCP 1.0.1-5 Beta 5 at <a href="https://sourceforge.net/projects/i-mscp/files/i-MSCP%201.0.1.5/">https://sourceforge.net/projec…cp/files/i-MSCP%201.0.1.5</a>
<strong>i-MSCP Team</strong>
Preview for the client part:
i-mscp.net/wcf/attachment/219/
Database schema, Config and Engine parts are finished. I must now finish GUI.
Thanks you.
Hello ;
I know well openSUSE since I've provided support for ispcp in past. If you are able to provide a patch for imscp, feel free.
Our plan is to support Debian/Ubuntu as primary distros for i-MSCP and when we will be in stable state, we will add support for some other distro. You can do a request to join our team as openSUSE maintainer if you want.
See http://trac.i-mscp.net/ticket/236
Any feedback is welcome. Idea is coming in my brain after talking with Christian (Joximu) on IRC about the greylisting feature like implemented in forked project and i-MSCP.
Edit: Copy made on public section to allow our members to provide their feedback.