| commit | f268015ac089d26f9bb957dad53e94ae78a3d8a8 | |
| author | Kartik K. Agaram <vc@akkartik.com> | |
| Mon, 7 Mar 2022 23:40:28 +0000 (7 15:40 -0800) | ||
| committer | Kartik K. Agaram <vc@akkartik.com> | |
| Mon, 7 Mar 2022 23:40:28 +0000 (7 15:40 -0800) | ||
| tree | c5a4cbbdb1b7bed93be954c257d5df8615188d2e | treesnapshot (tar.gz zip) |
| parent | cfb7cff4c111959779710d0c8a9a89f108a9e8d1 | commitdiff |
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.
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.
| attack.tlv | diffblobblamehistory | |
| src/lua.c | diffblobblamehistory |