added mutex to protect self->table

[thejbte]

Related issue
#21562

Description

This PR fixes the race condition in remoted bug, the solution was add mutex to self->table.

Tests

1. delete Privsep_Chroot() and nowChroot() from remoted/main.c
2. delete fork from ῢremoted/main.c`

      i = 0;
   //while (logr.conn[i] != 0) {
   //    /* Fork for each connection handler */
   //    if (fork() == 0) {
   //        /* On the child */
   //        mdebug1("Forking remoted: '%d'.", i);
           logr.position = i;
           HandleRemote(uid);
   //    } else {
   //        i++;
   //        continue;
   //    }
   //}

3. add flags to compile with thread-sanitizer CFLAGS="-g -fsanitize=thread -fno-omit-frame-pointer" LDFLAGS="-g -fsanitize=thread -fno-omit-frame-pointer"
4. build wazuh like this sudo make clean && make clean-deps && rm -rf external/* && make -j12 deps && make -j12 TARGET=server DEBUG=1 CFLAGS="-g -fsanitize=thread -fno-omit-frame-pointer" LDFLAGS="-g -fsanitize=thread -fno-omit-frame-pointer"
5. copy the binary file sudo cp wazuh-remoted /var/ossec/bin/
6. kill wazuh-remoted process sudo kill -9 $(pidof /var/ossec/bin/wazuh-remoted)
7. run wazuh-remoted sudo /var/ossec/bin/wazuh-remoted -f -u root or /var/ossec/bin/wazuh-remoted -f -u root &> threadsanitizer.log in order to save the console output.

• Compilation without warnings in every supported platform
  • Linux
  • Windows
  • MAC OS X
• Source installation

[thejbte]

race_condition_original.log
solution_with_afewagents.log
solution_with_multipleagents.log