Potential fix for code scanning alert no. 24: Use of potentially dangerous function

[cwlacewe]

Potential fix for https://github.com/IntelLabs/vdms/security/code-scanning/24

To fix the issue, replace the use of std::localtime with the thread-safe version localtime_r, which requires explicit allocation of a struct tm on the stack and then passing its pointer to receive the result. We need to edit line 269 of src/Server.cc, allocate a local struct tm variable, and use localtime_r to populate it. The code that uses now_tm remains unchanged, except we reference our stack variable instead of the potentially shared static buffer.

Typically, C++ standard library does not provide a direct wrapper for localtime_r, but POSIX (localtime_r) is broadly available on Linux and macOS, which matches the includes and style here. We'll need to include <time.h> for the function signature in case it has not been included. The change is localized to the region around line 269; no other changes are needed in file or method.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[github-actions]

Target CPP Coverage: 68.113%
Source CPP Coverage: 68.1076%

Target Python Coverage: 97.94%
Source Python Coverage: 97.94%