[Napshare-developer]Re: NapShare 2.2b has been released
Brought to you by:
web1
From: Nate <fi...@fa...> - 2005-04-15 21:15:34
|
A few tips, you will need to be a little patient with this new version as more people start running it things will get better. Please keep it running as much as you can. Make sure you uninstall any old NapShare version first so that you get a new "settings" directory, there are some new settings. It's also important to get the word out so that everyone upgrades ASAP for their protection (and faster downloads!). It is dangerous to run the old versions of MUTE, NapShare or MFC_MUTE at this time since known valid attacks have been posted. I tested both the Linux and windows versions, including sending different time offsets to test the time code and everything. A lot of thought went into this, and a lot of work on the code. The time number used has been put in the same place as the timer number was on the old MUTE versions, after the message ID. I also fixed the message ID code, it wasn't working properly all this time. I have had good reports from previous testers of the pipelining code that it does seem to increase download speeds. A few quick details: When it first starts up it contacts 4 random outside servers from a large list to get their "header" info that contains a time stamp. It only sends generic info to the server, only enough to get the headers. If all the server's times are within 3 seconds, we use that time to offset against your internal clock and thus are sync'ed with GMT/UTC. We sync again after 24 hours have passed, so no worries about drifting clocks. (it doesn't set or change your computer's internal clock, and you don't have to worry about doing that unless you want to) When a broadcast message is older than 10 seconds, we don't send it on or respond to it. If it's within 10 seconds, we process it and respond if it applies to us, we also pass it on to all other connected nodes. This prevents all the posted attacks, and keeps broadcast messages from living forever. |