| BufferOverflow | Date: Saturday, 16.02.2013, 23:26 | Message # 1 |
Group: Developer
Messages: 47
Status: Offline
| New version is released. Bugs fixed:
1) Chat Flood. Allowing to kick anyone or everyone with "Lost reliable commands" message.
2) q3dirtrav fix bug. Suddenly, but previous JASS version wasn't protection from .cfg downloading completely. Now you can turn sv_allowdownload 1 safely again.
3) Line breaks in chat and nick. I was known about this bug a lot time ago, but only now it seems needed to be fixed (it isn't critical bug anyway).
Also I've added new feature: cmd logging. See jass.ini for details. You can use it to detect new advisories. Recommended to use with "log" '2'.
JASS v3.1.0. win32
JASS v3.1.0. linux
Thanks to: Thedt, WEAPON_X, Sweet, Dark Angel.
Btw, someones tolds that JASS not protects against InfoBof (getinfo/getstatus crash). It's not true (at least for basejka). If you've used q3infoboom.exe on JASS-protected server and got message "Server is vulnerable", don't think that it is truly vulnerable. Server not responding you not becouse it's offline, but because JASS banned you  .
P.S. About jass_forceAntiDDoS and jass_forceOtherFixes. JASS puts it's fixes carefully, and if something goes wrong, does not put fix and prints:
Use cvars "jass_forceAntiDDoS" and "jass_forceOtherFixes" to force it, but on your own risk
It means that you hadn't installed patch 1.0.1. or you have ignored the requirement of "Only the original unmodified exe." Most likely, JASS came across the another fixes. JASS will install any non-conflict fix anyway. Yet it is possible to force JASS to put fixes even in the event of a conflict using these two cvars. But remember, this decision could lead to server crash.
|
| |
| |
