nail down trusted Teliva channels a little more

In each session, Teliva has to bootstrap a trusted channel with the
computer owner while running arbitrarily untrusted code. So let's get
really, really precise about what the trusted channel consists of:
  - the bottom-most row of screen containing the menu
  - the keystrokes the owner types in
  - ncurses COLOR_PAIR slots 254 (menu) and 255 (error)

One reason the menu colors are important: we don't want people to get
used to apps that hide the menu colors by setting default
foreground/background to invisible and then drawing their own menu one
row up.

The error COLOR_PAIR I don't see any reason to carve out right now, but
it seems like a good idea for Teliva the framework to not get into the
habit of apps doing some things for it.

I'm not sure how realistic all this is (I feel quite ill-equipped to
think about security), but it seems worthwhile to err on the side of
paranoia. Teliva will be paranoid so people don't have to be.

1 files changed, 0 insertions, 1 deletions

diff --git a/life.tlv b/life.tlv
index 606aca5..143de31 100644
--- a/life.tlv
+++ b/life.tlv
@@ -234,7 +234,6 @@
 - __teliva_timestamp: original
   main:
     >function main()
-    >  curses.init_pair(255, 15, 1)  -- reserved for Teliva error messages
     >  curses.init_pair(1, 22, 189)
     >
     >  -- initialize grid based on commandline args