byobu

Bug #578373
Comment #2

Comment 2 for bug 578373

Revision history for this message

Yucong Sun (sunyucong) wrote on 2010-05-11: Re: [Bug 578373] Re: Use screen -UDR

I am not sure about your use cases.

Current byobu attach to an existing session automatically. and make
it display simultaneously on all clients.

Say I have an server to manage, and I have my wks-home at home and
wks-work at work.

I connect form my wks-work to server, created the byobu session.

Then I left work, at home, I connected from wks-home. I expect to
attach to the existing screen and then disconnect others, but right
now byobu will just continue the old session and still send all my
input to wks-work. This is unnecessary and dangerous, if my wks-work
is compromised , I can't even know whether there's some one already
snooping my screen.

I don't know what your use cases are, but from an system administrator
point, it should works just like consoles, you grab it, others lose
it, they can grab it back, then you lose it.

On Tue, May 11, 2010 at 12:02 AM, Dustin Kirkland
<email address hidden> wrote:
> Hmm, not sure about this one ...
>
> I just tested this, in /usr/bin/byobu-select-session, changing -xRR to
> -UDR.
>
> I don't think I like the behavior.
>
> Can you test it out a bit and tell me the advantages and disadvantages
> of changing it this way.
>
> ** Changed in: byobu
> Status: New => Incomplete
>
> ** Changed in: byobu
> Importance: Undecided => Wishlist
>
> --
> Use screen -UDR
> https://bugs.launchpad.net/bugs/578373
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in byobu: Incomplete
>
> Bug description:
> We should use screen -UDR as the launching parameters
>
> as noted in the man of screen.
>
> -D -R Attach here and now. In detail this means: If a session is running, then reattach. If necessary detach and logout remotely first. If
> it was not running create it and notify the user. This is the author's favorite.
>
> Or at least we should mark it as an optional thing or an flag in .byourc since it is hardcoded to screen in launcher now. Also, it is not secure to just default to "share" screens.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/byobu/+bug/578373/+subscribe
>

I am not sure about your use cases.

Current byobu attach to an existing session automatically.  and make
it display simultaneously on all clients.

Say I have an server to manage, and I have my wks-home at home and
wks-work at work.

I connect form my wks-work to server, created the byobu session.

I don't know what your use cases are, but from an system administrator
point, it should works just like consoles, you grab it, others lose
it, they can grab it back, then you lose it.

On Tue, May 11, 2010 at 12:02 AM, Dustin Kirkland
<dustin.kirkland@gmail.com> wrote:
> Hmm, not sure about this one ...
>
> I just tested this, in /usr/bin/byobu-select-session, changing -xRR to
> -UDR.
>
> I don't think I like the behavior.
>
> Can you test it out a bit and tell me the advantages and disadvantages
> of changing it this way.
>
> ** Changed in: byobu
>       Status: New => Incomplete
>
> ** Changed in: byobu
>   Importance: Undecided => Wishlist
>
> --
> Use screen -UDR
> https://bugs.launchpad.net/bugs/578373
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in byobu: Incomplete
>
> Bug description:
> We should use screen -UDR as the launching parameters
>
> as noted in the man of screen.
>
>  -D -R   Attach  here and now. In detail this means: If a session is running, then reattach. If necessary detach and logout remotely first.  If
>               it was not running create it and notify the user. This is the author's favorite.
>
> Or at least we should mark it as an optional thing or an flag in .byourc since it is hardcoded to screen in launcher now. Also, it is not secure to just default to "share" screens.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/byobu/+bug/578373/+subscribe
>