<a href="http://2.bp.blogspot.com/-RfSp1Prm8Ns/YUOxaTgLFfI/AAAAAAAAvAE/SN4RCzdEi0Y5JMgSOfk7QtJ4oTb9HJ_hACK4BGAYYCw/s1600/PoW-Shield_7_screenshot-773941.jpeg" style="text-align: center;"><img alt="" border="0" height="290" id="BLOGGER_PHOTO_ID_7008640510588556786" src="http://2.bp.blogspot.com/-RfSp1Prm8Ns/YUOxaTgLFfI/AAAAAAAAvAE/SN4RCzdEi0Y5JMgSOfk7QtJ4oTb9HJ_hACK4BGAYYCw/w640-h290/PoW-Shield_7_screenshot-773941.jpeg" width="640" /></a> Project dedicated to provide DDoS <a href="https://www.kitploit.com/search/label/Protection" target="_blank" title="protection">protection</a> with proof-of-work<a name='more'></a> Description PoW Shield provides DDoS protection on 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: <ul> <li>proof of work authentication</li> <li>ratelimiting and ip blacklisting</li> <li>web application firewall</li> </ul> <a href="https://ruisiang.medium.com/pow-shield-application-layer-proof-of-work-ddos-filter-4fed32465509" rel="nofollow" target="_blank" title="Story on Medium">Story on Medium</a> 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: <ol> <li>The server generates a random hex-encoded “prefix” and sends it along with the PoW Shield page to the client.</li> <li>Browser JavaScript on the <a href="https://www.kitploit.com/search/label/Client%20Side" target="_blank" title="client side">client side</a> then attempts to <a href="https://www.kitploit.com/search/label/Brute-force" target="_blank" title="brute-force">brute-force</a> 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)</li> <li>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.</li> <li>The server starts proxying the now authenticated client traffic to the server with WAF filtering enabled.</li> </ol> <a href="https://github.com/RuiSiang/PoW-Shield/blob/main/USAGE.md" rel="nofollow" target="_blank" title="Usage">Usage</a> nodejs and docker <a href="https://github.com/RuiSiang/PoW-Shield/blob/main/CONFIGURE.md" rel="nofollow" target="_blank" title="Configuration">Configuration</a> environment variables Features <ul> <li>Web Service Structure</li> <li>Proxy Functionality</li> <li>PoW Implementation</li> <li>Dockerization</li> <li>IP Blacklisting</li> <li>Ratelimiting</li> <li>Unit Testing</li> <li>WAF Implementation</li> <li>Multi-Instance Syncing (Redis)</li> </ul> References <ul> <li>Proof-of-work by Fedor Indutny (PoW utility functions)</li> <li>Shadowd by Zesecure (WAF rules)</li> </ul> License BSD 3-Clause License Copyright (c) 2021, RuiSiang All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: <ol> <li> Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. </li> <li> Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. </li> <li> Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. </li> </ol> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. <div style="text-align: center;"><a class="kiploit-download" href="https://github.com/RuiSiang/PoW-Shield" rel="nofollow" target="_blank" title="Download PoW-Shield">Download PoW-Shield</a></div>

Tag

#Cybersecurity