souin VS caddy-security

HTTP plugin now support RFC 7234 caching options

It's always been blisteringly fast when we've used it, and I like the power of the configuration (it has its quirks but so do most powerful systems). But the overhead of setting it up and maintaining it due to having to handle TLS termination separately puts me off using it when other software is 'good enough'. If Varnish Enterprise was cheaper I would have bought it, but at their enterprise prices no way.

I'm keeping a watching brief on https://github.com/darkweak/souin and its Caddy integration to see if that can step up and replace Varnish for short-lived dynamic caching of web applications. Though I've lost track of its current status.

Centminmod (need lots of tweaks) or OpenLiteSpeed are consider more performant than default Nginx and Caddy, but I wish if someone can prove there is a better one out there or I just saw Souin HTTP cache (https://github.com/darkweak/souin) when I was reading Echo web framework for Go. Yet to experiment if there is a benefits unless it's insignificant.

There is no "refusal" as far as I can tell. The issues were reported [1] in September 2023 (as was this blog post) and the simplest one has been fixed (insecure random seed). I'm not aware of any public statements from the plugin maintainers, and there is no hostility in the issue comments.

[1]: https://github.com/greenpau/caddy-security/issues?q=is%3Aiss...

> September 18, 2023: The disclosure blog post was released and issues were filed with the original project repository.

I don't see those issues listed in the GitHub project issue tracker https://github.com/greenpau/caddy-security/issues. Have they been deleted?

Check out https://github.com/greenpau/caddy-security

There a pretty comprehensive auth plugin for Caddy. It can do local authentication with a session cookie, which should work with your IPTV apps. If your app can show a login form, it's super easy, but if I remember correctly you can also authenticate with basic auth and store the session in a cookie (this is mostly used to carry over the authentication to a different subdomain).

I use Caddy + Caddy Security, set up OAuth, and also only expose services over IPv6. It's not extra security, but it's less logs to deal with because nobody is scanning IPv6 address ranges, and there are less IPv6 capable hosts who are compromised.

Not sure if this fits your bill, but have a look at Caddy web server and its available authentification methods or even more with a plugin

Also look at github.com/greenpau/caddy-security to enable MFA for Caddy.

- Guacamole docker connects to Debian VNC Desktop - Caddy docker offers HTTPS proxy with Guacamole and the Caddy Security plug in for Auth with TOTP