Shrimp was built since the great Squid was > 100,000 lines of code which made it difficult for us to audit. Further, we needed a forward proxy that worked in a very specific way:

Regular Mode

• Traffic goes over IPv4 or IPv6, whichever your stack decides

Lockdown Mode

• Traffic goes over IPv6 and uses NAT64 for IPv4, locked to a specific network interface

Shrimp will be very convenient for VPN providers who use Squid to provide forward HTTPS proxy services. Besides being lighter, Shrimp hashes passwords with bcrypt which is more secure at rest than the typical hashing used in other forward proxies.

For us, we built it so that we could provide a proxy appliance to our end users on Cloud Seeder which allows them to both run their own double hop proxy where they control one of the hops and also gain plausible deniability.

Here's a video of it in action in our appliance:

We hope you find this useful just like our other open source repositories!

[1] Shrimp was released a little under a week ago but was not shared due to limitations on post frequency! The wait was small, though and we hope you think it was worth it!

[2] Shrimp is licensed under COOL (no restrictions just include attribution)

Where can I find them now? It can be a bundle of servers from various places and I can pay upfront for a year or two.

root@mylocalmachine:~# ping -f [we still don't post IPs, right?].98 
PING 56(84) bytes of data.
................^C   
--- ping statistics ---
214 packets transmitted, 198 received, 7,47664% packet loss, time 3361ms
rtt min/avg/max/mdev = 242.600/278.443/320.271/17.202 ms, pipe 21, ipg/ewma 15.780/252.115 ms

it's similar to/from other euro machines in various directions, here's to OVH for example over IPv6, no difference really

root@LESVPS:~# ping -f my.machine.in.ovh
PING 56 data bytes
......................................................................^C 
--- ping statistics ---
521 packets transmitted, 451 received, 13% packet loss, time 8398ms
rtt min/avg/max/mdev = 157.012/160.179/197.734/4.014 ms, pipe 14, ipg/ewma 16.150/159.652 ms

once the connection is over the pond, it's perfect

root@LESVPS:~# ping -f 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
.^C 
--- 8.8.8.8 ping statistics ---
752 packets transmitted, 751 received, 0% packet loss, time 10536ms
rtt min/avg/max/mdev = 13.024/14.164/40.957/2.508 ms, pipe 4, ipg/ewma 14.029/16.485 ms

What's going on? Other LES nodes from Inception are fine but, obviously, the US proxy is most useful for getting around GDPR/cookie/geoIP nonsense.

[proxy domains] button missing for NAT VPS in solusvm.
Can you please help to check?

Oplution

I have used nginx for several years to run a busy website, bit since I gave up most of my online projects, nginx has never been touched again. I must admit that I forgot nearly everything that I knew about it.

I would now like to install nginx on a VPS to work as caching proxy in front of Apache.
Do you have any good configuration hints that you can share for the given use case scenario?
Any links to good sites with tutorials for this? I know that it is not overly complicated, I just do not want to miss any good config setting to get the best result possible and I am not aware of the options that nginx has to offer im the meantime...

Thank you very much in advance!