diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2022-03-08 19:20:53 -0800 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2022-03-08 19:20:53 -0800 |
| commit | 08c49b5a0a5784c499ad0439c1f3258ff3755db9 (patch) | |
| tree | ab62510dde1e56e9c4ddf59cfa875c2b32f9e027 /manual_tests | |
| parent | 2b47f763086cba3369a928c8e9d9d9543b844e37 (diff) | |
| download | teliva-08c49b5a0a5784c499ad0439c1f3258ff3755db9.tar.gz | |
protect framework files from apps
There's a separate open question here of where Teliva should store files like teliva_editor_state and teliva_editor_buffer. One school of thought is that apps should never be dropping crud into people's directories. On the other hand, I'm kinda encouraging people so far to just run apps from Teliva's directory. Perhaps that makes it ok?
Diffstat (limited to 'manual_tests')
| -rw-r--r-- | manual_tests | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/manual_tests b/manual_tests index de65a57..63bc108 100644 --- a/manual_tests +++ b/manual_tests @@ -25,10 +25,8 @@ running app.. shouldn't grow the call stack either. == security/privacy program draws over menu -> getch -> Teliva menu is still visible -test/attack.tlv runs without error. See its blurb for details. - -TODO protect sensitive teliva files (teliva_edit_buffer, etc.) - should we protect .c sources? +app tries to read/write sensitive teliva files (teliva_edit_buffer, etc.) -> never allowed + TODO should we protect .c sources? TODO protect against DoS attack filling up disk |