]> &Brad.Hards; &Brad.Hards.mail; 2003 &Brad.Hards; &FDLNotice; 2016-07-25 5.0 (Applications 16.08) &krfb; is a server application that allows you to share your current session with a user on another machine, who can use a VNC client to view or even control the desktop. KDE kdenetwork krfb VNC RFB krdc Desktop Sharing Remote Control Remote Assistance Remote Desktop &krfb; is a server application that allows you to share your current session with a user on another machine, who can use a VNC client to view or even control the desktop. You would typically use &krfb; with the &kde; VNC client, which is &krdc;, since it closely matches the special features of &krfb;. &krfb; doesn't require you to start a new X session - it can share the current session. This makes it very useful when you want someone to help you perform a task. Please report any problems or feature requests to the &kde; mailing lists or file a bug at https://bugs.kde.org. This chapter provides a brief description of the Remote Frame Buffer protocol used by &krfb; and by other compatible systems. If you are already familiar with Remote Frame Buffer, you can safely skip this chapter. The high level implementation of a system using the Remote Frame Buffer protocol is known as Virtual Network Computer, or more often just as VNC. Remote Frame Buffer (or RFB for short) is a simple protocol for remote access to graphical user interfaces. It works at the frame-buffer level, which roughly corresponds to the rendered screen image, which means that it can be applied to all windowing systems (including X11, &MacOS; and &Microsoft; &Windows;). Remote Frame Buffer applications exist for many platforms, and can often be freely re-distributed. In the Remote Frame Buffer protocol, the application that runs on the machine where the user sits (containing the display, keyboard and pointer) is called the client. The application that runs on the machine where the framebuffer is located (which is running the windowing system and applications that the user is remotely controlling) is called the server. &krfb; is the &kde; server for the Remote Frame Buffer protocol. &krdc; is the &kde; client for the Remote Frame Buffer protocol. It takes a reasonable amount of network traffic to send an image of the framebuffer, so Remote Frame Buffer works best over high bandwidth links, such as a local area network. It is still possible to use &krfb; over other links, but performance is unlikely to be as good. It is very easy to use &krfb; - it has a simple interface, as shown in the screenshot below. Here's a screenshot of &krfb; &krfb; main window When you want to allow someone to access your desktop, you have to enable the checkbox Enable Desktop Sharing, which will start the server. The Address contains the address of your computer and the port number, separated by a colon. The address is just a hint - you can use any address that can reach your computer. &krfb; tries to guess your address from your network configuration, but does not always succeed in doing so. If your computer is behind a firewall it may have a different address or be unreachable for other computers. You can change the port on the Network page in the configuration dialog. The next field is prefilled with an automatically generated password. Click in the icon at the right of the field to change the password. Any remote user with the desktop sharing password will have to be authenticated. If unattended access is activated, and the remote user provides the password for unattended mode, desktop sharing access will be granted without explicit confirmation. By default the password for this mode is empty, to change that click on the button and enter a password. If unattended access is allowed, then you should probably specify a password. If the machine is a server and you are using &krfb; for remote administration, you probably want to use unattended access. &krfb; has no invitation feature any more as in previous versions. So you have to transfer the login information yourself using email or a personal invitation. If you cannot encrypt the email (or otherwise secure the link), sending a password by email is a very serious security risk, since anyone can read the password and address from the email as it passes over the network. This means that they can potentially take control of your machine. If you cannot encrypt the email message, it may be better to use a personal invitation, telephone the person you are giving access to, verify the identity of that person, and provide the required information that way. &krfb; uses the normal RFB password system, which does not transfer your password in the clear across the network. Instead, it uses a challenge-response system. This is reasonably secure, as long as the password is securely guarded. If you close the &krfb; main window by clicking on the window close icon or using the shortcut &Alt;F4 the server keeps running, which is indicated by an icon in the system tray. To stop &krfb; either use FileQuit in the main window or right click on the icon in the system tray and select Quit. In addition to the main &krfb; interface shown and described above, you can also control &krfb; using the Configure... on the &krfb; main window. The &krfb; configuration has two pages, as shown in the screenshot below: The Network page allows control over the port that &krfb; uses, as shown below. &krfb; Configuration (Network page) &krfb; Configuration (Network page) The Announce service on the local network checkbox controls whether &krfb; announces the service over the local network using Service Location Protocol. This is normally a good idea, but only works really well with a Service Location Protocol aware client, such as &krdc;. If you select the Use default port checkbox, then &krfb; will locate a suitable port. If you deselect this checkbox, you can specify a particular port. Specifying a particular port may be useful if you are using port-forwarding on the firewall. Note that if Service Location Protocol is turned on, this will automatically deal with identifying the correct port. The Security page allows you to configure whether the person connecting to the &krfb; server can control the desktop, or only view. &krfb; Configuration (Security page) &krfb; Configuration (Security page) When someone connects to &krfb; on your machine, you will get a pop-up notification that looks like the following screenshot, unless you are accepting unattended access without confirmation. &krfb; Connection Window &krfb; Connection Window If you Accept Connection, the client can proceed to authenticate, which requires the correct password for a login. If you Refuse Connection, then the attempt to connect will be terminated. The Allow remote user to control keyboard and mouse check box determines whether this client can only observe, or can take control of your machine. &krfb; Program copyright 2002 Tim Jansen tim@tjansen.de Contributors: Ian Reinhart Geiser geiseri@kde.org Documentation Copyright © 2003 &Brad.Hards; &Brad.Hards.mail; &underFDL; &underGPL; &documentation.index;