Hi,
Request review for integration of gtk-vnc into spec files.
Attached :
Solaris Spec : SUNWgtk-vnc.spec
Base Spec : gtk-vnc.spec
Copyright : SUNWgtk-vnc.copyright
Man Page : libgtk-vnc-1.0.3.txt
ARC Proposal : proposal-gtk-vnc.txt
Export Control : vinagre-2.x-gtk-vnc-0.x.txt
NOTE:
- OSR is approved
- Export Control: it is a combined form of gtk-vnc and vinagre.
materials pass JDS internal review and Irene send out for legal review.
- ARC : materials pass JDS internal review and Irene send out for ARC
review, LSARC/2008/707.
- Will add SUNWgtk-vnc-python25 after python25 binding for
SUNWgnome-python-libs is finished. Laca is doing it.
Thanks,
Halton.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SUNWgtk-vnc.spec
Type: text/x-rpm-spec
Size: 5297 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/jds-review/attachments/20081113/f2d3b363/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gtk-vnc.spec
Type: text/x-rpm-spec
Size: 4125 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/jds-review/attachments/20081113/f2d3b363/attachment-0001.bin>
-------------- next part --------------
Copyright 2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
------------------------------------------------------------------
For the avoidance of doubt, except that if any license choice other
than GPL or LGPL is available it will apply instead, Sun elects to
use only the General Public License version 2 (GPLv2) at this time
for any software where a choice of GPL license versions is made
available with the language indicating that GPLv2 or any later
version may be used, or where a choice of which version of the GPL
is applied is otherwise unspecified.
--------------------------------------------------------------------
Licensing and copyright information for gtk-vnc-%{gtk-vnc.version}:
License: GNU Lesser General Public License Version 2.1
You can find more information in the following directory:
%{_pkg_docdir}
AUTHORS: List of authors of gtk-vnc
COPYING.LIBS.bz2: GNU LGPL v2.1
ChangeLog: List of the most important changes in gtk-vnc
NEWS: List of the news in gtk-vnc
README: More information about gtk-vnc
plugin/gtk-vnc-plugin.c, plugin/gtk-vnc-plugin.h and src/x_keymap.c are
licensed under MIT:
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
plugin/npunix.c and plugin/npshell.c are licensed under MPL 1.1:
/* -*- Mode: C; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*-
*
* ***** BEGIN LICENSE BLOCK *****
* Version: MPL 1.1/GPL 2.0/LGPL 2.1
*
* The contents of this file are subject to the Mozilla Public License Version
* 1.1 (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
* http://www.mozilla.org/MPL/
*
* Software distributed under the License is distributed on an "AS IS" basis,
* WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License
* for the specific language governing rights and limitations under the
* License.
*
* The Original Code is mozilla.org code.
*
* The Initial Developer of the Original Code is
* Netscape Communications Corporation.
* Portions created by the Initial Developer are Copyright (C) 1998
* the Initial Developer. All Rights Reserved.
*
* Contributor(s):
* Stephen Mak <smak at sun.com>
*
* Alternatively, the contents of this file may be used under the terms of
* either of the GNU General Public License Version 2 or later (the "GPL"),
* or the GNU Lesser General Public License Version 2.1 or later (the "LGPL"),
* in which case the provisions of the GPL or the LGPL are applicable instead
* of those above. If you wish to allow use of your version of this file only
* under the terms of either the GPL or the LGPL, and not to allow others to
* use your version of this file under the terms of the MPL, indicate your
* decision by deleting the provisions above and replace them with the notice
* and other provisions required by the GPL or the LGPL. If you do not delete
* the provisions above, a recipient may use your version of this file under
* the terms of any one of the MPL, the GPL or the LGPL.
*
* ***** END LICENSE BLOCK ***** */
The sources of gtk-vnc-%{gvnc.version} were downloaded
from %{gvnc.SOURCE0.url}
-------------- next part --------------
INTERNATIONAL TRADE SERVICES
Software Export Classification Questionnaire
(REV 32, May 30th, 2001)
ALERT
If encryption is used for data privacy/ confidentiality, a One Time Review
by the US government is required, regardless of key length.
------------------------------------------------------------------------
In order for International Trade Services to determine the export
license required for the export of all software, the following
questionnaire must be filled out by the responsible engineer and/or
product manager 13 WEEKS PRIOR TO INTERNATIONAL SHIPMENT.
Your answers MUST be COMPLETE and ACCURATE. Sun's compliance with
US export laws depends on your cooperation.
------------------------------------------------------------------------
SECTION A. BASIC INFORMATION
1. Date of completing this questionnaire:
Nov 07, 2008
2. Name and Version number of Software (any code names?):
- gtk-vnc 0.x
- Vinagre 2.x
3.a Sun Division (No acronyms please):
New Solaris Group
3.b Developing Group (No acronyms please):
Desktop
4.a Name of Program / Product Manager:
Irene Huang
4.b Email (firstname.lastname at sun.com):
Irene.Huang at Sun.COM
5.a Name of Technical Contact:
Halton Huo
5.b Email (firstname.lastname at sun.com):
Halton.Huo at Sun.COM
6.a Name of person completing this questionnaire:
Halton Huo
6.b Email (firstname.lastname at sun.com):
Halton.Huo at Sun.COM
------------------------------------------------------------------------
7. Description of Product, its features and functionalities:
gtk-vnc is a VNC viewer widget for GTK. It is built using
coroutines allowing it to be completely asynchronous while
remaining single threaded. It provides a core C library, and
bindings for Python (PyGTK)
Vinagre is a VNC client for the GNOME Desktop. It uses gtk-vnc
to preform VNC operations underly. It's features are:
- Connect to several machines at the same time
- Keep track of your most used connections
- Keep track of your recently used connections
- Browse your network for VNC servers
- Don't need to supply the password on every connection
Notes:
- gtk-vnc implements its own 3DES algorithm, and makes use of GnuTLS
for other usages of encryption. GnuTLS which is discussed in a separate
Export Control form.
- GnuTLS also makes use of libgcrypt.
- Vinagre doesn't have any encryption/coding algorithms itself, but it
uses the interfaces provided by gnome-keyring to load/save the password
for VNC connections. It uses the functionality of gtk-vnc to perform
VNC operations.
For more information, you can refer to
http://sf.net/projects/gtk-vnc
http://www.gnome.org/projects/vinagre/
7.a. Will you be sending on any supporting product information ?
NO
------------------------------------------------------------------------
8 a. Is this a third-party (non-Sun) Software ?
YES
Note: If this software is just a repackaging of a 3rd-party software,
with NO modifications or additions by Sun's engineers, then only
complete items 1, 2, 3, 4, 5, 6, 8.a, 9 and 10 of this questionnaire.
i) Full name of third-party Vendor(s):
Vinagre comes from GNOME Community.
gtk-vnc is open source origin, and supported by the
community at: http://sf.net/projects/gtk-vnc
ii) Name and Version Number of third-party software(s):
Vinagre 2.x
gtk-vnc 0.x
iii) Does the vendor have an ECCN certification on file for this
version?
NO
8 b. Does this software incorporate third-party software ?
YES
If yes, please give the following information for ALL components.
i) Full name of third-party Vendor(s):
GNOME Community
GNU Community
ii) Name and Version Number of third-party software(s):
- GnuTLS 2.4.0 GNU Community
- libgcrypt 1.4.1 GNU Community
- Gnome 2.24 GNOME Community
iii) Does the vendor have an ECCN certification on file for this
version?
NO
iv) Is the third-party software offered in global/international
version with 0-56 bit encryption as well as a domestic version
with greater than 56-bit encryption ?
NO
v) If yes, which version(s) are you using ? (Please specify the
key length in each version):
N/A
vi) Is the vendor's binary code used in Sun's product ?
NO
vii) Is the vendor's source code used in Sun's source product?
YES
------------------------------------------------------------------------
ALERT - If encryption is used for data privacy/ confidentiality, a One
Time Review
by the US government is required, regardless of key length.
9. In how many versions will this software be produced ?
Note: By "versions", we are only interested in encryption key length.
e.g. a version with 0-56 bit encryption, another with greater than
56-bit; Not domestic vs. L10n versions, nor platforms.
Please select one: D
A. One version only, since no encryption involved.
B. One version with 40-bit encryption.
C. One version with 56-bit encryption.
D. One version with 128-bit (or greater than) encryption.
E. One version with up to but not exceeding 56-bit encryption,
plus a separate encryption kit
F. Two versions (one with 40-bit, one with 128-bit or higher)
G. Two versions (one with 56-bit, one with 128-bit or higher)
H. Three versions (one with 40-bit,one with 56-bit, one with
128-bit or higher)
I. Other combination
Please give details;
------------------------------------------------------------------------
10. Marketing & Manufacturing part numbers (if applicable):
Can you provide us an approved ECO or list of marketing/manufacturing
part numbers at this time ? If not, can someone sent it to us when
available ?
Advise below location of list, or who will send it on.
N/A
This version will be a full supported, branded product available
in Solaris as part of our ongoing work in the Solaris Nevada release
schedule.
------------------------------------------------------------------------
11. Development Timeline ?
a) Alpha YES/NO Date:
b) Beta YES/NO Date:
c) FCS YES/NO Date:
The GNOME community releases new versions of Vinagre regularly.
Also the gtk-vnc community releases new versions of gtk-vnc regularly.
It is our intention to update to newer versions of Vinagre in
accordance with the overall JDS schedule, which typically involves
updating the software in OpenSolaris and Nevada every 6 months.
------------------------------------------------------------------------
12. Product will be exported in the following form(s) (Select One Only)
a) Source only NO
b) Object (Binary) only NO
c) Source & Object YES
------------------------------------------------------------------------
13. a) How will the product be distributed ?
Please select;
Web-Based (electronically): YES
CD: YES
Other: N/A
If Other, please specify: N/A
b) If electronically, please identify server(s) or URL(s) where
the software will be posted. If you are using different servers
for pre-FCS versus FCS, please list ALL servers.
Name of Server/url (pre-FCS): http://jds.ireland,
http://www.opensolaris.org,
http://dlc.sun.com
Name of Server/url (FCS): http://dlc.sun.com,
http://pkg.opensolaris.org
c) If CD, who is the vendor/supplier ?
Refer to the usual practices and distributions as with the
Solaris Operating Environment.
d) Please specify target customers/audience:
i) Is the product for Sun internal access ONLY ?
NO
ii)Is the product accessible to external customers ?
YES
e) Is the product free of charge ?
YES
f) Are there any restrictions on who can download the software
from this server?
NO
If yes, please describe:
g) Please identify server name and the party responsible for
server management, if available.
i) Name of Server: http://dlc.sun.com,
http://www.opensolaris.org,
http://pkg.opensolaris.org
ii) Responsible Person: Bonnie Corwin
------------------------------------------------------------------------
14.a) Is the product embedded or preloaded in hardware ?
NO
14.b) If yes, please give name of hardware and its Marketing and Mfg.
numbers:
N/A
------------------------------------------------------------------------
SECTION B. TECHNICAL INFORMATION
(Note: This section MUST be completed by the engineers and must
be COMPLETE and ACCURATE)
1.a) Can this software be used on any kind of computers, regardless
of the computer's performance level ?
NO
1.b) What is the minimum hardware CPU requirement for running this
software ?
Minimum is the same as Solaris' minimum.
------------------------------------------------------------------------
2. Does the product include FIXED data compression or coding
(e.g. Lempel Ziv) ?
Note: Fixed means the coding or compression algorithm cannot accept
externally supplied parameters (e.g. cryptographic or key variables) and
cannot be modified by the user.
YES
2.a If Yes, please explain;
gtk-vnc uses inflate() from zlib for decompressing the compressed
data from VNC server.
------------------------------------------------------------------------
3. Does the product use, call on, or contain an encryption algorithm?
YES
If Yes, please provide detailed answers to *ALL* questions below;
------------------------------------------------------------------------
When answering below questions, please give answers for ALL the
versions, i.e. 40-bit, 56-bit, and 128-bit.
4. NSS (Network Security Services) and JSS (NSS for Java) are crypto
libraries used by iPlanet servers and many other products. See
http://www.mozilla.org/projects/security/pki/ for more information.
4.a Will your product use NSS or JSS to perform encryption functions?
NO
4.b If Yes, which version(s) ? (e.g. NSS v3.2, JSS 3.0) ?
NSS v:
JSS v:
4.c Are NSS and/or JSS the *only* encryption technologies in your product
(other possibilities include Kerberos, IPSec, etc.) ? YES/NO
NO
4.d Does your product use the official iPlanet build of NSS/JSS ?
NO
If you answered YES to ALL the above questions, you may skip the
rest of this form and submit <swclass.form.html#submit> it immediately.
------------------------------------------------------------------------
5. If this is a dot release, are there any differences in the
cryptographic
implementations in this version from the last version ?
NO
5.a) If Yes, please explain in detail;
------------------------------------------------------------------------
6. Is encryption used for User Access Control and Authentication ?
YES
6.a Algorithm used:
3DES - implemented in gtk-vnc
RSA - implemented in libgcrypt
DSA - implemented in libgcrypt
6.b Key Length:
3DES: 168 bits
RSA: 1024-2048 bits
DSA: 1024 bits
6.c Please describe in detail the techniques used;
The authentication method between VNC server and client is decided by
server.
If server does not have GnuTLS support, it uses 3DES to authenticate
client. The steps are:
1) Server sends a random 16 byte challenge
2) Client encrypts the challenge with DES using the user supplied
password as a key and send back to server
3) If the response matches the expected result, the client is authenticated.
Otherwise, the server closes the connection.
If server does have GnuTLS support, gtk-vnc uses GnuTLS anonymous
or X.509 certificate authentication as a way to authenticate a client.
Then, gtk-vnc uses the steps described above to finish.
For GnuTLS anonymous authentication, refer to
http://www.gnu.org/software/gnutls/manual/html_node/Anonymous-authentication.html#Anonymous-authentication
For X.509 certificate authentication, refer to
http://www.gnu.org/software/gnutls/manual/html_node/Certificate-authentication.html#Certificate-authentication
------------------------------------------------------------------------
7. Is encryption used for Data Authentication ?
YES. gtk-vnc uses GnuTLS anonymous or X.509 certificate authentication.
7.a Algorithm used;
Refer to B-9
7.b Key Length;
Refer to B-9
7.c Please describe in detail the techniques used;
Refer to B-9
------------------------------------------------------------------------
8. Is the encryption used for Data Privacy / Confidentiality ?
YES
8.a Algorithm used for data encryption and decryption:
Refer to GnuTLS B-8.a
8.b Key Length:
Refer to GnuTLS B-8.b
8.c Please describe in detail how this functionality is done;
Refer to GnuTLS B-8.c
gtk-vnc initializes GnuTLS session to support TLS1.1, TLS1.0 and SSL3.0
protocols.
GnuTLS itself will decide which protocol is to be used.
------------------------------------------------------------------------
9. Please explain Key Management features. List the algorithms and
associated key lengths;
gtk-vnc uses key exchange algorithms offered by GnuTLS, refer to GnuTLS B-9.
gtk-vnc initializes GnuTLS session to use different key exchange algorithms.
If using anonymous authentication, then the Diffie Hellman key exchange
algorithms are used. Key length is up to 256.
If use non-anonymous authentication, gtk-vnc initializes GnuTLS session to
supports four kind of key exchange algorithms:
- DHE_RSA
- DHE_DSS
- RSA
- SRP
Please refer to
http://www.gnu.org/software/gnutls/manual/gnutls.html#Certificate-authentication
------------------------------------------------------------------------
10. Please briefly describe how this product has been written to
preclude user modification of the encryption algorithm, key management
mechanism and key space;
N/A
------------------------------------------------------------------------
11. Does this product perform any pre-processing information
of plaintext data before encryption
(e.g. compression of the data) ?
NO
11.a If yes, please describe briefly;
------------------------------------------------------------------------
12. Does this product perform any post-processing information
of cipher text data after encryption
(e.g. packetization of the encrypted data) ?
YES
12.a If yes, please describe briefly;
Refer to B-3
------------------------------------------------------------------------
The following questions pertain to the issue of "Open Cryptographic
Interface". Please answer all 3 parts of the question in detail.
13.a Is the interface one that implements a fixed set of
cryptographic algorithms, key lengths or key exchange
management systems, that CANNOT be changed ?
NO
If yes, please describe;
13.b Is the interface a general application programming interface
(e.g., one that accepts either a cryptographic or non-cryptographic
interface but does not itself maintain any cryptographic
functionality) ?
NO
If yes, please describe;
13.c Is this interface an Open Cryptographic Interface ?
NO
Definition of "Open cryptograhic interface": A mechanism which is
designed to allow a customer or other party to insert cryptographic
functionality without the intervention, help or assistance of the
manufacturer or its agents, e.g. manufacturer's signing of cryptographic
code or proprietary interfaces.
If yes, please describe in detail how you propose to close it;
------------------------------------------------------------------------
14. Is this product written in Java ?
NO
If yes, which of the following techniques are used to protect against
decompilation ? Check all that apply and describe.
14.a Symbolic Obfuscation - Scrambling of the symbolic table
or scrambling of the byte code ?
NO
If yes, please describe;
14.b Structural Obfuscation - Using techniques to make the
code less readable. E.g. changing the function names,
i.e. "Encrypt with DES" becomes "Process Block" ?
NO
If yes, please describe;
14.c XOR Masking - For vendors that write their own Java Virtual
Machines (VMs), this provides load time obfuscation. The code
has an XOR mask over all the byte code. Classes reside on the
computer in XOR form. When they are loaded, they are
XOR'd back to the original class. Mask is hidden. ?
NO
If yes, please describe;
14.d Mark classes final - A final class means that features cannot
be extended or inherited to other classes - cannot be subclassed ?
NO
If yes, please describe;
14.e Rename attributes and function variables - Attributes
and function variables to the encryption classes have been
renamed to hide their true function ?
NO
If yes, please describe;
14.f Static linking - Encryption routines are statically linked.
Note: If dynamically linked, additional protective measures
will be required ?
NO
If yes, please describe;
------------------------------------------------------------------------
We will attempt to provide a response within one (1) week of
receipt of a completed questionnaire. It is understood that best
effort will be put forth and that one (1) week may not always be
enough time.
-------------- next part --------------
C Library Functions libgtk-vnc-1.0(3)
NAME
libgtk-vnc-1.0 - a VNC viewer widget for GTK
DESCRIPTION
gtk-vnc is a VNC viewer widget for GTK. It is built using
coroutines allowing it to be completely asynchronous while
remaining single threaded. It provides a core C library, and
bindings for Python (PyGTK). It also provides a web browser
plugin featuring a Gtk VNC widget which can be embedded in a
web page.
It can be used with virt-manager(1) and vinagre(1).
FILES
The following files are used by this library:
/usr/lib/libgtk-vnc-1.0.so
API shared library
/usr/lib/firefox/plugins/gtk-vnc-plugin.so
gtk-vnc plugin for firefox
/usr/lib/python2.4/vendor-packages/gtkvnc.so
gtk-vnc module for python 2.4
/usr/lib/python2.5/vendor-packages/gtkvnc.so
gtk-vnc module for python 2.5
ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWgtk-vnc |
|_____________________________|_____________________________|
| Interface stability | Volatile |
|_____________________________|_____________________________|
SunOS 5.11 Last change: 11 Nov 2008 1
C Library Functions libgtk-vnc-1.0(3)
SEE ALSO
firefox(1), python(1), vinagre(1), virt-manager(1),
libgnutls(3), libz(3), attributes(5), gnome-interfaces(5)
http://sf.net/projects/gtk-vnc
NOTES
Written by Halton Huo, Sun Microsystems Inc., 2008.
SunOS 5.11 Last change: 11 Nov 2008 2
-------------- next part --------------
Template Version: @(#)onepager.txt 1.35 07/11/07 SMI
Copyright 2007 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
tsclient
1.2. Name of Document Author/Supplier:
Halton Huo
1.3. Date of This Document:
07/22/08
1.3.1. Date this project was conceived:
03/26/07
1.4. Name of Major Document Customer(s)/Consumer(s):
1.4.1. The PAC or CPT you expect to review your project:
Solaris PAC
1.4.2. The ARC(s) you expect to review your project:
LSARC
1.4.3. The Director/VP who is "Sponsoring" this project:
robert.odea at sun.com
1.4.4. The name of your business unit:
OPG / OpenSource.
1.5. Email Aliases:
1.5.1. Responsible Manager:
harry.lu at sun.com
1.5.2. Responsible Engineer:
halton.huo at sun.com
1.5.3. Marketing Manager:
glynn.foster at sun.com
1.5.4. Interest List:
desktop-discuss at opensolaris.org
4. Technical Description:
4.1. Details:
tsclient (Terminal Server Client) is a frontend for rdesktop and other
remote desktop tools. It is a GNOME application. Notable visual
options include color depth, screen size, and motion blocking.
Features include:
- a GNOME panel applet to quickly launch saved profiles
- similar look and functionality to the Microsoft client and
compatibility with its file format
- support for rdesktop(1) 1.3, uttsc(1), Xephyr and VNC clients like
vncviewer(1)
/usr/bin/tsclient is a GUI wrapper tool. When it starts up, user can
choose connection protocol from a combo box. Depending on the protocol
chosen, it will call the relevant programs and with corresponding
parameters.
- RDP (connect to Microsoft Windows 2000 and older systems)
command is like "rdesktop -4 <hostname>"
- RDP v5 (connect to Microsoft Windows XP and newer systems)
command is like "rdesktop <hostname>"
There is no "-5" here because it is default for rdesktop(1)
- RDP v5 (Sun Ray version)
command is like "/opt/SUNWuttsc/bin/uttsc <hostname>"
- VNC (connect to systems sharing the desktop by using VNC)
command is like "vncviewer <hostname>"
- XDMCP (connect to servers running X)
command is like "Xephyr :1 -once -query <hostname>"
- ICA (connect to Citrix servers)
command is like "wfica -description <hostname>"
This proposal adds version 0.150, the latest stable release.
The tsclient program supports the following options:
Usage: tsclient [OPTION]... [FILE]...
FILE an rdp format file containing options
-h, --help display this help and exit
-v, --version output version information and exit
-x FILE launch rdesktop with options specified in FILE
/usr/lib/tsclient-applet is a GNOME panel applet, is aim to
launch saved profiles.
4.2. Bug/RFE Number(s):
None.
4.3. In Scope:
See above.
4.4. Out of Scope:
See above.
4.5. Interfaces:
Exported Interface
Interface Name Classification
Comment
------------------- ---------------
--------------
SUNWtsclient Uncommitted
Package name
/usr/bin/tsclient Volatile
tsclient GUI
/usr/lib/tsclient-applet Volatile
GNOME panel applet
/usr/share/applications/tsclient.desktop Volatile
UI spec
/usr/share/mime-info/tsclient.keys Volatile
mime info
/usr/share/mime-info/tsclient.mime Volatile
mime info
/usr/share/application-registry/tsclient.applications Volatile
mime type handler
/usr/lib/bonobo/servers/GNOME_TSClientApplet.server Volatile
bonobo server file
Imported Interface
Interface Classification ARC case Comment
-------- --------------- ----------
------------------
rdesktop Volatile LSARC 2008/083 rdp CLI
tool
vncviewer Volatile LSARC 2007/625 vnc CLI
client tool
Xephyr Volatile PSARC 2007/051 Xephyr
CLI tool
uttsc Committed IASWARC 2005/0024 SUN RDP
CLI tool
GNOME Libraries Committed LSARC 2005/734
4.6. Doc Impact:
New manpage, tsclient.1.
4.7. Admin/Config Impact:
This tool might be used by Administrators, who want to control their
machines with Remote Desktop enabled.
4.8. HA Impact:
None.
4.9. I18N/L10N Impact:
The JDS team and the G11N are working together to evaluate and
provide I18N/L10N support.
4.10. Packaging & Delivery:
Adds new package, SUNWtsclient, approx 458 KB.
Package will only go into SUNWCall and SUNWCXall clusters.
4.11. Security Impact:
tsclient is a wrapper tool for rdesktop, vncviewer, Xephyr and uttsc,
itself does not have any security issue.
4.12. Dependencies:
The following versions of the imported interfaces are required:
rdesktop
vncviewer
Xephyr
uttsc
They are optional dependencies, without them, tsclient can run, but
without releated feature.
5. Reference Documents:
[1] tsclient homepage:
http://sourceforge.net/projects/tsclient
[2] Related ARC Cases:
LSARC 2008/083: rdesktop
LSARC 2007/625: vncviewer
PSARC 2007/051: xorg server upgrade to 7.2
IASWARC 2005/0024: Sun RDP solution
LSARC 2005/734: GNOME For Nevada
