BearShare Forums  

Go Back   Gnutella Forums > Current Gnutella Client Forums > BearShare (Windows) > BearShare Open Discussion
Register FAQ The Twelve Commandments Members List Calendar Arcade Find the Best VPN Today's Posts

BearShare Open Discussion Open topic discussion for BearShare users

Preview this popular software (BearShare Beta v5 "Download")


 
 
LinkBack Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #17 (permalink)  
Old August 11th, 2001
Abaris's Avatar
Ringwraith
 
Join Date: May 13th, 2001
Location: Europe
Posts: 86
Abaris is flying high
Question mysterious

Vinnie said on the GDF:

> Damn these people that didn't learn from BearShare's mistakes!

> If you recall, the "problem" version of BearShare would send a binary
> query of fixed length ONCE to EACH new connection that was
> established.

> This is identical to the proposal that John Marshall suggested (a new
> query per new host connection).

Is this update behaviour still built into newer bearshare servents ? don't know, i don't use bearshare, but it would seem very strange to me as vinnie said it "screwed up the network" and as he didn't want it to be used for automated researching. I am very confused about this thing as well, for several reasons:

1) there is absolutely no sense in broadcasting version numbers in order to look for an update. it causes too much traffic and it would be way easier to just connect to the home server on startup (like other servents do).

2) there is even less sense in <I>encrypting version numbers with an RSA key.</I> this is simply ridiculous.

3) if it were to block fake versions, why is this protocol enhancement secret ? it would protect bearshare servents, but every other servent would still connect to the fake version (which might be a virus or something even worse...) because they don't have a notion of what these packets mean.

4) a fake version of bearshare could just send normal messages, identifying itself as "SomeNewClient", and noone would notice it!
The user running the fake would never know what messages it sends to other servents (if he is not a hacker himself), and those servents (including bearshare!) would connect to it because they think it is just a new unknown servent. If it is published under the name of bearshare but sends messages identifying itself as gnotella or gnucleus, then every version of bearshare would connect to it because gnotella and gnucleus have no encrypted authentification feature. As a blocking mechanism, it is absolutely ineffective, it is useless.

but if the packets would contain information about the user's system or downloads or something else which all these sp***re fanatics claim (i can't hear the word anymore), why should it be broadcasted to other servents instead of sending it home? that makes no sense either.

what could these packets ever be good for ?
Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Bearshare -> malformed packets? DMF Connection Problems 1 February 4th, 2005 06:50 PM
Newbie refresher course - bearshare spy-packets scandal Nosferatu BearShare Open Discussion 4 March 29th, 2002 07:55 PM
Which gnutella clients use SpyWare? ahcollin General Gnutella / Gnutella Network Discussion 8 January 1st, 2002 11:20 PM
One question about encrypted packets bodhi BearShare Open Discussion 26 June 22nd, 2001 03:20 AM
"spyware" clients? any recommendations? newmz General Gnutella / Gnutella Network Discussion 1 May 22nd, 2001 11:05 PM


All times are GMT -7. The time now is 07:04 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright © 2020 Gnutella Forums.
All Rights Reserved.