napshare-developer Mailing List for NapShare

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi there, I postet also a feature request at sf.net but also want to ask 
it this way.
Is napshare able to share more than one folder?

greets
Discodestroyer

It compiled OK with no changes to the windows MSYS (compiler) setup.

This version uses less CPU when you have a large amount of shared files.

You should update your list of webhost caches.

http://prdownloads.sourceforge.net/napshare/NapShare2_2_4-Setup.exe?download
http://sourceforge.net/project/showfiles.php?group_id=19407

-- 
http://www.fastmail.fm - Send your email first class

If you are having problems compiling and running with GCC 3.4 and the
2.6 Kernel this should solve the problems. A Mandrake 10.2 binary is
also available, it may work on Red Hat versions that were near the MDK
10.2 release time.

If you choose to compile you will need to install either the wxGTK or
wxPython "devel" libraries from RPM.

Links:
http://prdownloads.sourceforge.net/napshare/napshare_2_2_4.tar.gz?download
http://prdownloads.sourceforge.net/napshare/napshare_mandrake10_2binary_2_2_4.tar.gz?download
http://sourceforge.net/project/showfiles.php?group_id=19407

Enjoy!

-- 
http://www.fastmail.fm - The way an email service should be

Fine. thanks. Needed decision.
Though it is more ideology than earning money: This means we need a 
working app or code.
no problem with all, first we need partials and second E2E in napshare,
Do you tested i2phex over i2p? Secure gnutella client.
If gnutella would have forced partials, we could use gntuella,
but ed2k partials are better especially for a slow network to spread 
partials.
the key network hybrid with edonkey network or the gnutella network 
would then be the third measurement.
Why not taking shareaza code, making a mod and the first goal is to 
implement mute/keynetwork as a new network?
i2phex can only be stopped by the clients name shareaza.
and maybe roberto comes out with a working ants-java-mule client earlier.
There are many ideas concerned with a anonymous seed for edonkey partials.
First the seed, later the whole userbase. But maybe kademlia on i2p is 
out soon as well.
ants-mule would be better. but mute-gntuella fine as well. Or a shareaza 
key mod.
;-)
Nate wrote:

>NapShare is now a dual network client, it will continue to connect to
>the MUTE Network for as long as it is easy and safe to do so. If privacy
>issues or network flooding happen the user can choose not to connect to
>the MUTE Network.
>
>In order to quickly provide the users with some of the improved features
>requested such as supernodes, download speed increases, partial sharing
>during downloads, sub-hashes, E2E and a lot more, I will need to make a
>lot of changes to the network communication protocol.
>
>Therefore I am announcing the "Key Network". The protocol of this new
>network is the same as the MUTE network protocol at this point, but as
>time goes by I will be changing it to provide the advanced features that
>everyone wants. The network type will be identified at connection time
>after AES keys are exchanged to maintain privacy.
>
>NapShare clients will also provide a "bridge" between networks. It may
>be possible to bridge to other networks in the future.
>
>I know the Gnutella protocol and am open to comments/suggestions on how
>some special location users could provide a safe bridge to the Gnutella
>Network.
>
>I am also willing to accept code contributions for connection to other
>networks or other features. I don't have any problems accepting and
>integrating code/patches or ideas from other developers even if the
>code isn't pretty or "perfect" as long as it works.
>
>The next version will reflect the changes, and hopefully include some
>cool new features.
>
>Due to politics and/or personality clashes, I will no longer be
>supporting the MUTE *project*.
>
>
>  
>

NapShare is now a dual network client, it will continue to connect to
the MUTE Network for as long as it is easy and safe to do so. If privacy
issues or network flooding happen the user can choose not to connect to
the MUTE Network.

In order to quickly provide the users with some of the improved features
requested such as supernodes, download speed increases, partial sharing
during downloads, sub-hashes, E2E and a lot more, I will need to make a
lot of changes to the network communication protocol.

Therefore I am announcing the "Key Network". The protocol of this new
network is the same as the MUTE network protocol at this point, but as
time goes by I will be changing it to provide the advanced features that
everyone wants. The network type will be identified at connection time
after AES keys are exchanged to maintain privacy.

NapShare clients will also provide a "bridge" between networks. It may
be possible to bridge to other networks in the future.

I know the Gnutella protocol and am open to comments/suggestions on how
some special location users could provide a safe bridge to the Gnutella
Network.

I am also willing to accept code contributions for connection to other
networks or other features. I don't have any problems accepting and
integrating code/patches or ideas from other developers even if the
code isn't pretty or "perfect" as long as it works.

The next version will reflect the changes, and hopefully include some
cool new features.

Due to politics and/or personality clashes, I will no longer be
supporting the MUTE *project*.

-- 
http://www.fastmail.fm - IMAP accessible web-mail

This version is very stable.

It fixes a GUI lock up bug I have been trying to find for a while now
that wouldn't happen all the time, and I spent a lot of time tweaking
the download timing and re-search logic so that downloads work better.

Someone asked me if you must always use Automation. A manual search
feature is included.

Tested on Linux and win98. A Mandrake 9.2 binary is also available.

People who are running the older version MUTE clients are still at risk
due to posted attacks, please upgrade as soon as you can.

Linux and windows versions are available at the download link:
http://sourceforge.net/project/showfiles.php?group_id=19407

Home page http://napshare.sourceforge.net/
Mailing list info http://sourceforge.net/mail/?group_id=19407

It's important to open up a few more incoming connections at this time
if you are not firewalled.

Changelog entry:

# v 2.2.3   2005.04.29

- Fixed crash in download, some situations where re-search was used
- Fixed own search results come back to yourself
- Adjusted download logic for re-search

I hope I can explain a little clearer how the new GMT time stamp thing
works to protect privacy.

The two posted attack scenarios created two problems:

1. How to prevent the attacks.
2. How to do #1 above and still keep broadcast messages from living
forever.

Every message sent on the network has a unique Message ID and a Message
Counter attached to it. It looks something like this:

57EE60E1417F6048588A5B9874F0E5BDAB519AC0_67752657

Message ID (40 characters), then "_" (underscore character) then the
Message Counter.

The Message Counter was a number that we added +1 to when we sent a new
message out to the network. It slowly increased as new messages were
added to the network.

The Message Counter on new versions is now simply a Time Stamp based on
GMT, the number of seconds since midnight Jan 1, 1970 (also known as
UTC). We simply "stamp" new messages with the time.

If a message is older than 10 seconds, it's ignored, no action is taken.
This prevents messages from living forever. In the actual code, we allow
for a little slop between clocks, since real world clocks drift a little
and get out of sync. Broadcast messages do not live more than 10
seconds.

If a message is "fresh", then we process it internally, respond if
needed and pass it on to all the other connected nodes.

This protects the privacy of the user because we either react to the
message and also pass it on to other nodes that may also react, or we
ignore the message and it goes no further.

An attacker connecting twice to a node (either of the previously posted
attacks) only sees the message being passed on or not, and possibly a
number of reply messages that could have come from other connected nodes
further down the line.

Knowing the value or modifying the "UC" / TTL counter doesn't provide
any information because we ignore that too.

An attacker can't know what your clock is set to exactly, so there is no
way to know if a message originated at your node or was passed *through*
your node. (typical internet packet delays and routing also help with
this)

An attacker can modify the Time Stamp of it's sent messages, but the
receiving node will also pass that message to other nodes (if it isn't
old), so any replies may have come *through* the receiving node.

10 seconds is enough time to allow for clock "slop" and also create a
good number of results. Reply messages and other messages are allowed to
live a little longer because they are not broadcast messages and have
little chance of living forever.

If a source is more than 10 seconds away, the download travel time will
most likely be long also. It would be better to use a different path for
a download in that case. The network is very dynamic, so at any time a
re-search for a file source could show less delay.

This does *not* protect the users of old versions that are still out
there, you need to upgrade in order to be protected with this method.

It is possible to tell what version you are running by the way your node
handles messages.

An attacker *can* easily tell if you have upgraded or not.

Other details:

The time clock is sync'ed to GMT using randomly picked outside sources
selected from a large list of URL's. Four servers in a row must have the
same time within a few seconds in order for it to be a valid time.

The time clock is re-sync'ed every 12 hours, and if this fails, every
hour until a proper time is set.

