3 ms·

Most of the things you mentioned are implemented in the "Browser" that I've built. It's using multicast DNS to discover neighboring running instances and it has

Most of the things you mentioned are implemented in the "Browser" that I've built. It's using multicast DNS to discover neighboring running instances and it has an offline cache first mentality, which means that e.g. download streams are shared among local peers. Global peer discovery is solved via mapping of identifiers via the reserved TLD, and via mutual TLS for identification and verification. So peers are basically pinned client certificates in your local settings. Works for most cases, had to implement a couple of breakout tunnel protocols though, so that peer discovery works failsafe when known IPs/ASNs are blocked. Relaying and scattering traffic works automatically, so that no correlation of IPs to scraped websites can be done by an MITM. Tunnel protocols are all generically implemented, DNS exfiltration, HTTPS smuggling, ICMP tunnels, and pwnat work already pretty failsafe. What's missing is UPnP support so that it behaves a little more gracefully when a router would be cooperative in nature, but after trying to implement the "specification" a bunch of times I skipped it for now. Lots of work to be done though, and had to focus on couple of other things first before I can get back to the project. The browser is part of a larger network that's trying to automate cyber threat intelligence on a peer to peer level, so clients, servers, websites and domains have a trust ratio and a history of trust to prevent misclassification of a new domain owner that e.g. defaced a website or tries to inject their malicious assets up unto previously trusted peers. [1] https://github.com/tholian-network/stealth https://github.com/tholian-network/stealth

pyinstallwoes 4y ago
Thanks for sharing your comment and contributing to the solution. I like what you're doing. Do you have a Discord? Is it a solo project? Working with a team or just "community pull-requests?" Curious about your trajectory.
- cookiengineer 4y ago
  Currently we only have a public (and another private) Telegram channel where we occasionally discuss upcoming features, problems and solutions to technical problems. The Stealth browser is kind of a solo project for now. It grew out of my personal intention to build a better architecture for a more efficient web scraper + browser that doesn't waste internet bandwidth, because I have pretty crappy internet abroad. But I'd love to grow a community out of it. Before the 4chan attacks last year there were a couple of other devs that occasionally contributed to the project, but they faded slowly away with the discreditation campaigns against me/us. As the 4chan raids led to us realizing that we're better at building cyber intelligence + defense products, we also pivoted with the company to this area because of it. The threat analysis mechanisms and peer-to-peer networking parts (with trust ratio of nodes/edges/paths) are very similar in nature, so it was a good fit, technology-wise. I'd still want to build the stealth browser further and make a better project out of it (especially with the RetroKit fork which is WebKit minus the tracking APIs), but I've pivoted with the company to a different area and that's currently the primary objective. As our country is regularly attacked by a lot of cyber threats right now, we've focussed our efforts on developing the cyber defense technologies. Right now, stealth is primarily being used as a Web Scraper via it's node.js APIs by us. So it's still actively used and occasionally we'll push some features to the repository.

pyinstallwoes 4y ago

Thanks for sharing your comment and contributing to the solution. I like what you're doing. Do you have a Discord? Is it a solo project? Working with a team or just "community pull-requests?" Curious about your trajectory.

cookiengineer 4y ago
Currently we only have a public (and another private) Telegram channel where we occasionally discuss upcoming features, problems and solutions to technical problems. The Stealth browser is kind of a solo project for now. It grew out of my personal intention to build a better architecture for a more efficient web scraper + browser that doesn't waste internet bandwidth, because I have pretty crappy internet abroad. But I'd love to grow a community out of it. Before the 4chan attacks last year there were a couple of other devs that occasionally contributed to the project, but they faded slowly away with the discreditation campaigns against me/us. As the 4chan raids led to us realizing that we're better at building cyber intelligence + defense products, we also pivoted with the company to this area because of it. The threat analysis mechanisms and peer-to-peer networking parts (with trust ratio of nodes/edges/paths) are very similar in nature, so it was a good fit, technology-wise. I'd still want to build the stealth browser further and make a better project out of it (especially with the RetroKit fork which is WebKit minus the tracking APIs), but I've pivoted with the company to a different area and that's currently the primary objective. As our country is regularly attacked by a lot of cyber threats right now, we've focussed our efforts on developing the cyber defense technologies. Right now, stealth is primarily being used as a Web Scraper via it's node.js APIs by us. So it's still actively used and occasionally we'll push some features to the repository.