| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | delete some dead code | Kartik K. Agaram | 2022-01-24 | 3 | -62/+0 | |
| | | | | | | I'm kinda sorta able to get lcurses running on NetBSD 9.2 without this particular hack. | |||||
| * | more generic build target in luasocket | Kartik K. Agaram | 2022-01-24 | 2 | -14/+14 | |
| | | ||||||
| * | clarify generic 'bsd' build target | Kartik K. Agaram | 2022-01-24 | 1 | -7/+13 | |
| | | | | | We still only have OpenBSD working. | |||||
| * | file permissions: clear stale errors | Kartik K. Agaram | 2022-01-16 | 1 | -0/+1 | |
| | | ||||||
| * | editing apps: clean up some stale prints | Kartik K. Agaram | 2022-01-16 | 1 | -0/+6 | |
| | | ||||||
| * | file access policy: support editing with >10 lines | Kartik K. Agaram | 2022-01-16 | 1 | -3/+5 | |
| | | ||||||
| * | kilo: cleaner go menu | Kartik K. Agaram | 2022-01-11 | 1 | -0/+2 | |
| | | ||||||
| * | some heuristic guidance on permissions screen | Kartik K. Agaram | 2022-01-04 | 1 | -2/+59 | |
| | | ||||||
| * | try running permissions advice after editing | Kartik K. Agaram | 2022-01-04 | 1 | -3/+21 | |
| | | | | | | This implies it must be side-effect free. We still need to figure out how to convey that to the computer owner. | |||||
| * | slightly better error message | Kartik K. Agaram | 2022-01-04 | 1 | -1/+6 | |
| | | ||||||
| * | reorg | Kartik K. Agaram | 2022-01-04 | 1 | -17/+17 | |
| | | ||||||
| * | feels more consistent to exit editor with ctrl-x | Kartik K. Agaram | 2022-01-04 | 1 | -3/+3 | |
| | | ||||||
| * | extract function | Kartik K. Agaram | 2022-01-04 | 1 | -23/+14 | |
| | | ||||||
| * | load permissions properly in a third place | Kartik K. Agaram | 2022-01-04 | 1 | -2/+9 | |
| | | ||||||
| * | when editing a function, show its callers | Kartik K. Agaram | 2022-01-03 | 4 | -10/+63 | |
| | | | | | | | No way to select between them. That complicates the UI too much when we do so much with the cursor. But it's still useful to suggest things to type in after ctrl-g. | |||||
| * | start saving callers of functions | Kartik K. Agaram | 2022-01-03 | 3 | -2/+55 | |
| | | | | | | I think this is significantly slowing things down. Perhaps we should sample or something. | |||||
| * | comment | Kartik K. Agaram | 2022-01-03 | 1 | -1/+1 | |
| | | ||||||
| * | rename | Kartik K. Agaram | 2022-01-03 | 1 | -2/+2 | |
| | | ||||||
| * | extract a function | Kartik K. Agaram | 2022-01-03 | 3 | -21/+24 | |
| | | ||||||
| * | events view: jump to a function | Kartik K. Agaram | 2022-01-03 | 1 | -7/+27 | |
| | | ||||||
| * | rendering improvement | Kartik K. Agaram | 2022-01-02 | 1 | -3/+2 | |
| | | ||||||
| * | error handling when editing file permissions | Kartik K. Agaram | 2022-01-02 | 1 | -1/+21 | |
| | | | | | | | | Still highly non-ideal. Lua is a dynamic language, and has low ability to detect syntax errors within functions. Perhaps I should run a test call after every edit. | |||||
| * | bugfix: policies must end in newline | Kartik K. Agaram | 2022-01-02 | 1 | -3/+3 | |
| | | | | | I believe kilo kinda naturally enforces that. We'll see. | |||||
| * | instrument some obvious syscalls | Kartik K. Agaram | 2022-01-02 | 3 | -1/+31 | |
| | | ||||||
| * | indent | Kartik K. Agaram | 2022-01-02 | 1 | -6/+6 | |
| | | ||||||
| * | start on a view of audit events | Kartik K. Agaram | 2022-01-02 | 3 | -2/+73 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-01-02 | 1 | -3/+0 | |
| | | ||||||
| * | editing file permissions | Kartik K. Agaram | 2022-01-02 | 2 | -42/+76 | |
| | | ||||||
| * | make some space for callers of a function | Kartik K. Agaram | 2022-01-02 | 1 | -13/+26 | |
| | | ||||||
| * | start parameterizing viewport for editor | Kartik K. Agaram | 2022-01-02 | 1 | -8/+18 | |
| | | ||||||
| * | drop os.getenv | Kartik K. Agaram | 2022-01-02 | 1 | -7/+1 | |
| | | ||||||
| * | editable file permissions | Kartik K. Agaram | 2022-01-02 | 4 | -51/+192 | |
| | | | | | | | | | | | | | | | | | | | | | | Extremely cruddy implementation: - I'm still unclear on how to represent the advice function: - How to handle errors when loading user configuration? Currently I refuse to start. - Whole function? More errors to handle in header and so on. What if the function is renamed? - Just body? Needs more structured editing support. - Lots of duplication, particularly between the permissions in the menu and the permissions screen. I don't know how to show the hostname at the time of connect() or bind(), so networking is going to remain a boolean for now. It's also unclear what effective constraints we can impose on what gets discussed with a specific hostname. Everything outside the computer is out of one's control. One trick I learned is for consistently grabbing ASan logs on abort: It's always safe to redirect stderr with ncurses! | |||||
| * | fork a new editor widget for non-code | Kartik K. Agaram | 2022-01-02 | 2 | -2/+49 | |
| | | ||||||
| * | better follow kilo's naming conventions | Kartik K. Agaram | 2022-01-02 | 2 | -6/+6 | |
| | | ||||||
| * | start peeling out an editor for non-code | Kartik K. Agaram | 2022-01-02 | 1 | -14/+21 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-01-02 | 2 | -1/+3 | |
| | | ||||||
| * | copy tweak | Kartik K. Agaram | 2022-01-02 | 1 | -3/+4 | |
| | | ||||||
| * | rename | Kartik K. Agaram | 2022-01-02 | 4 | -31/+31 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-01-02 | 1 | -1/+1 | |
| | | ||||||
| * | sandbox: tweaks to warning copy | Kartik K. Agaram | 2022-01-02 | 1 | -7/+8 | |
| | | ||||||
| * | sandbox: color tweaks | Kartik K. Agaram | 2022-01-02 | 1 | -4/+4 | |
| | | ||||||
| * | spacing | Kartik K. Agaram | 2021-12-26 | 1 | -0/+2 | |
| | | ||||||
| * | undo accidental color scheme commit | Kartik K. Agaram | 2021-12-25 | 1 | -1/+1 | |
| | | ||||||
| * | start persisting sandboxing settings | Kartik K. Agaram | 2021-12-25 | 1 | -0/+86 | |
| | | | | | Zero guarantees of compatibility at this point. | |||||
| * | reorg | Kartik K. Agaram | 2021-12-25 | 1 | -24/+24 | |
| | | ||||||
| * | network calls are now sandboxed | Kartik K. Agaram | 2021-12-25 | 1 | -1/+10 | |
| | | | | | | | | I _think_ I don't need to gate other socket calls; you can't do anything without bind() and connect(). And they should be good places to dump more precise details later about the kind of server or client connection being attempted. | |||||
| * | file open() is now sandboxed | Kartik K. Agaram | 2021-12-25 | 3 | -15/+36 | |
| | | | | | | | | In the process we now also have a mechanism for Teliva to overlay errors while apps run. Might make sense to make that available to apps as well. But I'm starting to realize that any app access to the Teliva areas of the screen is fraught with risk. | |||||
| * | flesh out very preliminary UI | Kartik K. Agaram | 2021-12-25 | 3 | -19/+154 | |
| | | | | | | | | Our sandboxing model is a blunt caricature, just two booleans. But let's see how far this gets us. Still doesn't persist, and definitely has no effect. | |||||
| * | fix a couple of colors | Kartik K. Agaram | 2021-12-25 | 1 | -2/+2 | |
| | | ||||||
| * | delete a couple more hacky function prototypes | Kartik K. Agaram | 2021-12-25 | 3 | -4/+3 | |
| | | ||||||