Syntaxe: I have added your key. Make sure you have installed my key (below) and then try to connect.

Centauri (above post) reported that version 1.5b2 of waste has a incompatibility with waste versions others on the mesh are using. You probably will not be able to use that version on the zer0share mesh.

The situation with the NAT probably means you will be unable to accept incoming connections. You should still be able to join the mesh and download files.

You selected a non-default key length of 4096 bits, which is larger than the default 1536 bits. This will work, but depending on various factors you may experience degraded performance with this larger key size.

Here is my key and the other info:

WASTE_PUBLIC_KEY 20 1536 drak@zeroshare
AD849A75746B3D9D917356B0C6968A9096B7359E27E49E7110DD76EF702F
915452796B8B694DB92F282326463CD991D48EE7750C19DDE30AF915A85C
7692BAF43E665FF806319A86ED1AC5E395917F81A4772FE85D083B9B900E
08F71C0A9A2833BCA09EA3E6F34117145470E939861A1A5E578F5C9A871C
82D3AC3FC69458F992C52E98EE76A09919E32800E1A67299A7B9849187AC
5A139CE0AD210FE7663E16F4A9E9CF71FD341BB0BE20DFDDA292FFA52B92
1E43EBDF4202A94EB50E3F8F0003010001
WASTE_PUBLIC_KEY_END


Network Name:
zer0share

Listen on Port:
11150

URL:
zeroshare.drakonix.org

IP:
68.165.107.59

No respone yet from the network
 

Thanks, i added your key, and i saw i already imported it although it was already imported from the keys database from:

http://snow.prohosting.com/cycent/zer0/keys.pl

Still unable to get on the network, BTW is it "Zer0share" or "zer0share" as you wrote?

Thanks for all :W:

PS: i may PM may NAT and internal IPs if it is usefull, thought my NAT is already known now

Hi, I've just added your key to the database as well.

The network name is just zer0share
All nice and lowercase :)

WASTE 1.5 is a manadtory upgrade
 

Unfortunatly WASTE 1.5 looks like a manadatory upgrade as it fixes a few security holes in WASTE .One major vunerability Waste was able to be crashed by a annoymous user and this has now been fixed in 1.5 and now older clients cannot connect to WASTE 1.5 .

From the change log for WASTE 1.5 Alpha 1
• Although the inner protocol is compatible to older clients, I have made them incompatible by forcing another sync sequence. Because older clients have security issues this step is really needed.

Also WASTE 2 will not be compatible anyway so best to upgrade now .

WASTE 1.5 offers alot of improvments also like better DNS Redirection ,Resume downloads and the new "Stealth mode" go look at the change log to see them all.

let me just make a brief and personal observation. the farther i get from justin frankel's client the less comfortable i become. i'm using v1.0 and will continue for the time being. while i certainly appreciate the work being put into the offshoot versions - deliberately orphaning frankel's work is overkill.

- js.

Add me please?
 

WASTE_PUBLIC_KEY 20 1536 kingkakdw
F7FDE04993C90658951D6E52C9F49B20817E339F1487EBC26B3D0C92FA49
D645FE5934B95731159303164883C62B81F2BE753B2F96EE1DAE6502D795
30286625A434DFF66B4468A562917CCBEEA4085BF53BCEE4B02D12C138C1
5B779CB5DEB391CE0CAB475FCA16A0E0F4130BA8E2C6C1A1CCD31D96C0B8
A73D3D7F0B35B716E92AED147D023EEE8F24E9D7E7755BEA547B473099E1
F71B69FCBCDE0853F8BF4BCFA21ED8325FDBBC5901E5A62552845C2DF9C7
25E7BEF3642B8C420291E7550003010001
WASTE_PUBLIC_KEY_END

welcome to nu kingkakdw. you're added. :beer:

- js.

I can see where youre coming from, but wasnt it you who also said "Developers may find it useful for new projects and to test newer versions of Waste"?
It is a bit hard to test when the (newer) network isnt there :P

Now the exploits in WASTE are being documented it is only a matter of time before a hostile party or malicious user comprimises any WASTE clients older than 1.5 so you are in effect creating a insecure "secure" network and leaving others and yourself on your meshes open to DOS attacks and other vunerabilities .One of the reasons Justin released the code as GPL is so people would develop it . If he didnt want it developed he wouldnt of released the source code .There are alot of Justins code including Nullsoft projects that are closed source .

