Trevor Vaughan

@justin-stephenson Hmm...after thinking about that briefly, I guess all the user would do by un-setting that variable would be to cause looping. While a DoS risk, I think people would...

Sorry for the multi-post, typing as I think :-|. So, the real issue is if someone sets that variable before running `tlog-rec-session` the first time.

Hmm...that's not horrible but it would still be nice to have something built in given that the `tty` behavior could change at any time.

@spbnick I think this comes back to what I was worried about in some previous discussions. As much as I'm willing to believe that `tlog-rec-session` is absolutely perfect, replacing the...

@spbnick I think that I've just reproduced this case using `tmux`. If you open up a single `tmux` session, split the screen, and then start logging your session in the...

@spbnick I understand the issue with monitoring users that can disable the monitoring. However, if that is the last recorded event that leaves the system, then that, in and of...

@spbnick I think that would be ideal. If you hack together the code, I'd be happy to PR the documentation caveats as to what does, and does not, work and...

@spbnick I think that something may have been unclear in the explanation. I get that you would get double logging if you do the following as the same user: *...

@spbnick Just checking in to see if you managed to reproduce the issue based on my last comment.

Hmm...that's quite possible but it certainly makes circumventing the whole thing pretty trivial. Would appending an internal add-on identifier work? `:` or the like?