• Earn real money by being active: Hello Guest, earn real money by simply being active on the forum — post quality content, get reactions, and help the community. Once you reach the minimum credit amount, you’ll be able to withdraw your balance directly. Learn how it works.

PoW-Shield v2.0 - provide DDoS protection with proof-of-work

Status
Not open for further replies.

itsMe

*KillmeMories*
Staff member
Administrator
Super Moderator
Hacker
Specter
Crawler
Shadow
Joined
Jan 8, 2019
Messages
56,607
Solutions
2
Reputation
32
Reaction score
100,454
Points
2,313
Credits
32,590
‎6 Years of Service‎
 
76%
screenshot-7306.png


A project dedicated to provide DDoS protection with proof-of-work

PoW Shield provides DDoS protection on the OSI application layer by acting as a proxy that utilizes proof of work between the backend service and the end-user. This project aims to provide an alternative to general captcha methods such as Google’s ReCaptcha that has always been a pain to solve. Accessing a web service protected by PoW Shield has never been easier, simply go to the url, and your browser will do the rest of the verification automatically for you.

PoW Shield aims to provide the following services bundled in a single webapp / docker image:

    proof of work authentication
    ratelimiting and ip blacklisting
    web application firewall

How it Works

So basically, PoW Shield works as a proxy in front of the actual web app/service. It conducts verification via proof-of-work and only proxies authorized traffic through to the actual server. The proxy is easily installable and is capable of protecting low-security applications with a WAF.

Here’s what happens behind the scenes when a user browses a PoW Shield-protected webservice:

    The server generates a random hex-encoded “prefix” and sends it along with the PoW Shield page to the client.
    Browser JavaScript on the client-side then attempts to brute-force a “nonce” that when appended with the prefix, can produce a SHA256 hash with the number of leading zero-bits more than the “difficulty” D specified by the server. i.e. SHA256(prefix + nonce)=0…0xxxx (binary, with more than D leading 0s)
    Client-side JavaScript then sends the calculated nonce to the server for verification, if verification passes, the server generates a cookie for the client to pass authentication.
    The server starts proxying the now authenticated client traffic to the server with WAF filtering enabled.

Features

    Web Service Structure
    Proxy Functionality
    PoW Implementation
    Dockerization
    IP Blacklisting
    Ratelimiting
    Unit Testing
    WAF Implementation
    Multi-Instance Syncing (Redis)

Changelog v2.0

    Support integration with PoW Phalanx Controller
    Update dependencies


To see this hidden content, you must like this content.
 
Status
Not open for further replies.
Back
Top