Talk:Features/Terminal Sharing - Revision history

Bemasc at 17:04, 6 December 2009

2009-12-06T17:04:29Z

← Older revision		Revision as of 13:04, 6 December 2009
Line 20:		Line 20:

	Is there a way that this technology could be achieved without the dependencies, while maintaining security? I'm wondering about sending input and output over encrypted tubes rather than relying on sshd, and using some kind of key event trapping to redirect input instead of screen. It would be nice to keep Terminal's scrollback functionality etc. while sharing. Perhaps you should post this activity to ASLO with instructions for installing the dependencies. Bonus points for trapping the lack of the dependencies and showing a legible error message at startup! [[User:Wade\|Wade]] 12:55, 21 September 2009 (UTC)		Is there a way that this technology could be achieved without the dependencies, while maintaining security? I'm wondering about sending input and output over encrypted tubes rather than relying on sshd, and using some kind of key event trapping to redirect input instead of screen. It would be nice to keep Terminal's scrollback functionality etc. while sharing. Perhaps you should post this activity to ASLO with instructions for installing the dependencies. Bonus points for trapping the lack of the dependencies and showing a legible error message at startup! [[User:Wade\|Wade]] 12:55, 21 September 2009 (UTC)

			: I'm not using SSH here to maintain any kind of security. In fact, it provides little cryptographic security, because the private key for the session is known and fixed. I'm using it simply because RSH (unencrypted remote shell) is no longer installed in most distributions. SSH is being used here to provide bidirectional terminal access over the network. This is difficult to achieve in any other way due to the notorious vagaries of the TTY subsystem.
			: I haven't found any easy way to achieve the desired functionality without using Screen and OpenSSH. These seem like fairly harmless dependencies to me, since OpenSSH is already installed on almost every Sugar machine, and GNU Screen is already installed on many or most Linux desktops.
			: In contrast to Terminal Sharing, Sayamindu has recently implemented a sort of [http://lists.sugarlabs.org/archive/sugar-devel/2009-November/020799.html "Terminal Watching"] functionality. He used the accessibility features of our Terminal widget to scrape the screen and send it over a tube. This is also interesting, and does not introduce any new dependencies. It is, however, a less powerful form of collaboration. [[User:Bemasc\|Bemasc]] 17:04, 6 December 2009 (UTC)

Wade: /* Feature Acceptance */

2009-09-21T12:55:57Z

Feature Acceptance

← Older revision		Revision as of 08:55, 21 September 2009
Line 16:		Line 16:

	: Additionally, as Eben noted, the functionality described here is quite close to Sugar's fundamental mission, and there is an argument for including it in Terminal. Making Screen a Sugar dependency allows us to make these kinds of decisions later. It also opens a door for other shared activities that make use of a shared command line. [[User:Bemasc\|Bemasc]] 17:57, 6 August 2009 (UTC)		: Additionally, as Eben noted, the functionality described here is quite close to Sugar's fundamental mission, and there is an argument for including it in Terminal. Making Screen a Sugar dependency allows us to make these kinds of decisions later. It also opens a door for other shared activities that make use of a shared command line. [[User:Bemasc\|Bemasc]] 17:57, 6 August 2009 (UTC)

			Hey Benjamin,

			Is there a way that this technology could be achieved without the dependencies, while maintaining security? I'm wondering about sending input and output over encrypted tubes rather than relying on sshd, and using some kind of key event trapping to redirect input instead of screen. It would be nice to keep Terminal's scrollback functionality etc. while sharing. Perhaps you should post this activity to ASLO with instructions for installing the dependencies. Bonus points for trapping the lack of the dependencies and showing a legible error message at startup! [[User:Wade\|Wade]] 12:55, 21 September 2009 (UTC)

Bemasc at 17:57, 6 August 2009

2009-08-06T17:57:38Z

@@ Line 1: / Line 1: @@
 This sounds quite fun and useful. Is there a reason this couldn't be integrated with the Terminal activity itself, with these features enabled when the activity is shared? -[[User:Eben|Eben]] 02:04, 25 July 2009 (UTC)
 == Feature Acceptance ==
@@ Line 6: / Line 12: @@
 what would be the downside of packing the needed packages inside the activity? I guess one criteria for adding to the platform is: is this worthy for several activities? -[[User:Erikos|Simon Schampijer]] 04 August 2009 (UTC)

Erikos at 11:02, 4 August 2009

2009-08-04T11:02:40Z

← Older revision		Revision as of 07:02, 4 August 2009
Line 5:		Line 5:
	Hi Benjamin,		Hi Benjamin,

	what would be the downside of packing the needed packages inside the activity? I guess one criteria for adding to the platform is: is this worthy for several activities?		what would be the downside of packing the needed packages inside the activity? I guess one criteria for adding to the platform is: is this worthy for several activities? -[[User:Erikos\|Simon Schampijer]] 04 August 2009 (UTC)

Erikos: /* Feature Acceptance */ new section

2009-08-04T11:01:44Z

Feature Acceptance: new section

← Older revision		Revision as of 07:01, 4 August 2009
Line 1:		Line 1:
	This sounds quite fun and useful. Is there a reason this couldn't be integrated with the Terminal activity itself, with these features enabled when the activity is shared? -[[User:Eben\|Eben]] 02:04, 25 July 2009 (UTC)		This sounds quite fun and useful. Is there a reason this couldn't be integrated with the Terminal activity itself, with these features enabled when the activity is shared? -[[User:Eben\|Eben]] 02:04, 25 July 2009 (UTC)

			== Feature Acceptance ==

			Hi Benjamin,

			what would be the downside of packing the needed packages inside the activity? I guess one criteria for adding to the platform is: is this worthy for several activities?

Eben: Created page with 'This sounds quite fun and useful. Is there a reason this couldn't be integrated with the Terminal activity itself, with these features enabled when the activity is shared? -~~~~'

2009-07-25T02:04:59Z

Created page with 'This sounds quite fun and useful. Is there a reason this couldn't be integrated with the Terminal activity itself, with these features enabled when the activity is shared? -~~~~'

New page

This sounds quite fun and useful. Is there a reason this couldn't be integrated with the Terminal activity itself, with these features enabled when the activity is shared? -[[User:Eben|Eben]] 02:04, 25 July 2009 (UTC)