I had code to support forcing read-only but it wasn't well tested and I'm not really convinced I want to go down the road of making security guarantees in tmux, I don't really trust the way screen does it and it seems rather complicated.
My thinking is that you should not give access to important sessions to people you do not trust. -r is a convenience against accidents and you should use social mechanisms to make sure people use it (ie, apply cluebat if they do not). I make no guarantees that -r is foolproof and doesn't allow access in some way. It is a good idea to use separate user accounts and/or a separate tmux server with -L or -S for shared stuff. On Mon, May 10, 2010 at 10:24:03PM +0300, Lars Nooden wrote: > I'm looking for a recipe for tmux to allow two different accounts to share > the same session, but the second user should have only read-only access > and not allowed to connect read-write. > > > If the full path to the socket is known, then it looks like -S can be used > by the second user to point to the first user's tmux server. > > tmux -S /tmp/tmux-1000/default attach-session > > Is there a shorter way to have the tmux client act as it normally does but > look for the other user's server by user name, not uid? > > > It looks like read-only can be done on a voluntary basis by the user > connecting to the server > > tmux -S /tmp/tmux-1000/default attach-session -r > > Is there a way to start a session to force additional windows to be read > only? screen had 'aclchg' or something like that. > > /Lars Nooden > > ------------------------------------------------------------------------------ > > _______________________________________________ > tmux-users mailing list > tmux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tmux-users ------------------------------------------------------------------------------ _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
