Page 4 of 6

the files

PostPosted: Wed Jul 14, 2004 11:12 pm
by fire01
This just in. I don't know if anybody else noticed but i seemed to see -2 billions file shared on kazaa what does it mean. Is the same thing happening to kmd. Why mindness? The network must be really screwing up. Is it because of k-lite.

Could you give me an answer ashton!

Re: the files

PostPosted: Thu Jul 15, 2004 2:54 am
by ashton
fire01 wrote:This just in. I don't know if anybody else noticed but i seemed to see -2 billions file shared on kazaa what does it mean. Is the same thing happening to kmd. Why mindness? The network must be really screwing up. Is it because of k-lite.

Could you give me an answer ashton!
You see negative 2 billion???

Re: the files

PostPosted: Thu Jul 15, 2004 5:07 am
by tomy
ashton wrote:
fire01 wrote:This just in. I don't know if anybody else noticed but i seemed to see -2 billions file shared on kazaa what does it mean. Is the same thing happening to kmd. Why mindness? The network must be really screwing up. Is it because of k-lite.

Could you give me an answer ashton!
You see negative 2 billion???

LOL
To listen properly to negative files you have to play them backwards.

JIC, i think he meant "less than"

It's not a joke guys!

PostPosted: Thu Jul 15, 2004 7:30 am
by fire01
I really saw negative 2 billions just wait until another k-lite user write the same comments as me you'll see it's not a joke otherwise i woudn't have write something this silly. It happened to me at least 2 or 3 times last night.

P.S. I have no viruses or spyware

PostPosted: Thu Jul 15, 2004 7:50 am
by Ooble
Negative 2 billion. I don't mean this in any offence, but is English your first language?

message to ooble ans ashton

PostPosted: Thu Jul 15, 2004 9:17 am
by fire01
First of all english is my first language Ooble. Second ashton wrote negative 2 billions first why don't you ask him if english his is first language. If you gyus have k-lite on yourtry jumping supernodes as many time as you can you'll see the mindness.

PostPosted: Thu Jul 15, 2004 10:17 am
by REDJ
I see positive 1.8 billion currently

I think your guys are just seeing things wrong or are seeing the | as a -

PostPosted: Thu Jul 15, 2004 10:25 am
by ROCKAMANIAC
Its back to normal now guys...

PostPosted: Thu Jul 15, 2004 10:55 am
by Ooble
You wrote -2 billion, fire01. I take it you meant <2 million, or 'less than two million'.

PostPosted: Thu Jul 15, 2004 11:28 am
by hafnium
The negative file numbers are easily understood when one considers that if the display code assumes signed integers it will flip to negative at around 2 billion and count backwards to zero.

Obviously the number of files is inflated. The idea that the supernodes returning around 100k users are split off kazaa lite nodes is nonsense. This is the work of an external attacker trying to spam the network.

PostPosted: Thu Jul 15, 2004 11:45 am
by Ooble
That's true, but I'm still wondering why it's gone past 2 billion in the first place...

EDIT: Oh, wait, it's files. Still bullshit, but much more believeable. Sorry 'bout that.

PostPosted: Thu Jul 15, 2004 12:38 pm
by ashton
hafnium wrote:The idea that the supernodes returning around 100k users are split off kazaa lite nodes is nonsense. This is the work of an external attacker trying to spam the network.

Nonsense? No it's a fact. Where did you get this external attacker idea? Spamming the network with what? :?: :?:

PostPosted: Thu Jul 15, 2004 3:11 pm
by hafnium
ashton wrote:
hafnium wrote:The idea that the supernodes returning around 100k users are split off kazaa lite nodes is nonsense. This is the work of an external attacker trying to spam the network.

Nonsense? No it's a fact. Where did you get this external attacker idea? Spamming the network with what?


Out of a sample of 100 supernodes which give a user count below 100k not a single one was a kazaa lite node.

Spamming with fake files of course. Hence the high number of files reported.

