Jump to content
Froxlor Forum

d00p

Administrators
  • Posts

    10328
  • Joined

  • Last visited

  • Days Won

    43

Posts posted by d00p

  1. Dear Community,

     

    due to the stable release of Debian 7 "Wheezy" we decided to defer implementing the "dualstack / multi-ip" feature in favor of support for Debian Wheezy as many users already upgraded their installation.

     

    So to cut it short:

     

    upcoming 0.9.29:

    • support for Debian Weezy 
    • fix problem with paths that contain spaces
    • a few fixes for nginx users
    • possiblity to hide standard-subdomains in php-config overview
    • correction of domain-validating (if an IP is given)

    following 0.9.29.1:

    • support for multiple IP's per domain (ipv4 and ipv6)
    • more tiny fixes if needed
    • small features that are targeted to 0.9.29.1 of course

    ?

    Thanks for you patience and feel free to test multi-ip-support even now using the tilman19-master branch in our git-repository. Join us on IRC, get in touch with us and participate ;-) It's what froxlor lives off (mostly) :P

     

    d00p

  2. Dear Froxlor Community,
     
    the release candidate of version 0.9.28 has been released a month ago and thanks to a bunch of community users for testing and reporting, a lot of bugfixes found their way into this release and we are proud to announce a new stable release of Froxlor: 0.9.28
     
    The upcoming release-candidates, followed by a stable release, of version 0.9.29 will include improved SSL-support and IPv4/IPv6 dual-stack support as announced earlier.
    Also you might have noticed that we started to work on our new version tree 0.99 which will be API based. It's under heavy development and still in its beginnings.
     
    As we probably will not be finished with 0.99 after 0.9.29 is released, depending on bug-reports or similar, there will of course be another maintenaince release of 0.9.x if necessary.
     
    As announced in the release-candidate thread, support for php's safe_mode, mod_log_sql and Debian Lenny has been removed in this release. Also, Ubuntu Hardy completely and dovecot-1 on Gentoo have been marked as deprecated as they will be removed in 0.9.29.
     
    Please report bugs/errors in the bugtracker (http://redmine.froxlor.org) as usual.
     
    Changes in 0.9.28:

    + #536 Use complete domain name as default path for DocumentRoot
    
    + #1150 added possibility to add random prefixes to a customers database-name
    
    
    ~ #668 fixed FreeBSD 8.2: Bind 9 is missing from list of Daemons
    
    ~ #758 fixed bug in "Amount of APS installations" counter
    
    ~ #916 fixed webserver-specific default vHost settings don't work in ligHTTPd
    
    ~ #1023 fixed Redirect with SSL Enabled Domain
    
    ~ #1058 fixed bug in "Amount of autoresponders" counter
    
    ~ #1085 fixed incorrect configuration command for awstats under Gentoo
    
    ~ #1127 fixed falsely used e-mail sender name
    
    ~ #1134 updated default parameter list of sendmail-program in php.ini-template
    
    ~ #1136 fixed falsely added specialsettings to a ssl-redirect
    
    ~ #1160 fixed usage of empty value for CertificateChainFile (it's allowed)
    
    ~ #1172 cleaned up language files
    
    ~ #1173 fixed redirect to "ip:port"
    
    ~ #1180 fixed clean-up if fcgid/php-fpm configurations
    

     
    Important information: 
    The configurations for postfix on FreeBSD have been updated. Please check using http://config.froxlor.org/.

    Update: Due to a syntax-error in the updater we had to re-release as version 0.9.28.1 - for all who got stupid errors on updating, we are sorry :/

    Download: froxlor 0.9.28.1
     
    Note: Debian packages and the Gentoo ebuild will follow shortly.
     
    Visit http://www.froxlor.org or join our IRC channel #froxlor on irc.freenode.net.
     
    Thank you,
    d00p

  3. Dear Froxlor Community,

     

    it has now been a week since I took over the leadership of the project. Besides the survey, which will help setting the development focus of future releases, the goal was to review the changes made in GIT since the last release to publish a new version of Froxlor including a bunch of bugfixes and changes.

     

    One of the bigger changes is the complete switch to UTF-8 (see #1117).

    As this also includes the database we strongly recommened to backup your database before updating.

     

    Future releases and plans: The next stable release will be 0.9.28 of course. Followed by a maintenance version called 0.9.29.

    During that time, some major rework will take place which will lead to a new version-tree called 0.99 (starting with 0.99.0). Main focus will be set on code-cleaning, improving SSL-support and IPv4/IPv6 dualstack (as these two are the first two places on the most-used-feature-list from the survey).

     

    Also, some features will be marked as "unstable" or similar, which does not mean they are going to be removed, but that they need a major rework and are likely to not work properly. It is not yet decided what features will be on that list. Feel free to discuss in our IRC-Channel on freenode.

     

    Please report bugs/errors in the bugtracker (http://redmine.froxlor.org) as usual. There will be no more new features in 0.9.28.

     

    Changes in 0.9.28-rc1:

    + #1064 customers are now able to search their email-addresses in the overview (like domains, etc.)
    
    + #1103 new directory-structure for e-mail accounts. 
      New added accounts will be stored in a new maildir-structure (e.g.   
      /var/customers/mail/<customeracc>/<domain>/<mailacc>/Maildir/).   
      An explanation why this makes sense can be found in the ticket-description. Note: no configuration changes are necessary 
      and existing accounts do not need to be updated, as the homedir/maildir is read from the database.
    
    + #1107 the default language for users without a language-setting is now determined via HTTP_ACCEPT_LANGUAGE
    
    + #1138 added support for apache-2.4 (note: mod_log_sql is not compatible to apache-2.4)
    
    + #1153 path to nginx's fastcgi_params-file is now customizable 
      (as other distributions/systems do not have it in /etc/nginx/)
    
     
    ~ #1067 fixed alias generation when the docroot of a (sub)domain was below the customerdocroot
    
    ~ #1068 Apply settings for all subdomains in now deactivateable 
      (but will be checked when you re-open the domain-edit view, this is intended!)
    
    ~ #1075 the default php-cgi listener for nginx is now editable as intended 
    
    ~ #1079 php-fpm files are generated correctly - due to a double "cleaning" of the php-cgi-configdir, 
      they were created and later removed in the cronjobs
    
    ~ #1089 + #1118 fixed php-fpm usage on apache-webserver
    
    ~ #1095 fixed incorrect display of used traffic in admin-overview
    
    ~ #1097 fixed falsey used private class property in database-class
    
    ~ #1104 fixed endless-loop in readdir() when bind is not installed but php-fpm is activated
    
    ~ #1108 fixed problems when disabling a customer / the customer removes one of his database with mysql version >4.1
    
    ~ #1117 froxlor is now completely using UTF-8 encoding.
    
    
    x #1119 The classic theme has been removed. 
      Maintaining two very different themes and the goal to gain usability and simplicity lead to that decision.
    
     

    Important information: 

    • support for mod_log_sql will drop in the final 0.9.28 release. If you still use it, please switch to webalizer or awstats
    • support for dovecot-1 on Gentoo will be dropped in 0.9.29 as Gentoo's tree does not include it anymore.
    • support for Debian Lenny has been removed as it is EOL since 6.2.2012.
    • support for Ubuntu Hardy will be deprecated in 0.9.28 and removed in 0.9.29 as it will be unsupported in april 2013.
    • php's safe_mode setting will be removed in the final 0.9.28 release as it is deprecated.
    Download: 0.9.28-rc1

     

    Note: As this is a release candidate, there will be no Debian packages and no new Gentoo ebuild for this.

     

    Visit http://www.froxlor.org or join our IRC channel #froxlor on irc.freenode.net.

     

    Thank you,

    d00p

    • Like 38
  4. This is the result after 150 participants - thank you very much. The interpretation will follow in the announcement of the next release. You are welcome to join a discussion about the survey-results in our IRC-channel #froxlor on freenode.net.
     
    1. What operating systems are you using in your server(s)?

    • 74,66% - Debian
    • 2133% - Ubuntu
    • 8,66% - Gentoo
    •  3,33% - Other
    •  2,66% - Redhat
    •   2% - SuSe
    •   2% - BSD

     

    2. What webserver are you using?

    • 64% - Apache-2.2
    • 44,66% - Apache-2.4
    • 24% - Nginx
    • 13,33% - Lighttpd
    •   <1% - Other

     

    3. Are you using your own nameservers and the Froxlor generated DNS-configurations?

    • 62,9% - No
    • 37,1% - Yes

     

    4. Feature usage/importance (by average rating 1 - 4)

    • 3,79 - SSL
    • 3,68 - IPv6
    • 3,64 - proftpd
    • 3,60 - quota
    • 3,57 - dovecot
    • 3,50 - fcgid
    • 3,43 - php-fpm
    • 3,28 - SNI
    • 3,26 - built-in backup-solution
    • 3,21 - domainkeys
    • 2,98 - perl/cgi
    • 2,85 - bind
    • 2,74 - nginx
    • 2,74 - courier
    • 2,72 - custom-dns
    • 2,69 - pureftpd
    • 2,61 - ticket-system
    • 2,39 - APS
    • 2,37 - lighttpd
    • 2,36 - newsletter-system
    • 2,26 - PowerDNS
    • Like 27
  5. Dear Froxlor Community,

     

    as of today Froxlor is under new management. Due to time issues the former developers decided that this would be the best solution to keep Froxlor a good piece of open software. Many of you might already know that I myself once was part of the developer team for quite some time and so I return as the new project leader.

     

    There is lots to do and I know that many of you are waiting desperately for new releases, new features and bugfixes but please don't expect too much in the near future as there are many things that have to be done before releasing anything. Mainly administrative work with the servers and infrastructure and organization.

     

    First of all, I would like the community to participate in an online survey I've created, so we all can decide where Froxlor is going in the future and on which features the focus will be. Secondly, when I have enough response from the survey there will be a lot of code-cleaning and feature-removal (those that aren't used or too buggy to maintain).

     


     

    I want Froxlor to be a panel for "common" administrators. No super special features only a few of you will use (that can be handled with some kind of module-interface later on). That's why I am going to focus on the most used and most important features.

     

    Followed by that I'll try to reduce as much duplicate code as possible to decrease the number of potential error-sources. In addition to that I will convert as much functional code as possible into OOP (where possible) and therefore increase manageability. This will make it easier to develop good interfaces for modules/extensions/etc.

     

    Regarding the current bugtracker tickets: Not all bugs will be fixed and not all feature-requests will find their way into Froxlor. As said, I want Froxlor to be a help for common server-admins. Please don't get angry with me if several tickets going to get deleted or marked as invalid.

     

    Let's hope that we all can bring Froxlor back to life together to enjoy this great administration panel ;)

     

    Edit: Information about the survey results so far can be found here Froxlor feature survey results

     

    Greetings

    d00p

    • Like 23
  6. Froxlor it not only for Debian, and maintaining this amount of packages i a lot of work, also not only the webserver changes - there can also be other mailserver-services and ftp-services, etc. would you want to maintain all these packages? froxlor-nginx-courier-proftpd - froxlor-nginx-courier-pureftpd, froxlor-nginx-dovecot-proftpd...etc.etc.etc.

  7. Hello Froxlor-community and worried users,

     

    as there were a lot of noise regarding this "security issue" which initially came from

    php-friends.de i contacted them to ask where the problem is.

     

    They did answer me and gave a bit of information where a possible leak could exist in the Froxlor code. They told me to keep this confidential so I won't tell any details.

     

    To reassure you Dessa and I tested the situation with the given information and there is actually no possibility this particular "problem" is a security issue in Froxlor. Whether using mod_php nor using fcgid.

     

    To be clear: we have only tested a particular problem which we got information about by php-friends. I don't know if there is more or whether this was the only security issue php-friends found.

     

    regards

    d00p

    • Like 1
  8. Only the old theme is broken, in main.css all images are linked as

    /images/Classic....
    

     

    but it needs to be

     

    ../../images/Classic....
    

     

    No.

    If you use leading slashes, it always reads from the docroot. At least it did on our testservers

  9. Dear Froxies,

     

    as of this months, Februrary 2011, we've switched our source repository from SVN (subversion) to GIT (http://git-scm.com/).

     

    This arranges the repository as follows:

     

    Anonymous read-only access is provided via git://git.froxlor.org/froxlor.git and http://git.froxlor.org/froxlor.git'>http://git.froxlor.org/froxlor.git.

     

    The Froxlor GIT - repository may be browsed with the webinterface installed on http://git.froxlor.org

     

    If you want to contribute, you no longer need your own branch nor svn-access. Just clone our repository, make your changes, and create a patch using git format-patch origin/master. If you want to make our lives even easier, use git send-email to directly send us your patches vie e-mail. If you want to know more, join us on IRC (irc.freenode.net/#froxlor).

     

    Some more detailed information will be published on http://wiki.froxlor.org/doc/git these days.

     

    That's about it for now.

     

    d00p and the Froxlor-team

×
×
  • Create New...