lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3F130A66.2070204@midnightryder.com>
Date: Mon, 14 Jul 2003 14:54:14 -0500
From: "Davis Ray Sickmon, Jr" <midryder@...nightryder.com>
To: bugtraq@...urityfocus.com
Subject: Re: StarSiege: Tribes DoS


I'll add further information to this...

Part of StarSiege spawned Tribes 2, which is where Dynamix dissolved 
after being purchased by Sierra.  (In France?  WFT?  Dynamix was located 
in the US.)

Since then, another company now owns the Tribes 2 engine - Garage Games 
(http://www.garagegames.com) They took it, and stripped it of all the T2 
IP, and relicensed it to Indie game developers under the title of Torque 
(really nice engine with a great license scheme - I'm a licensee and 
getting close to completion of a title based off the engine.)  Since 
Torque is derived from Tribes by way of Tribes 2, I've passed along the 
information and attached code to Tim Gift, who's checking to make sure 
the Torque engine and the games that make use of it are / are not 
subject to this particular DoS.

Davis Ray Sickmon, Jr
Owner, Midnight Ryder Technologies

Mascot wrote:

> st0ic wrote:
> 
>>Overview:
>>     Sierra's "StarSiege: Tribes" game is vulnerable to a DoS (Denial of
>>Service) attack when running.
> 
> 
> This game was released in 1998. The creators (Dynamix) have since dissolved.
> When asked about open sourcing the game Sierra has replied "We don't have
> any idea where it is. It was archived by Dynamix long before they were
> closed and now it's probably in a box is some mega warehouse in france or
> something. We could't release it even if we wanted to." Check the last post
> on this page: http://tinyurl.com/gwhm (Tribalwar)
> 
> In other words, they don't have the source, they can't patch. Although if it
> starts being exploited the community will likely patch it via scripting or
> disassembly.
> 
> 
> --
> Mascot
> 
> 
> 




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