Client and Server in Python

The Idea: In your protocol, a client that wants to open a connection with a server will receive a challenge. The client must solve it, and send the solution to the server. The server will continue to communicate with the client only if the solution is valid. In this way, the number of requests that one client can do is limited by the time requested to solve the puzzle. The server will generate only a new puzzle for each incoming connection. Because programming at network level is more challenging than programming at application level, you do not need to directly modify the TCP protocol. You will simulate the TCP Trhee-way Handshake by implementing 2 different processes, one client and one server. Puzzle: You are free to design your own puzzle schema or implement an existing solution, but you can not use libraries with puzzle functions already implemented. In any case, your puzzle must have the following properties: • Construction difficulty: The challenge should be easy to construct, otherwise the re- source consumption problem in case of DoS attack is not mitigate but just shifted! • Solution difficulty: The challenge should not be too computationally heavy to solve, but enough to reasonably slow down the connection establishment beetwen client and server. • Verification difficulty: The puzzle solution should be easy to verify, in order to not add overhead at server side.