I have also given a lot of thought to the search originating node
"FORWARD" flag used to protect the senders privacy and couldn't come up
with anything that would let an attacker identify the originating party.

This version fixes a few bugs, one would happen only while downloading,
uploads and connections were not affected.

Tested on Linux and win98. A Mandrake 9.2 binary is also available.

People who are running the older version MUTE clients are still at risk
due to posted attacks, please upgrade as soon as you can.

It's probably a good idea for windows users to uninstall first.

Look for V2.2.2b (Beta).

Linux and windows versions are available at the download link:
http://sourceforge.net/project/showfiles.php?group_id=19407

Home page http://napshare.sourceforge.net/
Mailing list info http://sourceforge.net/mail/?group_id=19407

It's important to open up more incoming connections at this time if you
are not firewalled.

Changelog entry:

- Fixed crash in download, some situations where re-search was used
- Fixed own search results come back to yourself

The last NapShare to be compatible with the Gnutella network was V1.9.1,
and only for Linux.

It still works very well on Gnutella.

You should go and find new Webcache URLs to use, the default list is
getting old.

If you use automation with that version and want to use the "extern"
filters, apply the patch that's available in the patch section.

I urge you to start using the latest anonymous version for your own
privacy. Downloads are slower because everything goes through proxy
nodes, but that's the tradeoff.

I am not planning on supporting the Gnutella version anymore.

I just received a report from a reliable source that it works on XP with
no problems.

I also posted a Mandrake 9.2 (Linux) binary only version. It may also
work on RedHat of the same release version time.

> This version is much more compatible with the older versions still
> out there without risking the security of the new version.
> 
> It still uses the GMT clock sync stuff to prevent all the posted
> attacks.
> 
> Re-search for new sources on failed downloads is working again and I
> made some other minor fixes. Pipelining for faster downloads is
> included.
> 
> Tested on Linux and win98.
> 
> People who are running the older versions are still at risk, please
> upgrade as soon as you can.
> 
> It's probably a good idea for windows users to uninstall first.
> 
> Look for V2.2.1b (Beta).
> 
> Linux and windows versions are available at the download link:
> http://sourceforge.net/project/showfiles.php?group_id=19407
> 
> Home page http://napshare.sourceforge.net/
> Mailing list info http://sourceforge.net/mail/?group_id=19407
> 
> It's important to open up more incoming connections at this time if you
> are not firewalled.
> 
> Changelog entry:
> 
> - Now more compatible with older versions, without risking
>   the new version's security
> - Re-search on failed downloads is working again
> - Display of new or old version connection type
> - Clock sync every 12 hours, if fail retry next hour
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime
> info,
> new features, or free trial, at: http://www.businessobjects.com/devxi/728
> _______________________________________________
> MUTE-net-Discuss mailing list
> MUT...@li...
> https://lists.sourceforge.net/lists/listinfo/mute-net-discuss

This version is much more compatible with the older versions still
out there without risking the security of the new version.

It still uses the GMT clock sync stuff to prevent all the posted
attacks.

Re-search for new sources on failed downloads is working again and I
made some other minor fixes. Pipelining for faster downloads is
included.

Tested on Linux and win98.

People who are running the older versions are still at risk, please
upgrade as soon as you can.

It's probably a good idea for windows users to uninstall first.

Look for V2.2.1b (Beta).

Linux and windows versions are available at the download link:
http://sourceforge.net/project/showfiles.php?group_id=19407

Home page http://napshare.sourceforge.net/
Mailing list info http://sourceforge.net/mail/?group_id=19407

It's important to open up more incoming connections at this time if you
are not firewalled.

Changelog entry:

- Now more compatible with older versions, without risking
  the new version's security
- Re-search on failed downloads is working again
- Display of new or old version connection type
- Clock sync every 12 hours, if fail retry next hour

Upgrades are happening, so we are moving along.

There's announcements on http://zeropaid.com/ and
http://board.planetpeer.de/

I can't stress enough how important it is to upgrade, and get the word
out so more people upgrade as soon as possible.

Again, it's dangerous to keep using the old versions since there are
valid posted attacks.

Please be a little patient with this new version and keep it running as
long as you can while other people upgrade.