WASTE_PUBLIC_KEY 20 1536 gyromind
E44BA096E998B51B1A35E2EC69143338737DE715B7D000F94364F32F5CA1
3EF54580A00D51B54E6071008AC6F980B28645B97C415447A1C07789179C
F8177C497F832FF3E6B90AC4646423CEB9D52F06078A24B5750522B355BD
7A425A35F213C7ED543DE307351B9752ED8637140FA9C5FC2CECC4C20024
224FE85F43B4D580F18A8C47EC431D46311BC231388F70D0D879645FC726
E63CE28CB2DEB6D4BC5BAD8605BAC2BFA88B83793EA4AD1FA4465EAFB3BB
99ACA2D7AD28CC47BCCC4FE70003010001
WASTE_PUBLIC_KEY_END

What IP address do I use to connect when I get accepted?

you''ve been added gyromind. welcome to p2p-zone and zer0share. :tu: pm me using this board's pm functions for IP details - or use skype to talk to me directly.

- js.

skype username: jackspratts

I’m happy development continues in the open source communities but I’m withholding judgment on the validity of shutting down access to previous clients. If people want to choose different versions promoted by different groups that are not backwards compatible – or even parallel compatible – they’re free to do so naturally. Meshes after all are so small that a few dozen people taking themselves out of action will have no effect on the overall system. The recent merwin network for example, called by some “nullsoft” is now fully migrated to the latest sourceforge protocol and no longer exists as an original WASTE group. It vanished from the last legacy clients yesterday afternoon at 4 PM. At its peak a few months back I counted slightly more than 50 simultaneous users but like the lifecycle of most meshes it had been in steady decline for some time (people meet, hook up and leave to start their own) so while losing it to v1.5 Beta 2 wasn’t a happy occurrence it wasn’t a tragedy either.

The problem I have with this is practical certainly, but right at the moment it’s more philosophical in nature. By balkanizing an already balkanized community and by encouraging developers to create clients that only connect to themselves we run the risk of creating yet another incompatibility boondoggle like VHS vs. Beta, ACC vs. WMA and so on. It’s been difficult enough getting people comfortable with the concept of WASTE without having to sit down and explain the competing security claims of one group’s clients vs. another’s every few months. I’m not sure I’m even comfortable calling this new version WASTE. Yes it contains some of Justin’s code but it appears from the credits at least Frankel didn’t work on it. It doesn’t say he did plus he’s not in the habit of orphaning his previous work. If at some point he jumps back into the development fray his “authorized” versions may have little in common with sourceforge’s, creating further issues.

For the most part I’m not looking down at my feet wondering if my laces are tied, I’m trying to see over the hill into the next county. This is not an issue that needs to be solved today. It’s just one that should be thought about. It may help to remember that no client will be completely secure, not even this latest attempt to redress the faults of v.1. To split the community over alleged security faults and guaranteed fixes is to akin to splitting the church over how many angels can dance on a pin. It’s unnecessary – sure the answers may be different but they might be equally valid. To engage the community with chants of “my v. is better than your v.” is to fall into the trap of diminishing returns and increasing fractionalization with little to show in the way of actual net benefits.

Indeed, "Developers may find it useful to test newer versions of Waste,” and I’m glad they are, I’m pro-development - but zer0share was not intended to be dismantled every 90 days by trendy new clients.

The best way to handle this or any dispute is by inclusion. To bring all members of the community together into the standards dialog who wish to participate and to avoid as much as possible development teams creating exclusive & incompatible products for whatever reason. Waste is open source and that means everyone is free to decide and create – not just the people at sourceforge. That’s a good thing in theory and it’s important for the future. We’ve seen what can happen in practical terms when the conversation is dominated by intransigence and stubbornness sets in, because we know about that previous Justin Frankel system called Gnutella and how it’s played out since the source code was released. Disastrously in my opinion. We should do everything necessary to avoid another “Bearshare vs. the World” with WASTE (keep in mind I’m not accusing anyone of such behavior).

