Closed HiPhish closed 2 years ago
Forgot to mention: my system is Void Linux with glibc, software I am running:
I have solved it, my proxy specification was wrong. I should have installed Quicklisp as
(quicklisp-quickstart:install :path "/home/hiphish/.local/share/common-lisp/quicklisp" :proxy "http://localhost:8090/")
Now I can finally enjoy Quicklisp safely.
Hello,
I want to solved the security issue by performing an intentional MITM attack on myself and redirect all HTTP requests to HTTPS. I am using mitmproxy to intercept HTTP requests from Quicklisp and perform the corresponding HTTPS request, then forward the result back to Quicklisp. This should give me the security of TLS without having to modify Quicklisp itself. Here is how I started mitmproxy:
The proxy is running on port
8090
and the Python regular expression^http
will be replaced byhttps
in every request. Afterwards I install Quicklisp by invokingsbcl --load quicklisp.lisp
:This works fine at first, four HTTPS requests are performed:
GET https://beta.quicklisp.org/client/quicklisp.sexp
GET https://beta.quicklisp.org/client/2021-02-13/quicklisp.tar
GET https://beta.quicklisp.org/client/2021-02-11/setup.lisp
GET https://beta.quicklisp.org/asdf/3.2.1/asdf.lisp
However, after the last request
setup.lisp
times out. Here is the complete output of SBCL:Here is the backtrace:
If I choose to
CONTINUE
I get the message that Quicklisp has been installed correctly, however Quicklisp does not work correctly. I tried the following in a new SBCL instanceMitmproxy has not intercepted any new requests either since the original four, even though
(ql:config-value "proxy-url")
evaluates to"localhost:8090"
.