Z-Library Returns on the Clearnet in Full Hydra-Mode
torrentfreak.com
torrentfreak.com
Well I wouldn't go that far. There are more $5 wrenches than there are people.
The real test here was Assange who embarrassed the U.S. military by publishing drone footage of them killing civilians not to mention everything else.
They got him on an individual level (IMHO by blatantly discarding any remaining vestigial pretense of abiding by the law) but-- the site is up.
After the prosecution of Assange and Manning and with Snowden in exile, they've mandated to basically stop the whole whistleblower phenomenon in its tracks. Which was probably a bigger goal than one easily-replaced website.
It feels a bit like the Arab spring, a lot of hope in the beginning and then it all fizzled out.
Yes it has, the spook-friendly Bellingcat. It filled a Wikileaks-shaped hole.
See: Belarus, 2020 or Iran, 2022 for recent examples
there's a huge difference in knowing that your data has been compromised (you hand out the keys to avoid torture) and not knowing, that alone justifies every hoop you have to jump around to have your data encrypted.
besides, it doesn't apply here since onion services were created specifically to host content anonimously, they don't know who to torture.
1. Files are stored in a distributed fashion and referred to via their content hash. We already have IPFS for this.
2. Library metadata can be packaged up into a SQLite DB file. The DB would contain IPFS hashes, book names, authors, etc.
3. Teams of volunteers assemble and publish the library metadata DB files. There can be multiple teams, each with their own policies. The latest library files can be published via RSS. Each team can have their own upload portal.
4. A desktop app can pull multiple RSS feeds for multiple libraries. The libraries can be combined together and be searched easily on the client side. Users can search for content via the latest library metadata files, locally on their desktop. Content can be downloaded via IPFS.
5. The desktop app can also double as an IPFS host, allowing users to choose specific files to pin or simply allocate an amount of space for the purpose (100 GB, etc). There could also be servers that aggregate pinning info to make sure no gaps are there.
5. For ease of access, people can run websites that preclude the need to setup your own desktop app / download libraries.
6. Library teams can publish metadata DBs and content via torrents, too, for long-term/disaster-recovery/archival purposes.
This would be a true hydra. No one centralized team, no reliance on DNS. If one team's library set up goes down, you can use another's.
2. this would also need to be hosted and could be taken down. You'd need to mirror this too, but that's a simpler problem to solve (gigabytes instead of terabytes)
3. the upload portals and the RSS feeds would, again, be centralized or would have to change so regularly that they become impractical
in the end you would end up with a dozen (a hundred? more?) different z-libraries, which would make it actually worse from a preservation standpoint, since only the most popular content would be shared, libraries that focused on rare/exotic/fringe material would be endangered of being lost since they have fewer volunteers/mirrors/seeds/...
Also, freenet and other projects already showed that end-users allocating some storage and using that to spread data around is not an easy problem, the fluctuation in end-nodes is so big that it slows down the entire network to a crawl. I'm not sure this problem has been solved yet.
2. Well, users and librarians need some way to find each other. That's true in any system. And that communication medium can allow certain kinds of attacks. (website on the public internet, word-of-mouth, Telegram groups) If all someone needs is an IPFS hash of a recent library metadata DB (a SQLite file), any way of communication will suffice. I think this approach allows for centralization (sure, keep a website up as long a the authorities don't care) but also gracefully allows for all manner of de-centralization (use any of the above methods to distribute the metadata DB).
3. Any many-to-one system with curation (librarians) will have weak points. The idea is you can set up upload portals across any communication medium (a regular website, a dark-net site, a Telegram group, email) - and the libraries take care of collating the information. The social grouping is what matters more (libraries vs uploaders vs downloaders) - and we want to make it tech agnostic and, therefore, more resilient.
This system will be stable I think, for two reasons:
1. Network and branding effects will naturally create a few big libraries. People will use the familiar, useful libraries. See how few torrent search sites took up the bulk of traffic, back in the heyday of torrents. Most users will probably use a website, and the ones that are easiest to use will probably get the most traffic.
2. The resilience of the system is necessary only once in a while. A set of libraries will emerge, there'll be enforcement actions and they might break apart, and then new ones will pick up their pieces (easily bc the metadata and content is open). So we want to provide the open-ness for this to actually happen.
In fact, it fits in a tweet with enough room for steganographic deniability hijinks. You could publish a browser plugin which transforms tweets into IPFS CIDs according to a non-cryptographic hash algorithm. That way the cleartext of your tweet is not takedown-worthy, nor is the plugin, but the two together let users transform the seemingly innocuous tweet into the metadata DB update they need.
It's amazing that we can refer to data in a globally-unique way with small content-based hashes. Hash collisions aren't usually worth worrying about.
Another benefit is that its easy to store large numbers of hashes with basic metadata.
SHA-256 hashes are 32 bytes. If it takes 512 bytes on average to store author/title/publish-date/ISBN, then the hash is a small part of the total per item (though not well-compressible.) You can store the info for 2 million books in a megabyte.
Shadow librarians can also publish curated collections of books. I know a guy who tried to do this in a systematic way for college-level history textbooks covering a wide swathe of the world's history. The entire catalog with metadata and hashes is probably only a few hundred thousand KB.
There's some middle ground where we coordinate who pins what in a way where there's just enough enough redundancy to not worry about it disappearing, but not so much that any one of us is bearing an unnecessarily large burden.
I don't think we've quite figured that part out yet.
We do have a good example of this already I think: torrent client peer lists. When participating in a torrent, we can see the current availability of the data in the swarm, displayed usually as a bar visualization, with each pixel being a chunk. The darker the chunk, the more peers have a copy of that chunk. The result is also summarized in a number capturing the general health of the swarm wrt hosting the torrent.
All we need to do, then, is to have a mechanism where 1) the client has a list of items to pin 2) the client uses this existing swarm-tracking mechanism to figure out which files need more hosts 3) the client picks the best ones to host given the available space/network constraints. One can be smarter than just picking the lowest-seeded file. If a host is known to have files consistently, but is offline for a few hours a day, the client can be smart and not worry about immediately getting those files, perhaps spending available resources on less-seeded files.
This is possible with current technology. We can do a simple version of this via a torrent client plugin, reading the list of files from RSS or a special text file.
I've seen communities do this manually actually. For hosting SciHub torrents, the community made a web page that showed the current number of known seeds per torrent. Users were responsible for picking whichever ones, usually the lowest-seeded ones, and seeding them. We can remove this tedious and error-prone work.
Doing this per IPFS file will probably take up too many resources. Perhaps we need a standard IPFS<->torrent correspondence. Something as simple as a text file in the root of the torrent file structure, a file that maps IPFS hash <-> file inside the torrent. This way an IPFS swarm and a torrent swarm can work together. You get the easy retrieval of IPFS and the increased durability of torrent swarms.
I think we can come up with some scheme where it doesn't have to be centrally hosted. Like if my public key is 18 mod 256, then it's up to me to pin all of the files I rely on whose CID is also 18 mod 256.
If you've got thousands of users doing this, each one of them has to bear only 1/256th the burden.
I imagine incentive schemes where we keep track of which peers have gotten which files from our nodes, and then later randomly check to see if they're doing their part and pinning what they got from us
We'd all put $5 into a pot at the beginning of the month, and at the end of the month we'd share our data re: who seeded and who leeched. Maybe the bottom 10% leechers get no money back, the top 10% seeders get $10 back and everybody else gets their $5 back.
So it's like it costs $5 to access the first time, but if you leave a node running (like maybe you have a phone with a cracked screen that you just leave plugged in) then you'll never have to pay that $5 again, and if you're lucky you'll get $5 from a leecher.
Of course it doesn't make sense for all files anywhere, but in context with a project, like Z-library, where somebody is curating the files that are in scope. Otherwise an attacker could flood the network with noise that hashed in such a way that it affected only their target (and their target's 1/256 slice of the community).
Now passers-by can receive the message, time shifted, without the Internet.
[1] 0x.co
Now that I think about it again, I'm not sure what you'd use IPFS for that would require fast IPNS resolution anyway. Having version of a library that's an hour old is... just fine actually.
https://bafybeigpp6mtsmjngaqscfkjwzivbptt4ui5yb7uih6qe43obof...
You must learn about them.
https://bafybeigpp6mtsmjngaqscfkjwzivbptt4ui5yb7uih6qe43obof...
For me it has worked in Brave, Chrome, Firefox and Safari Tech Preview, with or without installed IPFS and IPFS Companion (with IPFS it works much better). Haven't worker in Safari in IOS and non-Chrome browsers on Android.
Not very fast and sometimes it requires page reloading but overall impression is awesome.
However, there is still the matter of having an account to get to these names. Which was the original reason the statists went after them in the first place. The users themselves will thus become the next target, just like in the days of Napster.
NAT "fixed" the problem of address exhaustion, but it killed the old internet. You cannot run your own network anymore. In the "old" times, I gave you a phone number or IP address and that's it, direct connection. All anyone could do was show up and take the computer to stop that. Sure there's a phone company or ISP involved, but they just powered the pump, you completely controlled what went through it.
Now I can't do that. They ran out of addresses and I share an address with X unknown others. So I can't give you a home address, just to a bank of doors. I could give you an apartment number, but that's also shifting transparently, so num X to you is num Y to someone else.
IPv6 would have solved the problem of exhaustion while preserving the right to an address. I could be some number permanently and you could reliably find a connection to my system using it. In that world I could set up a private DNS service in my house no one can alter without physically plugging in. Then have that store records to other addresses. Every part of that chain requires someone finding you and showing up at your door to disrupt.
Instead now I have to pay digital ocean 5 bucks to keep an address for me so anything can find me via them. A bunch of servers in my home effectively an island without a coordinate until DO points me out on request. Like having all mail addresses be to the local town hall for them to forward to me. Sure maybe you trust your local town hall, but they are fundamentally beholden to someone else.
With IPv6 support and adoption a whole network could be set up independent of any other authority besides BGP. Which requires nation-state levels of mobilization just to block an address, with fallout affecting literally thousands of others. They'd have to nuke a block to suppress any site, only for that site to find another address and be back to normal within minutes. Instead they do a WHOIS, send a scary email and boom, you're unknown, unfindable and disconnected. Hoping that word of mouth brings people to your new "address" exactly like losing your phone (and SIM) while abroad.
I know it sucks as a protocol but v6 to me is a massive extremely important development that would change how the internet, and from that all communication, works.
The only way around that is using naming systems that don't rely on centralized authorities, or at least can't be coerced by governments.
Suddenly someone shows up with address A and threats and then drowns trying to interpret that persons mappings. While that's happening I can find 5 other someones and suddenly I have 6 addresses all of which essentially ephemerally link to my system. Someone else does that for their mapping system and you get to Dijkstra levels of working out how to block connections.
After like 3 levels of middlemen even centralized authorities just struggle to do the actual work of blocking, outside of just issuing the order.
So I doubt those 5 new addresses will remain live for all that much longer. When you're on the lam, digitally or physically, or both, you find out who your real friends are, real quick.
On the other hand, I can type "tpb" into Google and get to a bittorrent of Disney's latest hits in less than 5 clicks, so maybe the copyright regime doesn't have an omnipotent hand on the Internet.
Your traffic is still going to specific IP address(es), but this isn't useful for someone trying to censor, unless they can persecute those running TOR nodes and/or prevent access to all TOR nodes.
Carrier Grade, CGNAT results in you not getting a public IP at all.
I'm pretty sure that wasn't me unless I have an alter ego called mister Hyde.
This is not how it works. Taking down a single IPv6 IP address (or whole AS) is a very simple thing and is done daily to combat spam and DDoS attacks, without requiring "nation-state levels of mobilization" (whatever that means). Also there is essentially no "fallout" at all in IPv6, and there isn't any fallout in IPv4, too, since BGP routes can be as specific as a single host
Private individuals have access to IPv4 blocks and maintain their own soverign networks. That fact doesn't change the reality that most people most of the time pay a network operator (ISP, Telecom) to operate their network. Network operators aren't going anywhere, and these network operators still maintain full control over how packets transit their network. In the case of WWAN networks, they will also know roughly where you are.
All IPv6 does is expand the address space and put the price of an address within reach of anyone... but it doesn't change the knowledge or hardware required to run your own network.
"The domain names in question are subdomains of newly registered TLDs that rely on different domain name registries."
There are multiple TLDs/SLDs involved (and the pool will likely grow over time)
Yes it is, but how do you discover the domains? There could be just a few hundred users per domain. Then you have to expend substantial effort to seize each domain.
Meanwhile any affected user just moves to their second domain. Even if the authorities got much better at taking down domains the only issue would be increasing the number of extra domains per user.
I can't see how the authorities can beat this.
> If users can’t access the universal login page, Z-Library says they can log in through TOR or I2P and get their personal clearnet domains there.
The GUID seems to be unique per-user, but also per ccTLD (mine are GUID.DOMAIN.cz and OTHERGUID.DOMAIN.ph).
I would guess that the pool of registered DOMAIN.ccTLD will grow faster than they can be blocked or seized, that new user per-domain GUIDs can be issued on demand onto different registered domains, and that there is an unused reserve of registered domains ready for deployment.
In my country they so this by asking all the ISPs to block the domain from their DNS servers. This works for 90% of the population, but all you have to do is just change the DNS server to something other than what the ISP gives you and you’re good to go.
Also, I just don’t get how current approach is any better. As far as I understand, there’s still a single point of failure, i.e. the site you get your “personal” domain from.
And if the actual web server is behind a service like cloudflare, the state can just ask cloudflare for the IP of the real server, then ask the datacenter who owns the server at IP x ...
Some domain registrars don't ask for your personal data and the registrars who ask for it won't verify them.
>then ask the datacenter who owns the server at IP x ...
Many datacenters in China and Russia doesn't care about some warez and if the zlib staff pays over Tor with cryptocurrencies the datacenter also don't know who rents the server
Eventually, you may buy a book that you know is worth it. Right now even the table of contents may not be available before buying.
From the list:
> 1lib.ae
> 1lib.in
> 1lib.io
> 1lib.mx
> b-ok.as
> b-ok.cc
> booksc.eu
> booksc.me
How does U.S. law enforcement get to seize domains under other countries' ccTLDs? Were the respective countries involved or did they just bully the operators who probably have name servers in the US?
And seizing domains is questionable in the first place - there isn't anything illegal about the domains itself and shouldn't the name -> IP association fall under free speech in the US?
Site operators could potentially re-render uploads and inject their own exploits.
I think it is more work to go to the single sign on, create an account, and save the custom domain names than just installing the tor browser and going to the zlib onion address?
Reading through the article, it seems the domain name is not publicly exposed and a new domain (?) is created on-the-fly? I am not sure if I understand how it works. But every user who logs in with a inter-mediator would get his own domain and that's their strategy to keep shop open for now.
Probably just a reference of Greek mythology. You chop one head, two grow. An analogue of spawning multiple domains a site is taken down.
The crucial line in that article; amusingly enough, it almost reads like a changelog entry.
Most of zlib is libgen, and I think libgen relies on user uploads and sourcing from their forums
Because “the government” is not a single unitary global institution.
In terms of system hardening, since the outer machines are almost bare, they are hard to hack. Attempting to attack the backend server isn't easy either (assuming the the webadmin knows what they are doing. Things like blocking outgoing traffic and configuring the system to not leak the backend server's IP)
> Cybercrimes are crimes committed through the Internet or using computer devices. These crimes almost always intersect with the postal system. That’s why the Postal Inspection Service is committed to protecting the public from criminals who steal digital information for financial gain, revenge, or even political advantage.
> These crimes almost always intersect with the postal system.
I don't understand this part at all.
One of the first articles that brought this up: https://news.yahoo.com/the-postal-service-is-running-a-runni...
See also: https://www.vox.com/policy-and-politics/2020/8/20/21377305/p...
https://www.google.com/search?client=firefox-b-d&q=.com+doma...