averageValentin

Appreciate the clarification. You're right that WebAssembly doesn't enforce bounds checking within its linear memory, allowing for out-of-bounds writes within the allocated space. While it does enhance security at the host boundary, it doesn't absolve the need for careful memory management within the WebAssembly module itself

Compiling to WebAssembly can mitigate certain issues, specificaly with memory safety in unsafe languages like C.

Take this C function: void write_to_buffer(char *buffer, unsigned int size, char value) { for (unsigned int i = 0; i <= size; ++i) { buffer[i] = value; // Unsafe: can write past the buffer if size is too large } }

Compiled to native code, an incorect size can lead to a buffer overflow. However, if you compile this to WebAssembly, the out-of-bounds write would be caught by the WebAssembly runtime, preventing a potential security flaw. But it doesn't eliminate the need for good coding practices, it does add a layer of protection against some kinds of memory-related errors

I've seen this too, and it's incredibly frustrating. Certs should be a stepping stone into the industry, not a stumbling block. It feels like the focus is more on making money from retakes rather than ensuring the test reflects actual job skills. The mismatch between study materials and test questions is disheartening for anyone trying to advance their career or break into a new field. We need a system where the effort put into learning is matched by the value of the certification gained.

Love the maze one

There have been a few documented cases where vertical transmission might have occurred, but it appears to be a rare event (most newborns tested shortly after birth are negative for the virus)

In-memory databases like Redis might be used to cache the key-to-scope relationship. However, the specifics of this implementation could be confidential.