What I’m advocating ultimately is this: Continue development, make WASTE as good as it can be, make it easy to use, secure and attractive. Bring people in. But by all means keep it as compatible and as free of personal competition and politics as possible. Even if that means certain compromises must be made on the path to theoretical perfection.

The most important part of WASTE won’t be discovered in the code, it’ll be found in the community. ;)

- js.

i can see reasons for not making it compatible with the original release..

as has been the problem with protocol changes in clients before
having one old client in an environment of new client will make it a weak link and be the hole where the whole network can be brought down..

i have known about the spoofing peoples nicks and being a third party in any private discussions they might be having.... but havent mentioned it anyone or talked about it publicly because its a pretty malicious idea...(in a trusted group you shouldnt need to worry about this..but all the same ..)
this needs to be fixed..and the new client encouraged to be taken up in all established meshes..

i have dicussed this with a few waste users and have come to the conclusion the upgrade would be an easy process (just make sure you mesh isnt called default in your profile manager)

sorry jack, but you have done your best to dicourage people from trying the new clients ever since wasted came out..i can understand a certain loyalty to the first release ..but really there is a few gaping holes there that need patching ...i would seriously suggest once the SF releasers get 1.5 out of beta all meshes upgrade...

%=0.2c

Hi i am new here glad to see the p2p community is coming back together that emule just sucks ass tbh

I have be around most of the p2p programs and have gotten many files that i share so others can get, manys on disk the now so ill have to wait till i get a new hdd so i can share more :p

Ive been using winmx again as after 2 years they have released a new beta version which runs well, if u just go to the news tab in www.winmx.com ull see there new one to dl anyways enuff of my rambling, ive got the key just below if someone can add me that would be grand.


WASTE_PUBLIC_KEY 20 1536 fennikishu
C6C4FE80D278782CFF94BA510CF3A44661F09ECA9CA0128E39CA9F3DF09A
FE481E65486E4D2BEA500BD85CA0114F00F843C46E23722DA8E8D9FC3A17
89A82C88B82377FAAD1DC7F2DCD3FF196CA9424728BA5044FD8648166EB1
DF71BBB51F1A8E72F464C4B860C8EBD066005E10D530FAE8868AC05A174B
AFF9276C2C7E593BC87830688480E3A41D86E15FEC8B655302764A3357FC
ED302EAB432802745F5E50038990728E710CB5A7AD3ED8B9811954978A0B
BCA01996019AB8638FF48C8B0003010001
WASTE_PUBLIC_KEY_END


This is a new idea and if its more secure i like that :}

Keep up the great work
:tu: :tu:

key added.

thanks for your interest in zer0share fennikishu & welcome to the p2p-zone! :beer:

- js.

hi and welcome..


:W:

i dont know if you realised it but..
this mesh is for sharing public domain content...

New Here
 

I'm new here and just found out about WASTE. Here's my public key. You just need to add me right, so I can connect?

WASTE_PUBLIC_KEY 20 1536 scoresby
E5D2C3E7D860DC91481A49FE5F801FDF927E592317E88F7705A5D122EDB9
98D15B981E09F2EBEC08AAEE5CB62ADD54BB8E4FBDF555B47131DD7DE3C8
300209749F4535B344A432AF9DDE4FEBAB263A1599FA81916E7CB2A94592
26B6A2B4DD4B4350AB9481AFF9B0E20E109CF3FAEC4C898B44B21547A57B
D931B8CF65119312D4092E5CBEFEE8D8A56080DB34E2FC678D5EE38FF189
88421586517B3DE33671CB6FDC619774A89143320D29B2876DFB852D64A7
3AB4CC7DDBDF98D7BC9B2F810003010001
WASTE_PUBLIC_KEY_END

welcome scoresby, i'm glad you discovered us. :ND: as long as you've configured the client properly, and you're using an original version you should be able to connect. under file | preferences | "network" check listen on port and enter 11150, and for "network name" enter zer0share as written. if you find yourself unable to enter the mesh call me on skype and i'll walk you in - username jackspratts. (www.skype.com/download)

see you soon.

- js.

oh what the hell ....... here it is


