4 ms·
Another lost decades we're going to build our stacks on something that does not natively support arrays nor uses them by default. Why? It should be very clear w
by rini17 3y ago
Another lost decades we're going to build our stacks on something that does not natively support arrays nor uses them by default. Why? It should be very clear we need memory references which know how big the referenced area is and can trap out of bound access _at runtime_.
- sargstuff 3y agoNamespace security issues on who gets access to various physical memory available (and/or remote access) in multi-user environment usually handled by OS/supervisor program such as init. Everyone at work (tech & non-tech) does not need full root access to work server.
- rini17 3y agoYes, Unix/C architecture has the implicit assumption that accessing out of bounds memory is a non-issue because it affects only one process and thus it's perfectly safe even if it goes undetected. He he he (sad laughter).