If you want to contribute a little more time to the upgrade process and
don't mind doing things like tweaking some settings temporarily, please
contact me privately.

Thanks.

Thanks for running a webcache!

I am using the "lower" code for the MUTE protocol stuff and didn't
change the string for that, I don't think Eric (MFC) did either, not
sure if that would cause any security concerns. It also doesn't identify
itself when it connects, all another node knows is that it's a MUTE
client, and that might be a good thing.

On Sat, 16 Apr 2005 00:17:10 +0200 (CEST), mu...@fi... said:
> I am still a newbie so forgive me if this is a stupid question BUT:
> 
> Is napshare using the same webcaches as mute and mute mfc?
> 
> I run a couple webcaches but have never seen a napshare client on any of
> them.
> 

I am still a newbie so forgive me if this is a stupid question BUT:

Is napshare using the same webcaches as mute and mute mfc?

I run a couple webcaches but have never seen a napshare client on any of
them.

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.

This version prevents all the posted attack problems, and also solves
the message "live too long" problem.

It includes the new pipelining code for downloads, so you should see
some increased speeds.

Linux and windows versions are available at the download link:
http://sourceforge.net/project/showfiles.php?group_id=19407

Home page http://napshare.sourceforge.net/
Mailing list info http://sourceforge.net/mail/?group_id=19407

It's important to open up more incoming connections at this time if you
are not firewalled.

Changelog entry:

- Use GMT/UTC time stamp on messages, fix for posted attacks
- Pipelining added, downloads should go faster
- IP blocking added
- LAN mode working (needs real world testing)
- Anti flooding code added, but not turned on for this version
- Downloads cancel faster

1=2E9=2E1 Beta 2 is here!

Sorry for the duplicate files, this one will fix that=2E You can
go through your "done" directory, sort it by size, and remove any
duplicate files=2E It would be better to just start with a new "done"
directory to start a clean new test=2E

Includes a few more fixes and tweaks=2E

You can get it temporarily at
http://napshare=2Esf=2Enet/napshare-1=2E9=2E1beta2=2Etar=2Egz

If this link doesn't work, there's either a newer beta version or
beta testing is done, check the home page=2E I will post updates here
if new beta versions are made=2E

Powered by Rockliffe MailSite http://www=2Erockliffe=2Ecom

For those of you interested in operating on a LAN with Gnucleus
users, I threw this little bit of code together, it should
find any Gnucleus on your local network, just like Gnuc does
when it starts in LAN mode=2E It will tell you the IP:port and
the LAN name=2E

Download it, put it in it's own directory, compile and run
it=2E You may need to set in your own network broadcast IP
if it doesn't work the first time, see the top part of
the source code for more info=2E The first response is
always yourself=2E

