Home
last modified time | relevance | path

Searched refs:RFB (Results 1 – 16 of 16) sorted by relevance

/external/libvncserver/vncterm/
DREADME9 takes an existing desktop and exports it via RFB (VNC), just that
21 patch for screen to use VNConsole to export it's contents via RFB...
/external/libvncserver/
DAUTHORS23 This includes an implementation of RFB protocol version 3.7t.
DLibVNCServer.spec42 which serves the current X Window System desktop via RFB (VNC)
DLibVNCServer.spec.in42 which serves the current X Window System desktop via RFB (VNC)
DREADME9 VNC is a set of programs using the RFB (Remote Frame Buffer) protocol. They
293 connect to it via vncviewers. The communication uses a protocol named RFB
301 it understands is negotiated by the RFB protocol.
312 RFB protocol, but IT IS NOT SECURE. Anybody sniffing your net can get the
DNEWS60 * Fix for tight security type for RFB 3.8 in TightVNC file transfer
DChangeLog307 protocol (RFB version 3.8t), and thus it is fully cross-compatible
321 summary: 20 RFB captures, representing "common" 2D and 3D
443 server listen on IPv6, too. As done with the RFB sockets, this uses a separate-socket approach
1127 evaluate to false. There can not be more than 255 security types and MSLogon is RFB 3.6
1395 community version of the RFB protocol:
1397 mentioned in the official RFB protocol.
1794 security type for RFB 3.8 (debian bug 517422.)
4504 libvncserver/rfbserver.c: RFB 3.8 clients are well informed
4508 * libvncserver/auth.c: Better support for RFB >= 3.8 protocols
4512 * libvncserver/auth.c: All security types for RFB >= 3.7 *have* to
[all …]
/external/libvncserver/webclients/novnc/include/
Dui.js59 UI.rfb = RFB({'target': $D('noVNC_canvas'),
Drfb.js16 function RFB(defaults) { class
/external/libvncserver/x11vnc/misc/enhanced_tightvnc_viewer/src/patches/
Dtight-vncviewer-full.patch1948 + " -rfbversion str Set the advertised RFB version. E.g.: -rfbversion 3.6\n"
1956 + " RFB data sent so as to work with the UltraVNC Server. For\n"
1957 + " some reason, each RFB msg type must be sent twice under DSM.\n"
5390 the actual desktop area. Make sure we don't pass it on to the RFB
5920 * SendRFBEvent is an action which sends an RFB event. It can be used in two
5921 * ways. Without any parameters it simply sends an RFB event corresponding to
10899 * rfbproto.c - functions to deal with client side of RFB protocol.
11338 - fprintf(stderr, "Connected to RFB server, using protocol version %d.%d\n",
11455 + fprintf(stderr,"Setting RFB version to %d.%d from -rfbversion.\n\n", viewer_major, viewer_minor);
11460 + fprintf(stderr,"Setting RFB version to %d.%d from SSVNC_RFB_VERSION.\n\n", viewer_major, viewer_…
[all …]
/external/libvncserver/webclients/java-applet/ssl/
Dultravnc-102-JavaViewer-ssl-etc.patch1718 // Constructor. Make TCP connection to RFB server.
5249 System.out.println("RFB server supports protocol version " +
5262 - System.out.println("RFB server supports protocol version " +
5267 + System.out.println("RFB server supports protocol version: " +
Dtightvnc-1.3dev7_javasrc-vncviewer-ssl.patch77 - " is not an RFB server");
78 + " is not an RFB server: " + b);
/external/libvncserver/x11vnc/
DREADME108 framebuffer (RFB) protocol.
1028 for RFB version 3.8.
3541 env | grep ^RFB | sort 1>&2
3574 env | grep ^RFB | sort 1>&2
4271 see the string "RFB 003.008" that came from x11vnc. Pointing a web
8481 As of Jan/2004 x11vnc supports the "CutText" part of the RFB (aka VNC)
8501 viewers. Note that since the RFB protocol only has a single "CutText"
8560 options (UltraVNC incorrectly uses the RFB protocol version to
8563 two options. Note that running as RFB version 3.6 may confuse other
8599 "-permitfiletransfer". UltraVNC evidently treats any other RFB version
[all …]
DRELEASE-NOTES242 works for RFB version 3.8.
/external/libvncserver/x11vnc/misc/enhanced_tightvnc_viewer/bin/util/
Dssvnc.tcl5674 if [regexp -- {RFB 00} $line] {
14671 RFB Version:
14673 Set the numerical version of RFB (VNC) protocol to pretend to
14770 SSVNC_SKIP_RFB_PROTOCOL_VERSION (force viewer to be RFB 3.8)
14773 SSVNC_DEBUG_RECTS (printout debug for RFB rectangles.)
14804 DEBUG_RFB_SMSG (RFB server message debug.)
15241 the UltraVNC DSM plugin also modifies the RFB protocol(!), and so the SSVNC
/external/svox/pico_resources/tools/LingwareBuilding/PicoLingware_source_files/pkb/es-ES/
Des-ES_zl0_kpdf_mgc.pkb3509 …*���ϳ�]�M����ꅌ�,<�< ��(�[�~��[����1�@bf$cR!c��#E��qv�[�2QaW2s)(H�L\�N#@RFB��Y�)�+�FAOL���…