OpenSSL 4.1.0 יצא: יכולות DTLS חדשות ובעיות מוכרות לבדיקה

Read this news or bug-fix article as reference material:
https://nethanelfitoussi.com/article/openssl-4-1-release-dtls-known-issues?lang=en

Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.

Use the article and its examples as references. Identify any missing project files before making changes.

If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.

Additional project setup instructions:
Evaluate whether my project needs OpenSSL 4.1.0 using https://github.com/openssl/openssl/releases/tag/openssl-4.1.0 and https://openssl-library.org/news/timeline/index.html . Treat October 23 as a feature-release date, not proof of a new emergency vulnerability. Inventory actual linked or bundled OpenSSL versions and vendor support, not only the openssl CLI. Check DTLS 1.3 and listener use against the release notes known issues. Keep compatible security updates on supported existing branches when a feature migration is unnecessary. Propose a staging test matrix for handshake loss/retry, provider compatibility and application HTTPS. Do not replace a system crypto library or deploy without approval.

Check the dated advisory and current official vendor guidance. Identify whether my installed version and configuration are affected before proposing a fix.

Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.