by GL_Support, 2 days ago
Flagship Industries has just released an upgrade to the Ventrilo Server. We have made the upgrade available to everyone at this time.
We HIGHLY suggest you upgrade your Ventrilo servers immediately using the upgrade option in the web Control Panel. One of the things this update fixes is a server crash exploit. An exploit tool was released into the wild earlier this week that crashes Ventrilo Servers. We believe this exploit is responsible for some odd reports of erratic Ventrilo issues and disconnects that some users have been encountering.
This server upgrade does not require a client upgrade. Your users will not need to install or configure new software.
When a lower-versioned server is the selected server in the Control Panel, a SERVER UPGRADE message will be displayed right above the "Server Information" section (just below the "News" section). Everyone can perform their own upgrades at their convenience. All servers that are not upgraded by the evening of Friday, August 22, 2008 (US EDT), will be upgraded sometime that Friday evening and the following Monday morning (we typically do them all Saturday morning).
The update also adds 2 new features, configurable in the Control Panel by clicking "Configuration":
NoLoginLimit=4
NoLoginTrigger=0
NoLoginLimit:
The determines how many concurrent TCP connections may exist from the same IP that have not performed an official login sequence. Anything over this number from the same IP will be automatically disconnected and there will be no log entry stating as such in order to prevent log spamming. A value of 0 will disable this connection spamming feature entirely should you absolutely need it.
If you have many users coming from the same IP, such as a corporate office, then you may need to increase this value. It’s all about probabilities that X number of connections would be not logged in all at the same time.
NoLoginTrigger:
This determines how many times a NoLoginLimit each triggered for any specific IP. If the NoLoginLimt for an IP is triggered this many times then the server will automatically add that IP to the temporary ban list for 5 minutes. This will further help to reduce log spamming. Difference is, once it is on the temporary ban list you will get a log entry every 10 seconds stating how many times they have tried to abuse it, but this log entry is nothing new. It’s been there going back to 2.3 I do believe.
Setting NoLoginTrigger to 0 will disable the feature of adding the IP to the temporary ban list. If NoLiginLimit is to 0 then this feature has no meaning.
Enjoy!
Stephen
by GL_Support, 2 days ago
Part of the 4.8 Release is a change to the paging of messages in the Private Message area. The change is relatively small code wise and doesn't effect other areas so I have gone ahead and hotfixed this functionality.
The new functionality removes the numbered items from the bottom of the PMs and replaces it with a "Next" "Previous" and "First" style of link. The reason for this is that we're no longer counting the total number of PMs. The count was causing performance issues and it was for the most part unecessary. This is similar to the way Google handles message paging in GMail.
A future release will include some more PM search functions which will remove the need to page even more.
-Stephen
by GL_Support, 2 days ago
Due to changes in the behavior of Auto Logins as well as user sessions when we release Version 4.8 at the end of this month all Auto Logins will be invalidated. This means you will have to log back in and choose "Keep Me Logged In" again.
If you are using Auto Login, please ensure you know your password. You can change it on your My User Page to ensure you know what it is currently.
In addition any active logins will be logged out when Version 4.8 is released.
We're sorry for the inconvenience, but these changes are to add functionality to the login system in Version 4.8 as well as to increase security.
-Stephen
by GL_Support, 3 days ago
We're gearing back up testing for a pending 4.8 release, and I have some more sneak peak info. The following is a picture of the new optional "Applicant Availability" info for guild applications. When you enable this feature the user is asked what days they are usually available to play. The display for the Pending Applications is like this:
This feature isn't for every guild, but if you get alot of applications and have to be very selective then raid availability might be a key factor in who you let into your guild.
In addition to these features version 4.8 includes alot of refinements and tweaks to existing functionality based on user feedback. We'll have more detail in the release notes.
Enjoy!
Stephen