WASTE_PUBLIC_KEY 20 1536 Legion
E5221CB3A19135A091F5130BF5DC7061251AF81F7C490040F8F760DFE78F
D3A08C1A472485829C7D1ACAC30C78B1E9362816223CA90157CDD0F0C973
8D93E1D6F5BD6DA89DBD8EAE8317DDFAEE222F0CCED580BE3CDD05E4A69D
094C7AC1492442CA627F3EE2F20DF1DB0888E1120EEC214DCE09AF818CD8
19041E86CD72AE15E7C9D0CD73A0B68F68C2C1342D888214366B1A924D22
303BF300DDBDEDCA24F87EF248FAFE9B000AE39ACD2CF542E334F93AC2E3
6B33E3F9A025DE3A8C94B5C90003010001
WASTE_PUBLIC_KEY_END

yo jack check your PM's plz...thanx

Public domain, that's like Everything right? ;)

WASTE_PUBLIC_KEY 20 2048 Heathcliff
C43A9030DA3DB86A850490000EE29E5ADF270158EF6A309C00195D4938DC
BD4CB2A89EBF321E2F2ED1D8040FA7952EB8A71B5BA23F5D930A0F76B06F
861DAC71AC8076720307C0AE06B880CDAFEAB0292E4ABB987941162A9FEB
1E5ED2C0572CC88BBE8F5C75DE9458DEF2C4DC1E240A931158B963223B43
EEC9A59C250A326082E7E7D05BA41F32257E942930D4F7699FCCDF0EFE92
A373E50CC0B0CDB4321DD87ED67691E62E66FA8770CC06DCBF0ADC455AF9
935D55196A8FFE08635426B06498CFF6E619E8EBB0EAD83C2BB71D463994
5D87FADB82EB775A7AC400D39470BA1B5A48788663B1372EA51D92884C5F
E7ED85F9246B875D065835355123ED4D0003010001
WASTE_PUBLIC_KEY_END

Here you go...

WASTE_PUBLIC_KEY 20 1536 Kronsor
DA7D167F88C1C0388126131043A4B1D662AEB5EE125A1DF8BBD6BAFF15FA
9527B0C4957A238B88F322DB3ED793A927B2790A4610994E32A84091F698
951221A8042608F03FCD81D6F603DFC118B3B249C0F8557306F48BDEB7D0
45234FD99BD774C6EA7E1F9DD0DE7FE45FD0A61BD6A1009A2F63F7485147
D290F683E98776A8ECDBFE4C93AC365D20AEC9A7FD41B8117600BA04FB37
7165C25FD16F1EA31A12DF084A24B51C7EB55157BF004194DF5CB6D8078B
3EADF8B0103CDC76A7ECAD550003010001
WASTE_PUBLIC_KEY_END

I'm game...

WASTE_PUBLIC_KEY 20 1536 JedeyeNite
C47360236729CD34C99B21AA9A9575D98D254FB042E3413935A85D3CF7A1
05E8A329AD7B428E8CC3DEB07E9C63CA9488B8C96E4A8C40B6A043637285
BFD2691E8C6DA8B8192899D6667DC969D6709A1FEE314D4411ED864E1F0F
35158CEB22469619A2CBA6BC2FE74CCDC2B7F8BCAAB7901A5020A72BC998
56CC66931BCE0B3DD4E3D787FF362E81037DB91F836A620DC236F3D82A72
880DDDBC055B7B40FEA4AC8D6B6CA70B4D6CC457C0BCB11FEEF9D9E3EE34
4F7000358741D326DC7E0DEB0003010001
WASTE_PUBLIC_KEY_END

Static IP (on pretty much continuously) : 80.229.36.166

you're added and online mr. son and mr. nite. welcome to zer0share @p2p-zone. :beer:

- js.

Had a problem....
 

I had a few problems a little while ago, and, well, it ended with me getting a new public key. If you could replace my old one, I'd be very grateful.

Cheers, kingkakdw

post your new key and i'll put it up.

- js.

welcome to zer0share's newest member heathcliff. this should be interesting. :D

- js.

i can email you the program if u wanna send me a pm
and you can find out what its all about

This isn't my favourite program. :N:

?

perhaps if you actually tried it...

- js.

It's too late. I'm fueled by a blind, irrational hatred for Waste... bordering on the psychotic. :)

perfectly normal, perfectly healthy. :S:

- js.

whats the main thing you hate about it?

i was wondering what napho hates about it..nothing to serious
i dont go for programs that remind me of hotline..

