PVM Toolkit for Windows

Total Page:16

File Type:pdf, Size:1020Kb

PVM Toolkit for Windows PVM Toolkit for Windows Jan Kwiatkowski1,2, Piotr Hojnor2 Cezary Janikow 2 Computer Science Department, 1 Math and Computer Science Department Wrocław University of Technology University of Missouri – St. Louis Wybrzeże Wyspiańskiego 27 8001 Natural Bridge Rd, 50-370 Wrocław, Poland St. Louis, MO 63121, USA phone: (+48)(71) 3203602 phone: (314)5166352 fax: (+48)(71) 3211018 fax: (314)5165400 e-mail: {kwiatkowski,hojnor}@ci.pwr.wroc.pl e-mail: [email protected] Abstract: In the past years, computing has been ronment, which emulates a distributed-memory moving from the sequential world to the parallel multiprocessor in a heterogeneous networked one, from centralized organization to decentral- environment. Reasons for the wide acceptance ized. This paper presents a short description of a and popularity of PVM for scientific computa- PVM (Parallel Virtual Machine) toolkit, devel- tions include availability of heterogeneous net- oped and implemented for the Windows operat- works and simple programming interfaces. Cur- ing system. It is intended to provide a graphical rently, PVM is available for a variety of hard- interface for PVM administration and process ware and software platforms, from personal monitoring. The toolkit will assist the user in the computers to supercomputers. Generally, PVM management of the virtual environment, and it consists of a daemon and PVM libraries, provid- can be used for PVM application tuning. The ing fundamental environment functionalities [5]. toolkit consists of a remote shell daemon Additionally, there are a number of auxiliary (RSHD), remote shell client (RSH), remote copy tools, such as graphical visualization of PVM client (RCP), and an administrative tool similar programs, administrative and other tools, which to XPVM, which serves administrative and extend the basic PVM functionally. Unfortu- monitoring functions. nately, such tools are not available for Windows. Therefore, a user must use a text console for all Keywords: distributed environments, PVM envi- PVM related functions. This text-based interface ronment, distributed processing, administrative is hard to use. Additionally, only two program- tools ming languages, Visual C++ and Visual Fortran, can be used for programming under PVM for 1 Introduction Windows. These are the main motivations for the work presented in this paper. The main objective In the past years, computing has been moving is to design and implement a PVM Toolkit for from the sequential world to the parallel one, Windows, to provide a graphical user interface from a centralized organization to decentralized. for PVM administration and process monitoring, There is also a large diversity of paral- and to support multiple languages. The toolkit lel/distributed computer organizations, including consists of a remote shell daemon (RSHD), re- those made possible by high-speed networks. mote shell client (RSH), remote copy client Thus, distributed parallel programming using (RCP), and an administrative tool similar to networked computers became one of the most XPVM, which serves administrative and moni- attractive and cheap ways to increase the com- toring functions [7]. This paper is organized as puting power [1,4]. In particular, the message- follow. Section 2 briefly describes the design. passing paradigm became very popular. PVM Section 3 presents basic functionalities of (Parallel Virtual Machine) is a software envi- RSHD, RSH and RPC. Section 4 presents the main functionalities of the administrative tool. the output window to display the incoming mes- Finally, section 5 summarizes this work and sages in the graphic mode. This allows very discusses future extensions planned. effective use of the PVM libraries in the graphical Windows environment - the libraries 2 Design overview do not have to be modified. void pvm_printf(char *fmt, ...) As mentioned, except for the classical PVM text { va_list va; console, there are no administrative tools sup- if (fmt) porting the PVM implementation for Windows { va_start(va, fmt); (WINPVM). Moreover, only two programming Vsprintf(commBuff, fmt, va); languages: Visual C++ and Visual Fortran, can Va_end(va); } /* if */ currently be used for programming under PVM for Windows. In this work, we extend the PVM #ifdef WINMAIN implementation for Windows [2,3]. First, we if (applHandle) provide a graphical monitoring console similar SendMessage(applHandle, to XPVM, to be used for environment manage- PRINTFMESSAGE, commBuff, 0); else #endif ment and to assist in tracing and tuning perform- printf("%s", commBuff); } ance of specific applications. Second, we provide additional useful tools, and extend the standard The above tools allow us to design and im- functionalities of other tools: plement the graphical console. Similarly to • A new RSHD server, allowing remote XPVM, to capture tracing information at run- process invocation to UNIX computers time, the user only needs to compile his program (feature not available in the standard using PVM libraries (some additional changes in PVM for Windows). the standard tracer were needed). Data captured during execution is immediately presenting (and • RSH shell, allowing adding new hosts to animated) by the new graphical console. All execute in PVM (there are some com- tracing information can be also stored in external mercial version, but very costly). files for later use such as for post-mortem analy- • RCP client, allowing distributing the ap- sis. Additionally, the user programs can be writ- plication code. ten in Borland C++ and Borland Delphi in addi- All pvm functions placed in the PVM libraries tion to Visual C++ and Fortran. communicate with the user utilizing the printf family of functions. It causes some problems 3 Remote Shell Daemon RSHD with programming under WINAPI. So, to allow easier interfacing in the graphical mode, a new RSHD daemon acts as a server for remote shell pvm_print function, presented below, is provided (RSH) and remote file copy (RCP). RSHD is a in the PVM libraries (module newcrt.c). service available on the UNIX operating system. This function checks if the invoked PVM li- Therefore, we need to provide RSHD for Win- brary function is to be used in the graphic mode. dows in order for PVM to communicate with If so, an internal Windows Message signals to UNIX. The new RSHD uses the same algorithm Fig.1. The main window of the Remote Shell Daemon as RSHD for UNIX BSD [6]. Additionally, it is used for defining the most commonly used equipped with a graphical user interface, which operations; the third, History, is used for allows changes to the execution environment storing the operations; and the last provides without having to restart it. The new daemon the command line. An operation is selected serves some useful functions such as: allowing by a click, and subsequently executed by the debugging, verifying the. .rhost file, checking Run button. secure connection conditions, manual and remote The graphical console of the RCP service can testing of Windows architecture (95/98, NT, work in two modes. First, when the architecture 2000), redirecting stdout and stderr, of the chosen host is recognized by the RSH choosing the localization of “temp files” service, the RCP main window is divided into ($TEMP or current directory). The RSHD two parts, one for the server and one for the re- graphical interface is presented in Figure 1. mote host (this allows text copying using the The main window consists of two parts. The drag and drop method). Second, if the architec- top of window is a menu with the following op- ture is not recognized, the RCP window provides tions: File|Close – close the application, the standard command line. Stop/Start - close or start the tracing process (the state of RSHD is stored to allow restarting from the last configuration), Settings – enable switch- 4 The PVM Graphical Console for ing on/off the above mentioned functionalities, Windows and Help - get the information about the avail- able options. The PVM graphical console assists the PVM The bottom of the main window is the central user in management of the virtual environment, widget where the results of the selected options and in monitoring the execution of the applica- are displayed. This display can be, at any time, tion. The main window of this console contains copied to the Windows clipboard. After three parts, as presented in Figure 2. The top part minimizing, the program is automatically saved is a toolbar containing iconic shortcuts for the as an icon tray. most often used user commands. The user can The RSH is a client for RSHD, it is used customize these. In the illustration, we have: for executing remote commands on a given Quit, Halt, RunRTSK and Help. Quit and Halt host. RSH services include a graphical con- are equivalent to quit and halt from the PVM sole, which is divided into four parts. The text console, RunRTSK starts the tools presented first part, Results, is used for showing the in the previous section, and Help presents infor- results of execution; the second, Aliases, is mation about the available options. The com- Fig.2. The main window of the administrative PVM console tool mands are selected with the mouse. text console, however, with improved interface. The middle part is the Page Control line con- The display widget is divided here into two taining Tabs Sheets for different visualizations of parts: the result panel, which presents the results the virtual machine. This simplifies management of the recently executed commands in a standard of the virtual machine because it allows the user way, and command line, where any pvm com- to concentrate on the most desired display fea- mand can be entered. The results displayed in the tures. The available Tab Sheets are: Commands, result panel are not lost but instead they are Tasks, Watch, Space-Time and Hosts. The de- buffered and can be viewed with the scrollbar. fault Tab Sheet is Commands. The remaining They can also be copied in the clipboard. The part of the main window is the central widget command line can be scrolled using the keyboard where the execution traces are displayed, as ac- arrow keys to retrieve command history.
Recommended publications
  • The Keys to Using SSH
    The Keys to Using SSH David Tomaschik RHCE, LPIC-1 System Administrator, Kennesaw State University MSCS Student, SPSU [email protected] http://systemoverlord.com Special ALE Central Edition! What is SSH? ● SSH = Secure Shell ● Originally intended as “Encrypted Telnet” ● Allows remote shell (command-line) access ● Connection Encrypted Using Public Key Cryptography ● SSH Version 1: Developed 1995, Now Insecure ● SSH Version 2: Standardized 2006 ● Only use SSH2! Why use SSH? ● Useful for remote system administration ● Transfer files securely ● Run remote applications ● Secure OTHER communications ● Requires Little Bandwidth ● Industry Standard SSH Clients ● Linux: OpenSSH; Usually Installed by Default ● OS X: OpenSSH; Installed by Default ● Windows: PuTTY, OpenSSH under Cygwin, Commercial SSH ● Android: ConnectBot + Others ● IOS: iSSH, Prompt, Others About the Presentation ● Assumes OpenSSH on Linux for both Client and Server ● Some features may require relatively recent versions of OpenSSH Basic Use ● ssh [email protected] Basic Use ● ssh [email protected] Verifying Who You're Connecting To ● The highlighted lines show you which host you are connecting to along with the key fingerprint. ● The key fingerprint is cryptographic proof that your connection is not being tampered with. ● Depending on your level of paranoia: ● Get the fingerprint from the system administrator ● Make your first connection from a 'trusted' network ● Just ignore it and hope its ok What You Can Do Now ● Run Commands Remotely ● Install packages/services ● Configure
    [Show full text]
  • Malware to Crimeware
    I have surveyed over a decade of advances in delivery of malware. Over this daVid dittRich period, attackers have shifted to using complex, multi-phase attacks based on malware to crimeware: subtle social engineering tactics, advanced how far have they cryptographic techniques to defeat takeover gone, and how do and analysis, and highly targeted attacks we catch up? that are intended to fly below the radar of current technical defenses. I will show how Dave Dittrich is an affiliate information malicious technology combined with social security researcher in the University of manipulation is used against us and con- Washington’s Applied Physics Laboratory. He focuses on advanced malware threats and clude that this understanding might even the ethical and legal framework for respond- ing to computer network attacks. help us design our own combination of [email protected] technical and social mechanisms to better protect us. And ye shall know the truth, and the truth shall make you free. The late 1990s saw the advent of distributed and John 8:32 coordinated computer network attack tools, which were primarily used for the electronic equivalent of fist fighting in the streets. It only took a few years for criminal activity—extortion, click fraud, denial of service for competitive advantage—to appear, followed by mass theft of personal and financial data through quieter, yet still widespread and auto- mated, keystroke logging. Despite what law-abid- ing citizens would desire, crime does pay, and pay well. Today, the financial gain from criminal enter- prise allows investment of large sums of money in developing tools and operational capabilities that are increasingly sophisticated and highly targeted.
    [Show full text]
  • Unix and Linux System Administration and Shell Programming
    Unix and Linux System Administration and Shell Programming Unix and Linux System Administration and Shell Programming version 56 of August 12, 2014 Copyright © 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2009, 2010, 2011, 2012, 2013, 2014 Milo This book includes material from the http://www.osdata.com/ website and the text book on computer programming. Distributed on the honor system. Print and read free for personal, non-profit, and/or educational purposes. If you like the book, you are encouraged to send a donation (U.S dollars) to Milo, PO Box 5237, Balboa Island, California, USA 92662. This is a work in progress. For the most up to date version, visit the website http://www.osdata.com/ and http://www.osdata.com/programming/shell/unixbook.pdf — Please add links from your website or Facebook page. Professors and Teachers: Feel free to take a copy of this PDF and make it available to your class (possibly through your academic website). This way everyone in your class will have the same copy (with the same page numbers) despite my continual updates. Please try to avoid posting it to the public internet (to avoid old copies confusing things) and take it down when the class ends. You can post the same or a newer version for each succeeding class. Please remove old copies after the class ends to prevent confusing the search engines. You can contact me with a specific version number and class end date and I will put it on my website. version 56 page 1 Unix and Linux System Administration and Shell Programming Unix and Linux Administration and Shell Programming chapter 0 This book looks at Unix (and Linux) shell programming and system administration.
    [Show full text]
  • Lab Work 03. Using Ssh/Rdp for Remote Linux/UNIX/Mac/Windows Servers
    LAB WORK 03. USING SSH/RDP FOR REMOTE LINUX/UNIX/MAC/WINDOWS SERVERS MANAGEMENT 1. PURPOSE OF WORK Get the initial skills of working with a remote host via ssh protocol. Secure SHell is the primary means of remotely managing networked computers running UNIX/Linux. The Linux/UNIX commands are used: ssh, scp, uname, passwd, date, who, pwd, mkdir, mc, exit, logout. 2. TASKS FOR WORK 2.1. Install Secure Shell Extension on your Chrome browser in the classroom or at home. Using the Secure Shell Extension, connect to the academy.lv remote server with your student account. Use the uname command (with the appropriate parameters) to determine the type of operating system, hardware platform, and version of the server core (make a Screenshot 1). 2.2. Download Putty.exe on your Windows computer in the classroom or at home. Using the putty.exe, connect to the academy.lv remote server with your student account. Use the passwd command for change Your password on academy.lv remote server. Use the date command (with the appropriate parameters) to determine the date and time of the remote server (make a Screenshot 2). 2.3. Start Your Linux Virtual Machine on VirtualBox on your Windows computer (show Lab Work 01). Start Linux Terminal. 2.4. Use the uname command (with the appropriate parameters) to determine the type of operating system, hardware platform, and version of the server core for local Linux (make a Screenshot 3). 2.5. Use the ssh command on Linux Virtual Machine (without loading the academy.lv remote server shell) to determine the date and time (date command with the appropriate parameters) for academy.lv remote server (make a Screenshot 4).
    [Show full text]
  • Mac OS X Server Introduction to Command-Line Administration Version 10.6 Snow Leopard Kkapple Inc
    Mac OS X Server Introduction to Command-Line Administration Version 10.6 Snow Leopard K Apple Inc. Apple Remote Desktop, Finder, and Snow Leopard are © 2009 Apple Inc. All rights reserved. trademarks of Apple Inc. Under the copyright laws, this manual may not AIX is a trademark of IBM Corp., registered in the U.S. be copied, in whole or in part, without the written and other countries, and is being used under license. consent of Apple. The Bluetooth® word mark and logos are registered The Apple logo is a trademark of Apple Inc., registered trademarks owned by Bluetooth SIG, Inc. and any use in the U.S. and other countries. Use of the “keyboard” of such marks by Apple is under license. Apple logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may This product includes software developed by the constitute trademark infringement and unfair University of California, Berkeley, FreeBSD, Inc., competition in violation of federal and state laws. The NetBSD Foundation, Inc., and their respective contributors. Every effort has been made to ensure that the information in this manual is accurate. Apple is not Java™ and all Java-based trademarks and logos responsible for printing or clerical errors. are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Apple 1 Infinite Loop PowerPC™ and the PowerPC logo™ are trademarks Cupertino, CA 95014 of International Business Machines Corporation, used 408-996-1010 under license therefrom. www.apple.com UNIX® is a registered trademark of The Open Group. Apple, the Apple logo, AppleScript, FireWire, Keychain, Other company and product names mentioned herein Leopard, Mac, Mac OS, Quartz, Safari, Xcode, Xgrid, and are trademarks of their respective companies.
    [Show full text]
  • Clustershell Documentation Release 1.8.2
    ClusterShell Documentation Release 1.8.2 Stephane Thiell Aug 15, 2019 Contents 1 Introduction 3 2 Release Notes 5 2.1 Version 1.8................................................5 2.1.1 Version 1.8.2..........................................5 2.1.2 Version 1.8.1..........................................6 2.1.3 Main changes in 1.8.......................................6 2.2 Version 1.7................................................8 2.2.1 Version 1.7.3..........................................9 2.2.2 Version 1.7.2..........................................9 2.2.3 Version 1.7.1..........................................9 2.2.4 Main changes in 1.7.......................................9 3 Installation 13 3.1 Requirements............................................... 13 3.2 Distribution................................................ 13 3.2.1 Fedora.............................................. 14 3.2.2 Red Hat Enterprise Linux (and CentOS)............................ 14 3.2.3 openSUSE............................................ 15 3.2.4 Debian.............................................. 16 3.2.5 Ubuntu............................................. 16 3.2.6 Installing ClusterShell using PIP................................ 16 3.3 Source.................................................. 17 4 Configuration 19 4.1 clush................................................... 19 4.2 Node groups............................................... 20 4.2.1 groups.conf........................................... 20 4.2.2 File-based group sources...................................
    [Show full text]
  • TR-4569: Security Hardening Guide for Netapp ONTAP 9
    Technical Report Security Hardening Guide for NetApp ONTAP 9 Guidelines for Secure Deployment of ONTAP 9 Product Security Team, NetApp December 2020 | TR-4569 Abstract This technical report provides guidance and configuration settings for NetApp® ONTAP® 9 to help organizations meet prescribed security objectives for information system confidentiality, integrity, and availability. TABLE OF CONTENTS Introduction ................................................................................................................................................. 4 ONTAP image validation ............................................................................................................................ 4 Upgrade image validation ........................................................................................................................................ 4 Boot-time image validation ...................................................................................................................................... 4 Local storage administrator accounts ...................................................................................................... 4 Roles, applications, and authentication ................................................................................................................... 4 Default administrative accounts ............................................................................................................................... 7 Certificate-based API access..................................................................................................................................
    [Show full text]
  • Putty User Manual
    PuTTY User Manual PuTTY is a free (MIT-licensed) Windows Telnet and SSH client. This manual documents PuTTY, and its companion utilities PSCP, PSFTP, Plink, Pageant and PuTTYgen. Note to Unix users: this manual currently primarily documents the Windows versions of the PuTTY utilities. Some options are therefore mentioned that are absent from the Unix version; the Unix version has features not described here; and the pterm and command-line puttygen utilities are not described at all. The only Unix-specific documentation that currently exists is the man pages. This manual is copyright 1997-2017 Simon Tatham. All rights reserved. You may distribute this documentation under the MIT licence. See appendix C for the licence text in full. Chapter 1: Introduction to PuTTY 1.1 What are SSH, Telnet and Rlogin? 1.2 How do SSH, Telnet and Rlogin differ? Chapter 2: Getting started with PuTTY 2.1 Starting a session 2.2 Verifying the host key (SSH only) 2.3 Logging in 2.4 After logging in 2.5 Logging out Chapter 3: Using PuTTY 3.1 During your session 3.2 Creating a log file of your session 3.3 Altering your character set configuration 3.4 Using X11 forwarding in SSH 3.5 Using port forwarding in SSH 3.6 Making raw TCP connections 3.7 Connecting to a local serial line 3.8 The PuTTY command line Chapter 4: Configuring PuTTY 4.1 The Session panel 4.2 The Logging panel 4.3 The Terminal panel 4.4 The Keyboard panel 4.5 The Bell panel 4.6 The Features panel 4.7 The Window panel 4.8 The Appearance panel 4.9 The Behaviour panel 4.10 The Translation panel 4.11
    [Show full text]
  • Local System Security Via SSHD Instrumentation
    Local System Security via SSHD Instrumentation Scott Campbell National Energy Research Scientific Computing Center, Lawrence Berkeley National Lab [email protected] ABSTRACT SSHD (iSSHD) and many other security tools and research In this paper we describe a method for near real-time projects is that iSSHD is not designed to detect and act on single identification of attack behavior and local security policy anomalous events (like unexpected command sequences), but violations taking place over SSH. A rational is provided for the rather to enforce local security policy on data provided by the placement of instrumentation points within SSHD based on the running SSHD instances. analysis of data flow within the OpenSSH application as well as our overall architectural design and design principles. Sample A key idea is that the generation of data is completely decoupled attack and performance analysis examples are also provided. from its analysis. The iSSHD instance generates data and the analyzer applies local policy to it. By using the Broccoli library Categories and Subject Descriptors [4], we convert the structured text data output by iSSHD into D.4.6 [Security and Protection]: Information Flow Controls – native bro events that are processed by the analyzer system [3]. Events, as their name implies, are single actions or decisions made General Terms by a user that are agnostic from a security analysis perspective. Measurement, Security. Bro processes these events in the same way as network traffic events, applying local security policy to interpret them as desired. Keywords SSH, keystroke logging, Bro IDS, Intrusion Detection, policy Local security policy can be thought of as sets of heuristics that enforcement.
    [Show full text]
  • Command-Line Administration for Version 10.5 Leopard
    Mac OS X Server Command-Line Administration For Version 10.5 Leopard Apple Inc. Apple, the Apple logo, AppleScript, Bonjour, iCal, © 2007 Apple Inc. All rights reserved. FireWire, iMac, iPod, iTunes, Keychain, Mac, the Mac logo, Macintosh, Mac OS, Power Mac, QuickTime, Xsan, The owner or authorized user of a valid copy of Xgrid, and Xserve are trademarks of Apple Inc., Mac OS X Server software may reproduce this registered in the U.S. and other countries. ARD, Finder, publication for the purpose of learning to use such Leopard, and Spotlight are trademarks of Apple Inc. software. No part of this publication may be reproduced Apple Store is a service mark of Apple Inc., registered in or transmitted for commercial purposes, such as selling the U.S. and other countries. copies of this publication or for providing paid-for support services. Adobe and PostScript are trademarks of Adobe Systems Incorporated. Every effort has been made to ensure that the information in this manual is accurate. Apple Inc. is not The Bluetooth® word mark and logos are registered responsible for printing or clerical errors. trademarks owned by Bluetooth SIG, Inc. and any use of such marks by Apple is under license. Apple 1 Infinite Loop Intel, Intel Core, and Xeon are trademarks of Intel Corp. Cupertino CA 95014-2084 in the U.S. and other countries. 408-996-1010 ™ ™ www.apple.com PowerPC and the PowerPC logo are trademarks of International Business Machines Corporation, used The Apple logo is a trademark of Apple Inc., registered under license therefrom. in the U.S.
    [Show full text]
  • Detection of Malicious Remote Shell Sessions
    2019 11th International Conference on Cyber Conflict Permission to make digital or hard copies of this publication for internal use within NATO and for personal or educational use when for non-profit or Silent Battle non-commercial purposes is granted providing that copies bear this notice T. Minárik, S.Alatalu, S.Biondi, and a full citation on the first page. Any other reproduction or transmission M.Signoretti, I.Tolga, G.Visky (Eds.) requires prior written permission by NATO CCD COE. 2019 © NATO CCD COE Publications, Tallinn Detection of Malicious Remote Shell Sessions Pierre Dumont Roland Meier Department of Information Technology Department of Information Technology and Electrical Engineering and Electrical Engineering ETH Zürich / Kudelski Security ETH Zürich Zürich / Lausanne, Switzerland Zürich, Switzerland [email protected] [email protected] David Gugelmann Vincent Lenders Exeon Analytics Science and Technology Zürich, Switzerland armasuisse [email protected] Thun, Switzerland [email protected] Abstract: Remote shell sessions via protocols such as SSH are essential for managing systems, deploying applications, and running experiments. However, combined with weak passwords or flaws in the authentication process, remote shell access becomes a major security risk, as it allows an attacker to run arbitrary commands in the name of an impersonated user or even a system administrator. For example, remote shells of weakly protected systems are often exploited in order to build large botnets, to send spam emails, or to launch distributed denial of service attacks. Also, malicious insiders in organizations often use shell sessions to access and transfer restricted data. In this work, we tackle the problem of detecting malicious shell sessions based on session logs, i.e., recorded sequences of commands that were executed over time.
    [Show full text]
  • Secure Remote Administration with SSH
    7 Secure Remote Administration With SSH 7.0 Introduction In this chapter and the next chapter we'll look at some of the ways Linux offers to remotely administer a server, or to remotely access your workstation. Linux gives users great flexibility and functionality. You may have command-line only or a full graphical desktop, just as though you were physically present at the remote machine. OpenSSH is the tool of choice for remote command-line administration. It's secure, and easy to set up and use. It's also good for running a remote graphical desktop, because you can tunnel X Windows securely over SSH. This works well over fast local links. However, it's less satisfactory over a dialup or Internet connection because you'll experience significant lag. Rdesktop is a simple Linux client for connecting to Windows Terminal Servers, and to the Windows XP Professional Remote Desktop. This is useful for some system administration tasks, and for accessing Windows applications from Linux. For dialup users who want a remote graphical desktop over dialup, FreeNX is just the ticket. It is designed to deliver good performance over slow links. Currently you can use it to access a Linux PC from Linux, Windows, MacOSX, and Solaris. VNC is the reigning champion of cross-platform remote graphical desktops. With VNC you may do all sorts of neat things: run several PCs from a single keyboard, mouse, and monitor, mix and match operating systems, and do remote technical support. In this chapter we'll look at how to use OpenSSH. The next chapter is devoted to Rdesktop, FreeNX, and VNC.
    [Show full text]