Hi David,

The goal of *not* having the "latest" links was to make it harder for people to just fetch the latest stunnel from my server in their CI/CD pipelines (potentially, on each commit) instead of using their local mirror.  I see thousands of automated requests from a single IP address in my logs.

I guess I need to implement rate-limiting for those requests instead.  Alternatively, maybe I should try using CloudFlare CDN. I'd appreciate your comments and recommendations.

Best regards,     Mike

On 7/14/23 18:13, David Richard (CajunD) wrote:

Hi Folks,

I have found some older discussions about keeping archives and such, but wanted to ask if you could create an alias that always pointed to the latest version.

We were hard-linking to a version in /downloads/ and when version 5.69 was removed a few days ago, some automation on our end broke and (as a result of circumstance) caused an outage while we were trying to fix another problem with a remote dependency. We have altered our script to point to the archive version and added checking to ensure any future problems are handled properly.

That being said, we will always want the latest version of your software when we build our machine images. And while you do send an announcement, we have to take additional action on our end to get that new version. A “latest” link would allow us to get the latest version automatically when we perform security updates.

Thanks for considering this request.

David.

David Richard [email protected] _______________________________________________ stunnel-users mailing list [email protected] To unsubscribe send an email [email protected]