It's not really a pathological hatred. :) I just don't think Waste is the most efficient way to acquire files. People seem to get them elsewhere, THEN share on Waste. I prefer to stick to the elsewhere. :ND:

waste and tor
 

im really noob in such things.......pls enlighthen me ... :W:

cant we use waste with tor?

and whats the diffrence of tor to those other socks softwares? i mean how its works in terms of relay and encryption ? :dunno:

thanks guys.

http://freehaven.net/tor/

actually, Waste is just another "elsewhere", but i know how you feel - i feel the same way about tofu.

There's no reason you couldn't. WASTE uses TCP, but it already makes use of public key cryptography so whether the traffic is anonymous or not, it can't easily be spied upon. ;)

I'm not sure whether WASTE has an option for using a socks proxy. :hmm: Take note of the following from the documentation :
It might be a bit overkill but if you're really paranoid you could give tor a whirl. :W: It's an interesting project in that the proxies are connected like a second-generation decentralised p2p network, rather than in the typical client-server fashion. :tu:

If you're new to WASTE though, try it out first until you're comfortable enough to use tor in conjunction with it. :p

ooh.ok thanks a lot for the info. :AP:

let us know how it goes if you try it with tor..
i agree waste is just another place to share files
you might not get top speeds
but..i dont mind slow stuff like edonkey ,i am on a shared home network so cant go maxing out the bandwidth too often...

i asked that idea becuase of the the ip concern in waste..as i understand our ip still shows ..so i thought of tor for that matter.im very new at this things in fact im dont know what the helll im doing.
anyway....i used sockscap in waste and tor...i used 2 pcs and tried to connect them....they did....and in my firewall logs..they have two difft ip.
the other was localhost and the other 199.173.10.10

too bad eversince i upgraded , i cant connect to you guys anymore. :(

i just got online again and tried waste and tor.....this time..difft pc and totally difft continent...so far no complains except initally while waste+sockscap trying to connect it seems waste is hangning and dead (sockscap is the culpprit) but as soon as the mesh is up the waste+sockscap becomes stable.
i just hope you can recommend a socckscap alternative.

bottomline.....the tor dnt gives your waste ip add.
now i would like your comments...does that mean waste+tor is reallly anonymous in every meaning of the word?

waste is made for small groups of trusted users ,that should not have to worry that the other users know each others ip

something like this might be good on those large public meshes tho..

WASTE_PUBLIC_KEY 20 1536 86LG4T5
DF019B1B7C5E589622810B98C274B4BEA5167AF6506C25FAE877DFB4EFAB
FAC24D991616DF1841F7DF6017D4DBA46C048B4522BACC5C2DF10AE95A61
6B5D7516F7D5356EDE00061879B5C3A36DA734F2E1C22C1C2F6665919E47
CAD04D2CCC8CE10868DADE0C1855A17DA54B6CF4AA3F539AFCD34A2910E5
F193E7EA2DE1C927D32B808357B941FC0EC00CA627DA5AF36F096DBCA988
497032CFFA1DF1F366BEBAA4CCD3368B74D0E2B01FA5F71BB7FDE0220633
F4E83635C43A6ADCCEB8DEEB0003010001
WASTE_PUBLIC_KEY_END

This one's for Mazer and Beatnik. Thanks guys! I'm mostly trying to make sure this works, so my library may not be huge or anything.

OH, that was for you too, JackSpratts! :W:

i was staying out of this one, it looked like a familly affair lol.

welcome to the p2p-zone OpieKanobe and of course to zer0share. your key was added sunday evening. :beer:

- js.

yall switch to1.5.2 yet? ill come back if you have.

defacto! long time lol. not yet. still playing with 1. :guitar:

- js.

ummpp..still playing with 1. :ick: ;)
ill jump in as soon as you guys int .2 ;)

many people got into waste within days (hours) of it's initial release over a year ago. immediately setting up meshes using the very first client, they invested a lot in creating (easy) and maintaining (hard) their world-wide social groups. they run on frankel's original client, the V. 1 and it’s initial upgrades. pulling the plug is not a step to take lightly, not without a great reason, and for some, joining another mesh full of strangers would not be one of them. V. 1 may have been orphaned by a handful of people at sourceforge and they may have felt they had that great reason, and from their perspective it's possible such a drastic step was necessary (time will tell), but it's equally true that without any major likelihood of being compromised all of these legacy networks run perfectly well on V.1 and will continue to do so into the foreseeable future. for obvious reasons these are not issues shared by waste newbies.

