 | | | Treason Uncloaked! (Erik) | Treason Uncloaked! (Erik) 2006-09-29 - By Tom Diehl
Back
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--===============1569328031==
Content-Type: TEXT/Plain; charset=US-ASCII; format=flowed
On Fri, 29 Sep 2006, Erik wrote:
>> Message: 1
>> Date: Fri, 29 Sep 2006 08:47:05 -0400
>> From: Brian Long <brilong@(protected)>
>> Subject: Re: Treason Uncloaked!
>> To: "Discussion of Red Hat Enterprise Linux 3 (Taroon)"
>> <taroon-list@(protected)>
>> Message-ID: <451D15C9.4020907@(protected)>
>> Content-Type: text/plain; charset=ISO-8859 (See http://ISO-8859.ora-code.com)-1; format=flowed
>>
>> Erik wrote:
>> > My current Server: Redhat AS Release3 2.4.21-4.ELsmp #1 SMP Fri Oct 3
>> > 17:52:56 EDT 2003 i686 i686 i386 GNU/Linux
>>
>> Erik,
>>
>> You're running the RHEL 3 GA with no updates applied. I suggest you
>> connect to RHN and update your server ASAP. There are various security
>> and functionality fixes in the updates.
>>
>> /Brian/
>>
>>
>>
>> -- ---- ---- ---- ---- ---- --
>>
>
> 1) The Server is already tuning off for window scaling during the 'Treason
> Uncloaked' occur
>
> bash> cat /proc/sys/net/ipv4/tcp_window_scaling
> bash> 0
>
> 2) Yesterday evening I also update the latest kernel from version
> 2.4.21-4to the version
> 2.4.33 and using up2date to install all newer packages. But today currently
> at 5.53am, I still can see the message in dmesg. Se below:
>
> TCP: Treason uncloaked! Peer 211.25.132.129:63581/80 shrinks window
> 1866011154:1866011155. Repaired.
> TCP: Treason uncloaked! Peer 211.25.132.129:63581/443 shrinks window
> 1866011154:1866011155. Repaired.
> TCP: Treason uncloaked! Peer 202.75.46.41:7638/443 shrinks window
> 1073268829:1073268830. Repair
>
> I already spend about a week to search in google regarding this 'Treason
> Uncloaked' issue. All what I can see is just explaination but there is no
> spesific solution. But this issue make my webserver running in high Load
> Average ( over 110 ) and cpu running 100% with Idle is 0%.
If you cannot be 100% sure what is going on and then 100% sure you have
eliminated it, then your only choice is to reload the machine.
Most of the time barring a desire to do further forensic research on it
the easiest and most expedient thing is to format and reload.
>
> Thank you.
>
--
Tom Diehl tdiehl@(protected) Spamtrap address mtd123@(protected)
--===============1569328031==
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Content-ID: <Pine.LNX.4.64.0609291815581.28838@(protected)>
Content-Description:
Content-Disposition: INLINE
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
--===============1569328031==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
--===============1569328031==--
|
|
|