Get it at:
http://napshare=2Esf=2Enet/findgnuc=2Ec
(if it's not there then look in the latest tar=2Egz file)

There's a thread with more info about this at:
http://www=2Egnutellaforums=2Ecom/forumdisplay=2Ephp=3Fforumid=3D20

Let me know how it works for you=2E
Here's my test output:

$ gcc -o findgnuc findgnuc=2Ec
$ =2E/findgnuc

Make sure port 5467 is not firewalled, UDP packets must get back to
us!
Check that your network broadcast IP is: 255=2E255=2E255=2E255

GNUCLEAR PING Sent! (now waiting for responses, to stop use cntl-c)

GNUCLEAR PING "PROBING-NETWORK-ONLY" at 192=2E168=2E0=2E1:6346
GNUCLEAR PONG "MYNETWORK" at 192=2E168=2E0=2E251:6346
GNUCLEAR PING "MYNETWORK" at 192=2E168=2E0=2E248:6346

DONE (5 minutes)

Powered by Rockliffe MailSite http://www=2Erockliffe=2Ecom

A new version of NapShare is about to be released! Please test out
the "beta" version and let me know if you have any problems=2E

You can get it temporarily at
http://napshare=2Esf=2Enet/napshare-1=2E9=2E1beta1=2Etar=2Egz

If this link doesn't work, there's either a newer beta version or
beta testing is done, check the home page=2E I will post updates here
if new beta versions are made=2E

You can run this test version in it's own directory=2E

NOTE: This beta version will NOT mess with your settings in the
=2Enapshare dir, it will only write config files to the working
directory, so make a new directory, test, and then if you like,
go back to the old version=2E Just do a "make" only (not install)
and move the finished binary from the "src" directory to where
you want it to run, then do =2E/napshare in that directory=2E

Changes include:

- Multi Source Downloads !
- Better push results in both downloads and uploads
- IP based blocking, see right click in nodes window
- Tested with Gnucleus 1=2E8=2E6 LAN mode for private networks
- Lots of tweaks and more info in displays
- Compiled OK on Mdk 8=2E2, 9=2E2 and RH 9=2E0

Readme file and some gui additions will follow in later versions=2E

If you would like to do some advanced testing with gdb, please
consult the README file on how to use gdb, it's not too hard to
do and you can send me a bt and/or "print" some variables, just
type "help" when in gdb=2E

Send feedback to web1 - at - users=2Esourceforge=2Enet

Enjoy!

Powered by Rockliffe MailSite http://www=2Erockliffe=2Ecom

- Nodes stay connected better, less dropped nodes
- Automation can now kick nodes after passes
- Automation file can be loaded without quitting program
- Automation messages added to bottom of screen, tells status better
- Trailer status bits set to "standard" gnutella specs
- Memory leak fixes (thanks to all who posted info)
- Little fixes here and there
- README file updated

http://napshare=2Esf=2Enet

RPM's for RH & Mdk also

Powered by Rockliffe MailSite http://www=2Erockliffe=2Ecom

I just finished a MySql Automation Filter perl script with it's
companion MySql Admin script.
The Admin script is a console based menu driven program that uses
your current list of files in your "done" directory to create a list
of file names and sizes for use by the filter script.
The filter script checks about to be downloaded files against the
list of file sizes and if it finds a match it doesn't download the
file.
The Admin script will also list any dups you may have in your "done"
directory so you can clean up if you wish.
Using MySql opens up a lot of other possibilities. The scripts
contain a lot of example code that you should be able to use to do
other functions.
You could for example create a database containing files from many
different directories you have so no dups are downloaded. You could
also have a script run from cron on a regular basis that updates this
list.
I have been running this script for a week now with no problems, I
would appreciate any bug reports you can provide.
The scripts are available on the script page at the project site:

http://napshare.sourceforge.net/scripts.html

Enjoy!

Happy Hollidays!

I added GWebCache support and would like any feedback on how
it works for you.
I also added code to attempt to support private filesharing
LANs. If you can test this, please do so.
The new code is available via anon CVS now, I will put up a
tar file after I test it for a while longer. More info in
the README file.

Enjoy!

Hi,

i am more a napshare user than a developer ! maybe in the future :-)) 
i want use napshare for downloading mp3 but i did not understand yet how i 
can reasume and complete an incomplete file in another day when i disconnet 
the PC from the web.
Can someone tell me what i have to do ??

thanks and best regards
ULI

I've created a patch that makes napshare be more
intelligent in detecting duplicate files. When I click
on  a file now, many more matches are auto-hilighted.
When I click on download selected all of the names are
renamed to the file that I clicked on.

My question is, in download_new, is there any way to
flag two files as being the same file (so that if one
completes, the other will be removed from the queue,
and they won't both try to download at the same time)
without having the same name? Also, I am not sure if
napshare requests the wrong name from the clients or
not at this point.

Thanks in advance,
~Daniel

=====
/bb|[^b]{2}/

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

2001	Jan	Feb (2)	Mar	Apr	May (1)	Jun (2)	Jul (3)	Aug (1)	Sep	Oct	Nov	Dec (1)
2002	Jan (7)	Feb (16)	Mar (21)	Apr	May (2)	Jun (1)	Jul (1)	Aug (2)	Sep	Oct	Nov	Dec (1)
2003	Jan (1)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov (3)	Dec
2005	Jan	Feb	Mar	Apr (12)	May	Jun (2)	Jul	Aug	Sep	Oct	Nov	Dec
2006	Jan (2)	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

napshare-developer Mailing List for NapShare

napshare-developer — Developer Chat