diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2022-03-07 15:40:28 -0800 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2022-03-07 15:40:28 -0800 |
| commit | f268015ac089d26f9bb957dad53e94ae78a3d8a8 (patch) | |
| tree | c5a4cbbdb1b7bed93be954c257d5df8615188d2e /src/luasocket/mbox.lua | |
| parent | cfb7cff4c111959779710d0c8a9a89f108a9e8d1 (diff) | |
| download | teliva-f268015ac089d26f9bb957dad53e94ae78a3d8a8.tar.gz | |
fix the security vulnerability
We now have a notion of libraries that we load after app code, to prevent them from getting overridden. Should I just load all libraries after the app? There might be value in allowing apps to override library functions. Disallowing that too much may be going against Lua's dynamic nature.
Diffstat (limited to 'src/luasocket/mbox.lua')
0 files changed, 0 insertions, 0 deletions