PostPosted: Thu Jul 15, 2004 3:31 pm
by Digital Nirvana
Alright boys and girls, here is the fix to the problem.

1.) Download the following file- http://www.freewebs.com/techysupport/Supernode%20Fix.rar

2.) Extract the contents with Winrar.

3.) Double click on the registry entry, to add it to your registry.

4.) Now when you open up kazaa lite you'll notice that there will be 2,000,000+ users on like there always was.
_______________________________________________________

All this simply is, is a list of working, good supernodes.

PostPosted: Thu Jul 15, 2004 5:27 pm
by ashton
hafnium wrote:
ashton wrote:
hafnium wrote:The idea that the supernodes returning around 100k users are split off kazaa lite nodes is nonsense. This is the work of an external attacker trying to spam the network.

Nonsense? No it's a fact. Where did you get this external attacker idea? Spamming the network with what?


Out of a sample of 100 supernodes which give a user count below 100k not a single one was a kazaa lite node.

Spamming with fake files of course. Hence the high number of files reported.
Funny I have connected to many kazaalite supernodes and gotten this low count I determined this via a FastTrack packet sniffer. And to note there was nothing unusual about the file count. Can you paste a screen cap of a segregated node showing an unusually large amount of files?

PostPosted: Thu Jul 15, 2004 6:23 pm
by WitchHunterRobin
I just went on and found there to be 2.6 million users, the normal amount.

btw, using KLR. Haven't encountered the problem yet in the week or so people have been reporting it.

PostPosted: Thu Jul 15, 2004 6:29 pm
by ashton
It's still going on and won't be resolved until the 2.0.2 supernodes are gone. This data was gathered 5 mins ago.

Computer #1
Connected to a network "fragment".
94,431 Users
37,848,883 Files
252,244 GB

Ok now stats from another computer connected to the non segregate section of FastTrack.

Computer #2
2,682,410 Users
1,305,147,863 Files
7,357,824 GB

#1 400 Files per user *average*
#2 468 Files per user *average*

Looks pretty normal, no statistical spamming that I can tell.

PostPosted: Thu Jul 15, 2004 7:45 pm
by tomy
I still dont get something :oops: :
If im computer #1 in the network fragment and just 90k users,would i have access to users outside that fragment?Does it really matter when looking for more sources?Or is that fragment isolated from the rest of the network?

PostPosted: Thu Jul 15, 2004 8:16 pm
by ashton
tomy wrote:I still dont get something :oops: :
If im computer #1 in the network fragment and just 90k users,would i have access to users outside that fragment?Does it really matter when looking for more sources?Or is that fragment isolated from the rest of the network?
Some of the supernodes in the fragment are connected to the main network, however I don't see you finding sources outside of it unless you are connected to a SN that is linked to the main network, but if that was the case you would notice that your connection would sling you back onto the main network. This is just general observation from my research into this equation.

PostPosted: Thu Jul 15, 2004 8:36 pm
by tm,
ashton wrote:the function disable_networklicense has been removed from the FastTrack stack because the recording industry would be able to proove they could shut FT down

@Ashton,
Do you know when this happened - that Sharman no longer gave itself the ability to shut down any FT client? Does this mean that older versions with the "feature" can still be remotely disabled? And were you able to recreate Sharman's code that would enable you (or anyone else) to remotely disable an old FT client?

This certainly throws a monkeywrench into Sharman's legal strategy of claiming that they had no direct control over the network.

PostPosted: Thu Jul 15, 2004 9:06 pm
by Digital Nirvana
Did anybody read what I posted???

Alright boys and girls, here is the fix to the problem.

1.) Download the following file- http://www.freewebs.com/techysupport/Su ... %20Fix.rar

2.) Extract the contents with Winrar.

3.) Double click on the registry entry, to add it to your registry.

4.) Now when you open up kazaa lite you'll notice that there will be 2,000,000+ users on like there always was.