now should somebody create a client that ties them all together and turns meshes into NODES and SUPERNODES, you’d have the killer app that breaks out waste into the world at large and you might see early adopters making a major migration to the new client. on the other hand it may be that for some early users, perhaps even for most of them, the farther away the noobs move from V.1 the happier they get, while thanking sourceforge for the favor of turning the first meshes into really private places. so until such time as a breakout client arrives (if ever) a lot of these people will appreciate the meshes for what they are: small pods of friends hanging out, in tune, in touch, enjoying their quiet spaces, protected from the p2p tempests that always seem to disturb everyone but them.

- js

now i understand and agree ,though, can i ask this(im new at this things) so how about that null mesh i encountered? is that still one of those original mesh you are talking about?

null, which was originally the open mesh "mirwin", was fully migrated by members to the new client within hours practically of it's release.

i think it's still running but since my client can't connect anymore i can't tell you anything with certainty. it ran on port 1337. my guess is it still does.

while i encourage everyone to post the keys and other information that helps people connect to the fully open, non-controversial zer0share, i don't feel i can do that with other meshes, like null, without first talking to the users. perhaps someone here who's on it can help you with that. ;)

- js.

I'm back.. I told you
 

Hey Jack, I think I know what you need to get me back in the grind here, but I don't have a static IP, I haven't been through the whole thread yet, but here's my pubkey

WASTE_PUBLIC_KEY 20 1536 Zeke
E07024C56F9B35CC3736B8C6666CDF97211FBD7D11E8C357FAD1D2B27ECB
218E5BEE27186630FF94164D7FEC48AD1F6FA3D2F0F232936AF3CF7D95F5
E744BE622353E84791F3BC9E527CDB8C6730FBD152269F5F7A48BC99EAD1
E015EF436FA379EB0DFE0172939AD512CB852434A89C9758B6B97AA5209B
35FDFC91D2CDA7B8ADA34DBD47C231BA4306D63D438AB057E9C0E275F765
5A0E5D5F7FFB5C92A1DE2E3966123FE2D87BB28FFA4A506D2C0AB069BD55
A37976811D813CB728765F390003010001
WASTE_PUBLIC_KEY_END

Hope to join ya soon.

zeke!

welcome back. your key's added. if you need help, call me on skype when you see me around.

- js.

the site thingy said my key was invalid :(

but here is it:

WASTE_PUBLIC_KEY 20 1536 Japje
B4CF57251D17B8F33BC02343AE9AFC6B9EEC7359CD298BF2985183E8C19D
229B93E8B85E832F3896D4B9F5884F4B27B99213E5EFBA4A410DF8DDBF7E
C560CEC508A758818B3193F134FD2564131001CD330C5F329C5AF8011DE4
704FDDB124D8108C911AE386ECD5C93E3945DCD26EECF4B228AFF5704A79
05B45D39A6305F368FAC3F87C81512F0BB26C0EC6802245F5744F549C5E6
42D221252174934EF8C4CC3C26339936C947FEC4AACF7CC5BEDC375D04B4
53A00CF29BCCBA1F0B8236230003010001
WASTE_PUBLIC_KEY_END

ip = home.japje.nl
port = 11150

hi Japje and welcome to the p2p-zone. :beer:

your key's been inserted to zer0share. as long as you're using an original client you should be fine.

- js.

well, ive added lots of keys, and i try to connect to all the ip's that are listed here, like:
centauri.my-vnc.com:11150
aussiebeermatt.servebeer.com:11150
68.165.107.59:11150

but i cant get connected :(
ive set my port to 11150 in prefs, but no luck..
do i need to forward the port from my router?
( wouldnt make sense cause im dmz )

i dont have skype but you could always mail me on:
irc@ownt.nl or if that 1 doesnt work free@ownt.nl

out of the three ips you tried only
68.165.107.59
is connected to the zer0share mesh atm

you can pm me next time you try

then just leave it try and connect as long as possible

yup works like a charm multi! :)