On Tue, May 11, 2010 at 03:02:00PM +0300, Lars Nooden wrote:
> On Tue, 11 May 2010, Nicholas Marriott wrote:
> > Yeah we should probably relax that to allow group permissions, try this.
>
> The patch itself allows tmux to tolerate a socket which has group read
> write permissions allowed. In pra
On Tue, 11 May 2010, Nicholas Marriott wrote:
> Yeah we should probably relax that to allow group permissions, try this.
The patch itself allows tmux to tolerate a socket which has group read
write permissions allowed. In practice, tmux recreates the socket or
resets the permissions back to the
On Tue, May 11, 2010 at 02:07:04PM +0300, Lars Nooden wrote:
> On Tue, 11 May 2010, Nicholas Marriott wrote:
> >I had code to support forcing read-only but it wasn't well tested and
>
> Is it available still? I tried changing the permissions of the tmux
> socket directory to 750 and 710 but tmux
On Tue, 11 May 2010, Nicholas Marriott wrote:
> I had code to support forcing read-only but it wasn't well tested and
Is it available still? I tried changing the permissions of the tmux
socket directory to 750 and 710 but tmux would not allow either to be
used, perhaps rightly so.
Here are the
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
