AES128 | well commented 128bit AES implementation

see below (the code collects the tables data into a dict)

Thanks @so-cal-cheesehead you are correct the API was faulty

1. You should only gzip when it's requested by the client.

Accept-Encoding: gzip is never requested, but you gzip the response anyway.

So curl gives it back to you as-is.

2. Given the behavior of your browser, it sounds like double-compression. Maybe you have some HTTP reverse proxy in place which already handles compression to the browser, but doesn't compress backend traffic. So you may not need any gzipping at the backend at all - try curl --compressed to confirm this.

3. You should filter out Content-Length from the response. Content-Length is the final size of the compressed HTTP response, so the value changes during compression.

4. You should not blindly apply compression to all URI's. Some handlers perform gzipping already (e.g. prometheus /metrics), and some are pointless to compress (e.g. .png, .zip, .gz). At the very least strip Accept-Encoding: gzip from the request before passing it down the handler chain, to avoid double-gzipping.

5. Transparent gzipping in Go has been implemented before. A quick search reveals this gist (adjusted for point #4 above):

Your server/device seems to require some dummy keyboard interactive authentication:

Your server seems to issue two keyboard-interactive authentication challenges

• First, a prompt for a password
• Second, a banner with no prompts.

So you will have to do something like this:

I was probably over engineering it.

Setting the ssh.ClientConfig like this solved the problem:

So, between nginx and the world you can choose to let dockers ingress loadbalance to your nginx instances, or use an external loadbalancer. If you had a fixed set of nodes that an external loadbalancer was pointing to then

I solved my problem.
In keycloak docker compose file need to add reverse proxy location in KEYCLOAK_FRONTEND_URL
Like KEYCLOAK_FRONTEND_URL: "https://myhost.com/auth"

So the issue was I was using the wrong username, but it was still throwing a key authentication error.

Per @martin-prikryl's request, I attempted to connect using PuTTY, and found a nice tutorial specifically using PuTTY to SSH into Bluehost.

I had first written a script for FTP, and that used the Bluehost FTP account you can specifically create on their site. When I decided to write my SSH script, I used the same username. Alas, but for SSH, Bluehost wants the main login's username, NOT the FTP account one.

But it still recognizes the username on some level, but then the key is not linked to it, thus the key authentication error.

So I used PuTTy with the main username and that worked fine.

I then updated my script (credit to this stackoverflow post)

My new script that uploads an entire dir to bluehost using SSH: