quake3 1.32c update

25 replies [Last post]

9. May 2006 - 21:29

#11

Offline

Joined: Nov 2003

Posts:

quake3 1.32c update

i just can say, as soon as possible, 2!S Servers willl be updated, i just have to w8 until EN-Manouche is back from tour.

and pb is not stupid, if id would have informed evenbalance about the update, they would have reacted on it. but it is like always...

9. May 2006 - 21:54

#12

Offline

Joined: Sep 2003

Posts:

quake3 1.32c update

[BRO]Servers Updated

9. May 2006 - 22:03

#13

Offline

Joined: Sep 2004

Posts:

quake3 1.32c update

wrote:

are you joking, right? try to consider year of release and difference between 'q3a' project and 'punkbuster' project

Good point about the release date difference, but they could have improved the interface with this update. I guess there's no money in it anymore so nobody will bother.

parasight://infesting.your.senses

9. May 2006 - 22:14

#14

Offline

Joined: Dec 2004

Posts:

quake3 1.32c update

in any case e+ is kinda immune against that overflow (due to modified code)

so when you *know* that you are connecting to e+ server you can have relative sense of security even with 1.32b

but noone says that anyone cant give you ip for example of baseq3 server for purpose to *own* you

i'll check that traversal bug soon

9. May 2006 - 22:21

#15

Offline

Joined: Jun 2005

Posts:

quake3 1.32c update

wrote:

Quote:

but if server is 1.32c can people with 1.32b connect?

Ok, I just tested. When server is 1.32c the "b" players CAN connect and play without problems. Same goes with sv_punkbuster 1 on 1.32c.

Stupid PB kicks only 1.32c players on 1.32b servers. (info to evenbalance sent).

So, update your servers all NOW!! Players wait couple days.

That's because this is a server side update.

wrote:

lol@sethy ur too funny man... if i was a woman, you would make me horny.

10. May 2006 - 10:54

#16

Offline

Joined: Dec 2005

Posts:

quake3 1.32c update

@Setesh. No. It's for client and server. Please read the first post.

Anyways, I just got reply from Evenbalance on pb 1.32b server kicking 1.32c client issue:

Quote:

05/09/2006 19:30:32 - "Stuart Dunsmore"
Note #2: This should be fixed now.
05/09/2006 14:23:48 - "dakarin"
Note #1: Ticket submitted to support staff.

Let's check it...

EDITED: Ok, checked on c4-tdm 1.32b server pb 1, pure 1, client-1.32c. I played for 3 minutes, no kick for that earlier bug.

So now everyone should update! GOOD LUCK AND HAVE A FUN!

SiN - team of extraordinary individuals.

Those worthless creatures surround me...

10. May 2006 - 12:13

#17

Offline

Joined: Jun 2005

Posts:

quake3 1.32c update

wrote:

@Setesh. No. It's for client and server. Please read the first post.

Anyways, I just got reply from Evenbalance on pb 1.32b server kicking 1.32c client issue:

Quote:

05/09/2006 19:30:32 - "Stuart Dunsmore"
Note #2: This should be fixed now.
05/09/2006 14:23:48 - "dakarin"
Note #1: Ticket submitted to support staff.

Let's check it...

EDITED: Ok, checked on c4-tdm 1.32b server pb 1, pure 1, client-1.32c. I played for 3 minutes, no kick for that earlier bug.

So now everyone should update! GOOD LUCK AND HAVE A FUN!

The only part about client side i read in the first post is this:

Quote:

Finally, server administrators should note that game servers should be running in restricted environments as much as possible ( unpriviledged accounts and chroot jails ). It's a good thing to do the same for clients, or at least ensure that you are properly firewalled.

Which is only based on the part that that a client side should be properly firewalled/protected. Not about that the client needs the file also or do i read something wrong?

The readme only says stuff about the server.

Quote:

If you run a server with any older version, please upgrade or consider turning off autodownload

wrote:

lol@sethy ur too funny man... if i was a woman, you would make me horny.

10. May 2006 - 12:28

#18

Offline

Joined: Dec 2005

Posts:

quake3 1.32c update

@Setesh: than read again:

Quote:

Issue #2 ( CVE pending ): R_RemapShaders buffer overflow

A second issue fixed in this release would let a malicious server exploit a buffer overflow to execute a shellcode on connecting clients.

Which means - someone is bad-dark side ubber hacker, he runs q3 server, then you try to connect, he sends you among normal q3 data malicious code which overite some parts of memory in your computer, if done well, CS (code segment) in memory is overwritten with attacker code, if unlucky that codes get executed on your PC - it can contain anything: trojan horse, virus, sniffer or else. ---> You've been hacked.

SiN - team of extraordinary individuals.

Those worthless creatures surround me...