guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Jumper (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GUACAMOLE-16) Implement text-based screen recording for SSH/telnet
Date Thu, 19 May 2016 05:44:12 GMT

     [ https://issues.apache.org/jira/browse/GUACAMOLE-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Jumper resolved GUACAMOLE-16.
-------------------------------------
    Resolution: Done

Completed prior to full migration to Apache infrastructure.

> Implement text-based screen recording for SSH/telnet
> ----------------------------------------------------
>
>                 Key: GUACAMOLE-16
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-16
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: SSH, Telnet
>            Reporter: Michael Jumper
>             Fix For: 0.9.10-incubating
>
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from [GUAC-1451|https://glyptodon.org/jira/browse/GUAC-1451],
an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the
Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance *have not
been copied* and can be found instead at the original issue.
> {panel}
> Guacamole should have the ability to record sessions for later playback. In the case
of SSH (or telnet), the full text underlying the session should be dumped to a file, with
the pure Guacamole protocol graphical session recording being left for [GUAC-236|https://glyptodon.org/jira/browse/GUAC-236]
(covering all protocols).
> Things to keep in mind:
> # The text-based output should be kept compatible with existing session recording formats,
like the two-file typescript output produced by the {{script}} command.
> # As the server will be dumping this text directly to a file, the name of this file will
need to be kept unique, and the corresponding connection parameters will need to be dynamic
enough that reasonable patterns can be specified (via parameter tokens?)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message