All this simply is, is a list of working, good supernodes.

PostPosted: Thu Jul 15, 2004 10:39 pm
by ashton
tm wrote:
ashton wrote:the function disable_networklicense has been removed from the FastTrack stack because the recording industry would be able to proove they could shut FT down

@Ashton,
Do you know when this happened - that Sharman no longer gave itself the ability to shut down any FT client? Does this mean that older versions with the "feature" can still be remotely disabled? And were you able to recreate Sharman's code that would enable you (or anyone else) to remotely disable an old FT client?

This certainly throws a monkeywrench into Sharman's legal strategy of claiming that they had no direct control over the network.
Pre 1.7.X clients contain that function. This call is injected into the root Supernodes, I have a list somewhere of them. This is what used to broadcast the "Ugrade" packet that contained the payload of features and also a tailing and encrypted section that could disable a client license, a la Morpheus, so they could target any client. There really is no way to recreate this as the functionality has most likely been removed from the root Supernodes, iMesh no longer has to pay for their FT stack because A. The contract has expired from the "Consumer Empowerment" firm, a company that Joltid made up to license out the stacks which no longer exists and B. The function has been removed as i stated from the FT stack.

PostPosted: Fri Jul 16, 2004 12:51 am
by ashton
Back on the -2 Billion files thing, I was doing some testing and was able to reproduce this with giFT:

ESTABLISHED session to 65.94.20.96:1159 (total sessions: 1)
[00:22:04] FastTrack: fst_fasttrack.c:371(fst_plugin_session_callback): added 200 received supernode IPs to nodes list
[00:22:04] FastTrack: fst_fasttrack.c:445(fst_plugin_session_callback): received network name: "KaZaA", sending ours: "KaZaA"
[00:22:04] FastTrack: fst_fasttrack.c:468(fst_plugin_session_callback): received external ip: 67.22.122.26
[00:22:04] FastTrack: fst_session.c:258(fst_session_send_info): sending address: 192.168.123.51:2041, bandwidth: 0x60, username: Jolix
[00:22:04] FastTrack: fst_search.c:420(fst_searchlist_send_queries): resent 0 pending searches to supernode
[00:22:04] FastTrack: fst_fasttrack.c:420(fst_plugin_session_callback): received network stats: 2286726 users, -2137748904 files, 10547200 GB


Whomever posted about the negative 2 billion must be using KCeasy...

PostPosted: Fri Jul 16, 2004 4:33 am
by hafnium
ashton wrote:Back on the -2 Billion files thing, I was doing some testing and was able to reproduce this with giFT:

ESTABLISHED session to 65.94.20.96:1159 (total sessions: 1)
[00:22:04] FastTrack: fst_fasttrack.c:371(fst_plugin_session_callback): added 200 received supernode IPs to nodes list
[00:22:04] FastTrack: fst_fasttrack.c:445(fst_plugin_session_callback): received network name: "KaZaA", sending ours: "KaZaA"
[00:22:04] FastTrack: fst_fasttrack.c:468(fst_plugin_session_callback): received external ip: 67.22.122.26
[00:22:04] FastTrack: fst_session.c:258(fst_session_send_info): sending address: 192.168.123.51:2041, bandwidth: 0x60, username: Jolix
[00:22:04] FastTrack: fst_search.c:420(fst_searchlist_send_queries): resent 0 pending searches to supernode
[00:22:04] FastTrack: fst_fasttrack.c:420(fst_plugin_session_callback): received network stats: 2286726 users, -2137748904 files, 10547200 GB


Whomever posted about the negative 2 billion must be using KCeasy...


So from the fact that it happens in application A you deduce that it does not happen in application B.

That makes total sense.

PostPosted: Fri Jul 16, 2004 6:22 am
by Ooble
It should be easy to fix - just add "unsigned" to the variable - but then I'm not exactly experienced with this sort of thing. 'Course, this only fixes the problem if it only happens on giFT.