newFilemanager Upload page shows size limit (SKINS)
Added 2 global tokens
|MAX_FILE_SIZE| - max number of bytes allowed to be uploaded |MAX_FILE_SIZE_STR| - string representatiuon (ie: "10.0 Mb")
Enhanced skins - lang/en/user/filemanager/upload.html
newApache 2.0 system
Firstly, this will not change the version of apache you are running unless you want it to. It requires the running of several commands to do it, so you don't need to worry about anything being changed.
The only real change to DA is how the httpd.conf files are written. You can let DA know to use the apache 2 files by setting "apache_ver=2.0" in your directadmin.conf file, but the convertor will do that for you anyway.
virtual_host2.conf virtual_host2_sub.conf virtual_host2_secure.conf virtual_host2_secure_sub.conf
The only real difference being the replacement of User and Group with
Once you've got this version of DA, you'll be able to update to apache 2 by updating the build script and installing apache 2. The script will convert your main httpd.conf file and recompile apache/php/mod_frontpage etc for you. It will also set the required DA settings and rewrite all user httpd.conf files to apache 2.
To get and build apache 2.0, run the following:
cd /usr/local/directadmin/customapache ./build update ./build clean ./build update_data_ap2 ./build convert ./build apache_2 ./build php_ap2 n ./build mod_frontpage_ap2 ./build mod_perl_ap2
newMoved sessions directory
Moving the sessions out of /home/tmp to it's own private directory in /usr/local/directadmin/data/sessions (chmod 700, diradmin:diradmin)
The option for the directadmin.conf will be "sessions_dir", and will default to /usr/local/directadmin/data/sessions if nothing is set in the directadmin.conf (sessions_dir will not be in the directadmin.conf by default). The only reason you'd need to add it to the directadmin.conf would be if you need the session files to be in /home/tmp.
Due to the directory move, an update of DA will log out anyone currently logged in because the session files won't be moved. A simple re-login will log you back in. The "logout on update" will only affect this update.
The /usr/local/directadmin/data/sessions directory will be created automatically if it doesn't exist.
API commands that use sessions files won't be affected, they'll continue to work normally.
newOption to disable IP check for sessions
By default, the IP will be checked for each request to ensure that the caller is who he says he is.
For some clients, their IP is changed between requests, preventing them from using DA.
This feature will allow a server admin to disable the IP check for sessions.
Note that this is removing one layer of security, so keep that in mind you decide to use it.
Note that for comparison, php session do not have this extra layer, so disabling it would make it more similar to other session-based tools.
/usr/local/directadmin/directadmin set disable_ip_check 1 service directadmin restart
newcustom subdomain creation/deletion scripts
subdomain_create_pre.sh - Runs BEFORE a subdomain is created, but after it's confirmed. If this script returns a non-zero value, the creation is aborted. subdomain_create_post.sh - Runs AFTER the subdomain is created. subdomain_destroy_pre.sh - Runs BEFORE a subdomain is destroyed. If this script returns a non-zero value, the destruction is aborted subdomain_destroy_post.sh - Runs AFTER the subdomain is destroyed.
username=ownerofdomain domain=domain.com subdomain=sub contents=1 or 0 - only for destroy. Specifies that the directory and contents are being removed.
fixedda-popb4smtp doesn't handle virtual pop logins
The new format is:
Jul 21 16:02:49 server vm-pop3d: User 'admin' logged in from 188.8.131.52, nmsgs=0
da-popb4smtp was setup to handle that, but this fix allows it to handle this as well:
Oct 22 13:06:09 server vm-pop3d: User 'user' of 'domain.com' logged in from 184.108.40.206, nmsgs=1