head	1.6;
access;
symbols
	TIGRIS_1_1_0RC2:1.3
	TIGRIS_1_1_0RC1:1.3
	TIGRIS_1_1:1.3.0.4
	TIGRIS_1_0_8:1.3
	TIGRIS_1_0_8RC3:1.3
	TIGRIS_1_0_8RC2:1.3
	TIGRIS_1_0_8RC1:1.3
	TIGRIS_1_0_7:1.3
	TIGRIS_1_0_7RC3:1.3
	TIGRIS_1_0_7RC2:1.3
	TIGRIS_1_0_7RC1:1.3
	TIGRIS_1_0_6:1.3
	TIGRIS_1_0_6RC5:1.3
	TIGRIS_1_0_6RC4:1.3
	TIGRIS_1_0_6RC3:1.3
	TIGRIS_1_0_6RC2:1.3
	TIGRIS_1_0_6RC1:1.3
	TIGRIS_1_0_5:1.3
	TIGRIS_1_0_5RC6:1.3
	TIGRIS_1_0_5RC5:1.3
	TIGRIS_1_0_5RC4:1.3
	TIGRIS_1_0_5RC3:1.3
	TIGRIS_1_0_5RC2:1.3
	TIGRIS_1_0_5RC1:1.3
	TIGRIS_1_0_4:1.3
	TIGRIS_1_0_3:1.3
	TIGRIS_1_0_2:1.3
	TIGRIS_1_0_1:1.3
	TIGRIS_1_0:1.3.0.6
	TIGRIS_1_0_0:1.3
	TIGRIS_1_0_0_RC1:1.3.0.2;
locks; strict;
comment	@# @;


1.6
date	2001.08.23.23.50.46;	author susank;	state Exp;
branches;
next	1.5;

1.5
date	2001.06.21.07.07.40;	author jefflove;	state Exp;
branches;
next	1.4;

1.4
date	2001.06.11.03.14.33;	author jefflove;	state Exp;
branches;
next	1.3;

1.3
date	2001.03.13.06.26.04;	author lori;	state Exp;
branches
	1.3.4.1
	1.3.6.1;
next	1.2;

1.2
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.1;

1.1
date	2001.01.29.19.38.23;	author lori;	state Exp;
branches;
next	;

1.3.4.1
date	2001.08.23.23.50.15;	author susank;	state Exp;
branches;
next	;

1.3.6.1
date	2001.08.23.23.49.16;	author susank;	state Exp;
branches;
next	;


desc
@@


1.6
log
@corrected href-- needed prepended 'http://'

Issue number: 5492
Obtained from:
Submitted by:
Reviewed by:
@
text
@  <div class="docs" id="ddsshguideterminals">
   <h2>Using the Desktop Terminals</h2>

<div class="toc">
   <h3>SSH Guide: Index</h3>

   <ul>
    <li>
     <a href="ddSSHGuide.html">About this guide</a> 

     <ul>
      <li><a href="ddSSHGuide.html#aboutssh">About SSH</a></li>

      <li><a href="ddSSHGuide.html#furtherdocumentation">Further documentation</a></li>
     </ul>
    </li>

    <li><a href="ddSSHGuideConcepts.html">Concepts</a></li>

    <li><a href="ddSSHGuideTerminals.html">Choosing the desktop terminal</a></li>

    <li>
     <strong>You are here:</strong> Using the Desktop Terminal 

     <ul>
      <li><a href="#macs">Macintosh</a></li>

      <li><a href="#windows">Windows</a></li>

      <li><a href="#othersshclients">Other SSH clients</a></li>
     </ul>
    </li>

    <li><a href="ddSSHGuideCygwin.html">Tunneling using Cygwin: The Desktop Unix Emulator</a></li>

    <li><a href="ddSSHGuideterminating.html">Terminating the tunnel</a></li>
   </ul>
</div>

   <div class="courtesylinks">
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>

   <h3>Necessities</h3>

   <dl>
    <dt>Hostname</dt>

    <dd><code>thisdomain.com</code></dd>

    <dt>Local port:</dt>

    <dd><code>2401</code></dd>

    <dt>Remote port:</dt>

    <dd><code>2401</code></dd>

    <dt>Username:</dt>

    <dd><code>tunnel</code></dd>

    <dt>User password:</dt>

    <dd><code>tunnel</code></dd>
   </dl>

   <h3><a id="macs" name="macs">Macintosh</a></h3>

   <ul>
    <li><a href="http://www.macssh.com">MacSSH</a></li>

    <li><a href="http://www.lysator.liu.se/~jonasw/freeware/niftyssh/">NiftyTelnet SSH</a></li>
   </ul>

   <p>Both Mac clients offer intuitive interfaces; both also are well-documented. For that reason, this discussion of the Mac clients is very brief. However, for both clients, the important information is the same as for the Windows clients: the hostname and ports must be correctly specified.</p>

   <h3><a id="windows" name="windows">Windows</a></h3>

   <p>Two free clients for Windows provide SSH tunneling:</p>

   <ul>
    <li><a href="http://www.zip.com.au/~roca/ttssh.html">TTSSH</a>, an open-source add-on to Tera Term Pro</li>

    <li><a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a>, a free implementation of Telnet and SSH for Win32 platforms. It also provides an XTerm terminal emulator.</li>
   </ul>

   <p>As with the Mac clients, the important things to keep in mind are the hostname and the port numbers. For both terminals, the configuration process is straightforward. Because TTSH is an add-on to Tera Term, it means you have to go through that one extra step before SSH functionality is possible. [A fuller description of tunneling with TTSH is being drafted and will be posted when finished. For now, please see TTSH's <a href="http://www.zip.com.au/~roca/ttssh.html">website</a>.]</p>

   <p>PuTTY, on the other hand, does not allow you to easily configure the client to handle port forwarding. As a result, it is not recommended for tunneling.</p>

   <h3><a id="othersshclients" name="othersshclients">SecureCRT and F-Secure SSH</a></h3>

   <p>Both these clients are fairly easy to use and configure for SSH1 tunneling. The information you will need--doubtless familiar by now--is listed below.</p>

   <p>The following illustrates the procedure; we will use SecureCRT (version 3.1.2):</p>

   <ol>
    <li>Open a new session, specifying "SSH1" in the pull-down menu.</li>

    <li>For "Hostname," enter "<code>thisdomain.com</code>."</li>

    <li>Click on the "Advanced" button by "Hostname."</li>

    <li>Once in the Advanced section, click on the "Port Forwarding" tab.</li>

    <li>For "Local port," enter "<code>2401</code>."</li>

    <li>For "Remote port" enter "<code>2401</code>."</li>

    <li>For Username, enter "<code>tunnel</code>."</li>

    <li>For User password, enter "<code>tunnel</code>."</li>

    <li>For "Remote hostname," enter "<code>localhost</code>."</li>

    <li>Enter "Save" and "OK" to exit the dialog box.</li>

    <li>Back in the main connection page. . . .</li>

    <li>Leave the defaults for "Cipher" and "Authentication" as they are.</li>

    <li>Click on "Connect."</li>

    <li>The server should then prompt for your password. It is "<code>tunnel</code>."</li>

    <li>If this is your first time, the client will tell you that no "host key" for the server has been found and ask if you want to continue. Answer yes.</li>

    <li>You are now tunneling.</li>

    <li>The terminal screen does not show a prompt. That's how it should be. The tunnel has been established. You are now ready to begin using CVS securely.</li>
   </ol>

   <p>We discuss how to use the open-source desktop Unix emulator for Windows, Cygwin, in the section titled, <a href="ddSSHGuideCygwin.html">Tunneling using Cygwin</a>. Because Cygwin does emulate a Unix environment, complete with many Unix commands, those who are tunneling from a Unix-like environment (say, from a Linux machine), can refer to the discussion on Cygwin.</p>

   <div class="courtesylinks">
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.5
log
@html usage revision
@
text
@d71 1
a71 1
    <li><a href="www.macssh.com">MacSSH</a></li>
@


1.4
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 14
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>Using the Desktop Terminals</title>
<style type="text/css">
 dd.c3 {font-weight: bold}
 dt.c2 {font-weight: bold}
 li.c1 {list-style: none}
</style>
<style type="text/css">
 p.c1 {font-weight: bold}
</style>
 </head>
d4 2
a5 3
 <body>
  <div class="docs" id="docid">
<h2>Using the Desktop Terminals</h2>
d7 3
a9 1
  <p>SSH Guide: Index</p>
d11 2
a12 4
  <ul>
   <li>
    <dl>
     <dt><a href="ddSSHGuide.html">About this guide</a></dt>
d14 3
a16 3
     <dd><a href="ddSSHGuide.html#aboutssh">About SSH</a></dd>
    </dl>
   </li>
d18 1
a18 5
   <li>
    <dl>
     <dd><a href="ddSSHGuide.html#furtherdocumentation">Further documentation</a></dd>
    </dl>
   </li>
d20 1
a20 3
   <li>
    <dl>
     <dt><a href="ddSSHGuideConcepts.html">Concepts</a></dt>
d22 2
a23 1
     <dt><a href="ddSSHGuideTerminals.html">Choosing the desktop terminal</a></dt>
d25 2
a26 1
     <dt class="c2">You are here: Using the Desktop Terminal</dt>
d28 1
a28 1
     <dd class="c3"><a href="#macs">Macintosh</a></dd>
d30 3
a32 1
     <dd class="c3"><a href="#windows">Windows</a></dd>
d34 1
a34 1
     <dd class="c3"><a href="#othersshclients">Other SSH clients</a></dd>
d36 3
a38 1
     <dt><a href="ddSSHGuideCygwin.html">Tunneling using Cygwin: The Desktop Unix Emulator</a></dt>
d40 3
a42 5
     <dt><a href="ddSSHGuideterminating.html">Terminating the tunnel</a></dt>
    </dl>
   </li>
  </ul>
<div class="courtesylinks"><a href="/servlets/HelpTOC">Back to main Help index</a></div> 
d44 1
a44 1
  <h3>Necessities</h3>
d46 2
a47 8
  <blockquote>
  <p>
 <b>Hostname</b>: <code>thisdomain.com</code><br />
    <b>Local port:</b> <code>2401</code><br />
    <b>Remote port:</b> <code>2401</code><br />
    <b>Username</b>: <code>tunnel</code><br />
    <b>User password:</b> <code>tunnel</code>
</p>
d49 1
a49 1
  </blockquote>
d51 1
a51 1
  <h3><a id="macs" name="macs">Macintosh</a></h3>
d53 1
a53 2
  <ul>
   <li><a href="www.macssh.com">MacSSH</a></li>
d55 1
a55 2
   <li><a href="http://www.lysator.liu.se/~jonasw/freeware/niftyssh/">NiftyTelnet SSH</a></li>
  </ul>
d57 1
a57 1
  <p>Both Mac clients offer intuitive interfaces; both also are well-documented. For that reason, this discussion of the Mac clients is very brief. However, for both clients, the important information is the same as for the Windows clients: the hostname and ports must be correctly specified.</p>
d59 1
a59 1
  <h3><a id="windows" name="windows">Windows</a></h3>
d61 1
a61 1
  <p>Two free clients for Windows provide SSH tunneling:</p>
d63 1
a63 2
  <ul>
   <li><a href="http://www.zip.com.au/~roca/ttssh.html">TTSSH</a>, an open-source add-on to Tera Term Pro</li>
d65 2
a66 2
   <li><a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a>, a free implementation of Telnet and SSH for Win32 platforms. It also provides an XTerm terminal emulator.</li>
  </ul>
d68 1
a68 1
  <p>As with the Mac clients, the important things to keep in mind are the hostname and the port numbers. For both terminals, the configuration process is straightforward. Because TTSH is an add-on to Tera Term, it means you have to go through that one extra step before SSH functionality is possible. [A fuller description of tunneling with TTSH is being drafted and will be posted when finished. For now, please see TTSH's <a href="http://www.zip.com.au/~roca/ttssh.html">website</a>.]</p>
d70 2
a71 1
  <p>PuTTY, on the other hand, does not allow you to easily configure the client to handle port forwarding. As a result, it is not recommended for tunneling.</p>
d73 2
a74 1
  <h3><a id="othersshclients" name="othersshclients">SecureCRT and F-Secure SSH</a></h3>
d76 1
a76 1
  <p>Both these clients are fairly easy to use and configure for SSH1 tunneling. The information you will need--doubtless familiar by now--is listed below.</p>
d78 1
a78 1
  <p>The following illustrates the procedure; we will use SecureCRT (version 3.1.2):</p>
d80 1
a80 2
  <ol>
   <li>Open a new session, specifying "SSH1" in the pull-down menu.</li>
d82 2
a83 1
   <li>For "Hostname," enter "<code>thisdomain.com</code>."</li>
d85 2
a86 1
   <li>Click on the "Advanced" button by "Hostname."</li>
d88 1
a88 1
   <li>Once in the Advanced section, click on the "Port Forwarding" tab.</li>
d90 1
a90 1
   <li>For "Local port," enter "<code>2401</code>."</li>
d92 1
a92 1
   <li>For "Remote port" enter "<code>2401</code>."</li>
d94 1
a94 1
   <li>For Username, enter "<code>tunnel</code>."</li>
d96 1
a96 1
   <li>For User password, enter "<code>tunnel</code>."</li>
d98 2
a99 1
   <li>For "Remote hostname," enter "<code>localhost</code>."</li>
d101 1
a101 1
   <li>Enter "Save" and "OK" to exit the dialog box.</li>
d103 1
a103 1
   <li>Back in the main connection page. . . .</li>
d105 1
a105 1
   <li>Leave the defaults for "Cipher" and "Authentication" as they are.</li>
d107 1
a107 1
   <li>Click on "Connect."</li>
d109 1
a109 1
   <li>The server should then prompt for your password. It is "<code>tunnel</code>."</li>
d111 1
a111 1
   <li>If this is your first time, the client will tell you that no "host key" for the server has been found and ask if you want to continue. Answer yes.</li>
d113 1
a113 1
   <li>You are now tunneling.</li>
d115 1
a115 2
   <li>The terminal screen does not show a prompt. That's how it should be. The tunnel has been established. You are now ready to begin using CVS securely.</li>
  </ol>
d117 24
a140 5
  <p>We discuss how to use the open-source desktop Unix emulator for Windows, Cygwin, in the section titled, <a href="ddSSHGuideCygwin.html">Tunneling using Cygwin</a>. Because Cygwin does emulate a Unix environment, complete with many Unix commands, those who are tunneling from a Unix-like environment (say, from a Linux machine), can refer to the discussion on Cygwin.</p>
<div class="courtesylinks"><a href="/servlets/HelpTOC">Back to main Help index</a></div>
 </div>
</body>
</html>
@


1.3
log
@fixing links; conforming index and style with rest of help docs
@
text
@d1 2
d4 11
a14 1
<head>
d16 3
a18 1
<title>Using the Desktop Terminals</title>
d20 1
a20 6
</head>
<body>
<span class="PlainText">
<span class="Header">Using the Desktop Terminals</span> 
<p>
<span class="PlainText"><b>SSH Guide: Index</b>
d22 4
a25 3
<ul>
	<dl>
<dt><a href="ddSSHGuide.html">About this guide</a>
d27 3
a29 1
<dd><a href="ddSSHGuide.html#aboutssh">About SSH</a></li>
d31 5
a35 1
<dd><a href="ddSSHGuide.html#furtherdocumentation">Further documentation</a></li>
d37 3
a39 1
<dt><a href="ddSSHGuideConcepts.html">Concepts</a>
d41 1
a41 1
<dt><a href="ddSSHGuideTerminals.html">Choosing the desktop terminal</a>
d43 1
a43 5
<dt><b>You are here: Using the Desktop Terminal
	
	<dd><a href="#macs">Macintosh</a></dd>
	
	<dd><a href="#windows">Windows</a></dd>
d45 1
a45 1
	<dd><a href="#othersshclients">Other SSH clients</a></b>
d47 1
a47 2
	
<dt><a href="ddSSHGuideCygwin.html">Tunneling using Cygwin: The Desktop Unix Emulator</a>
d49 1
a49 1
<dt><a href="ddSSHGuideterminating.html">Terminating the tunnel</a>
d51 1
a51 3
	</dl>
</ul>
<a href="/servlets/HelpTOC">Back to main Help index</a>
d53 5
a57 2
<p>
<hr noshade size=1>
d59 1
a59 1
<span class="InputHeader">Necessities</span>
d61 8
a68 2
<blockquote>
<b>Hostname</b>: <span class="TypewriterPlain">thisdomain.com</span><br>
d70 1
a70 1
<b>Local port:</b> <span class="TypewriterPlain">2401</span><br>
d72 1
a72 1
<b>Remote port:</b> <span class="TypewriterPlain">2401</span><br>
d74 2
a75 1
<b>Username</b>: <span class="TypewriterPlain">tunnel</span><br>
d77 2
a78 3
<b>User password:</b> <span class="TypewriterPlain">tunnel</span>
</blockquote>
<p>
d80 1
a80 8
<hr noshade size=1>
<a name="macs"></a><span class="InputHeader">Macintosh</span>
<ul>
<li><a href="www.macssh.com">MacSSH</a> 
<li><a href="http://www.lysator.liu.se/~jonasw/freeware/niftyssh/">NiftyTelnet SSH</a></li>
</ul>
<p>Both Mac clients offer intuitive interfaces; both also are well-documented. For that reason, this discussion of the Mac clients is very brief. However, for both clients, the important information is the same as for the Windows clients:  the hostname and ports must be correctly specified. 
<p>
d82 1
a82 3
<hr noshade size=1>
<a name="windows"></a><span class="InputHeader">Windows</span>
<p>Two free clients for Windows provide SSH tunneling:
d84 1
a84 1
<ul>
d86 2
a87 1
<li><a href="http://www.zip.com.au/~roca/ttssh.html" target="_new">TTSSH</a>, an open-source add-on to Tera Term Pro
d89 2
a90 1
<li><a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/" target="_new">PuTTY</a>, a free implementation of Telnet and SSH for Win32 platforms. It also provides an XTerm terminal emulator. 
d92 1
a92 1
</ul>
d94 1
a94 8
<p>As with the Mac clients, the important things to keep in mind are
the hostname and the port numbers. For both terminals, the
configuration process is straightforward. Because TTSH is an add-on to
Tera Term, it means you have to go through that one extra step before
SSH functionality is possible. [A fuller description of tunneling with
TTSH is being drafted and will be posted when finished. For now,
please see TTSH's 
<a href="http://www.zip.com.au/~roca/ttssh.html" target="_new">website</a>.]
d96 1
a96 2
<p>PuTTY, on the other hand, does not allow you to easily configure the client to handle port forwarding. As a result, it is not recommended for tunneling.
<p>
d98 1
a98 2
<hr noshade size=1>
<a name="othersshclients"></a><span class="InputHeader">SecureCRT and F-Secure SSH</span>
d100 1
a100 1
<p>Both these clients are fairly easy to use and configure for SSH1 tunneling. The information you will need--doubtless familiar by now--is listed below.</p>
d102 2
d105 1
a105 2
<p>The following illustrates the procedure; we will use SecureCRT (version 3.1.2):
<ol>
d107 1
a107 1
<li>Open a new session, specifying "SSH1" in the pull-down menu.</li>
d109 1
a109 1
<li>For "Hostname," enter "<span class="TypewriterPlain">thisdomain.com</span>."</li>
d111 1
a111 1
<li>Click on the "Advanced" button by "Hostname."</li>
d113 1
a113 1
<li>Once in the Advanced section, click on the "Port Forwarding" tab.</li>
d115 1
a115 1
<li>For "Local port," enter "<span class="TypewriterPlain">2401</span>."</li>
d117 1
a117 1
<li>For "Remote port" enter "<span class="TypewriterPlain">2401</span>."</li>
d119 1
a119 1
<li>For Username, enter "<span class="TypewriterPlain">tunnel</span>."</li>
d121 1
a121 1
<li>For User password, enter "<span class="TypewriterPlain">tunnel</span>."
d123 1
a123 1
<li>For "Remote hostname," enter "<span class="TypewriterPlain">localhost</span>."</li>
d125 1
a125 1
<li>Enter "Save" and "OK" to exit the dialog box.</li>
d127 1
a127 1
<li>Back in the main connection page. . . .</li>
d129 1
a129 1
<li>Leave the defaults for "Cipher" and "Authentication" as they are.</li>
d131 1
a131 1
<li>Click on "Connect."</li>
d133 1
a133 1
<li>The server should then prompt for your password. It is "<span class="TypewriterPlain">tunnel</span>."</li>
d135 2
a136 1
<li>If this is your first time, the client will tell you that no "host key" for the server has been found and ask if you want to continue. Answer yes.</li>
d138 5
a142 3
<li>You are now tunneling.</li>

<li>The terminal screen does not show a prompt. That's how it should be. The tunnel has been established. You are now ready to begin using CVS securely.</li>
a143 1
</ol>
a144 8
<p>We discuss how to use the open-source desktop Unix emulator for Windows, Cygwin, in the section titled, <a href="ddSSHGuideCygwin.html">Tunneling using Cygwin</a>. Because Cygwin does emulate a Unix environment, complete with many Unix commands, those who are tunneling from a Unix-like environment (say, from a Linux machine), can refer to the discussion on Cygwin.
<p>

<hr noshade size=1>
<a href="/servlets/HelpTOC">Back to main Help index</a>
</span>
</body>
</html>
@


1.3.4.1
log
@corrected href-- needed prepended 'http://'

Issue Number: 5492
Obtained from:
Submitted by:
Reviewed by:
@
text
@d63 1
a63 1
<li><a href="http://www.macssh.com">MacSSH</a> 
@


1.3.6.1
log
@corrected href-- needed prepended 'http://'
Issue number:  5492
Obtained from:
Submitted by:
Reviewed by:
@
text
@d63 1
a63 1
<li><a href="http://www.macssh.com">MacSSH</a> 
@


1.2
log
@added <title> tags to all files
@
text
@d1 2
a2 2
<HTML>
<HEAD>
d4 1
a4 1
<TITLE>Using the Desktop Terminals</TITLE>
d6 2
a7 2
</HEAD>
<BODY>
d9 3
a11 3
<SPAN class="Header">Using the Desktop Terminals</SPAN> 

<span class="InputHeader">SSH Guide Index</span>
d14 2
d17 1
a17 3
<li><a href="ddSSHGuide.html#thisguide">About this Guide</a></li>

<li><a href="ddSSHGuide.html#aboutssh">About SSH</a></li>
d19 1
a19 1
<li><a href="ddSSHGuide.html#furtherdocumentation">Further Documentation</a></li>
d21 1
a21 1
<li><a href="ddSSHGuideConcepts.html">Concepts</a></li>
d23 1
a23 1
<li><a href="ddSSHGuideTerminals.html">Choosing the Desktop Terminal</a></li>
d25 5
a29 3
<li><b>You are here: Using the Desktop Terminal</b></li>

<ul>
d31 1
a31 1
<li><a href="ddSSHGuideUsingterminals.html#macs">Macintosh</a></li>
d33 2
a34 1
<li><a href="ddSSHGuideUsingterminals.html#windows">Windows</a></li>
d36 1
a36 1
</ul>
d38 1
a38 2
<li><a href="ddSSHGuideCygwin.html">Tunneling Using Cygwin: The Desktop Unix Emulator</a></li>
<li><a href="#Terminating.html">Terminating the Tunnel</a></li>
d40 1
d42 2
a43 5
<br><br>



<dl>
d45 1
a45 1
<dt><b>Necessities</b></dt><br><br>
d47 2
a48 1
<dd><b>Hostname</b>: <span class="TypewriterPlain">idendev.com</span><dd>
d50 1
a50 1
<dd><b>Local port:</b> <span class="TypewriterPlain">2401</span><dd>
d52 1
a52 1
<dd><b>Remote port:</b> <span class="TypewriterPlain">2401</span><dd>
d54 1
a54 1
<dd><b>Username</b>: <span class="TypewriterPlain">tunnel</span></li>
d56 3
a58 1
<dd><b>User password:</b> <span class="TypewriterPlain">tunnel</span></li>
d60 2
a61 4
</dl>
<br>

<a name="macs"></a><b>Macintosh</b>
d67 1
d69 2
a70 3

<a name="windows"></a><p><b>Windows</b>

d75 1
a75 1
<li><a href="http://www.zip.com.au/~roca/ttssh.html">TTSSH</a>, an open-source add-on to Tera Term Pro
d77 1
a77 1
<li><a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a>, a free implementation of Telnet and SSH for Win32 platforms. It also provides an XTerm terminal emulator. 
d88 1
a88 1
<a href="http://www.zip.com.au/~roca/ttssh.html">website</a>.]
d91 1
d93 2
a94 2

<p><b>SecureCRT and F-Secure SSH</b></p>
d104 1
a104 1
<li>For "Hostname," enter "<span class="TypewriterPlain">idendev.com</span>."</li>
d130 1
a130 1
<li>If this is your first time, the client will tell you that no "host key" for the server has been found and ask if you want to continue. You want to continue.</li>
d138 2
a139 6
<p>We discuss how to use the open-source desktop Unix emulator for Windows, Cygwin, in the section titled, "<a href="ddCygwin.html">Cygwin</a>." Because Cygwin does emulate a Unix environment, complete with many Unix commands, those who are tunneling from a Unix-like environment (say, from a Linux machine), can refer to the discussion on Cygwin.

<p> <a name="#Terminating"></a><span class="InputHeader">Terminating the Tunnel</span>

<p>The easiest way to terminate the tunnel is to <span class="TypewriterPlain">Ctrl-C (^C)</span> it out of existence. In both the Mac OS and Windows environment, you can also close the client window, thereby shutting the tunnel down.</p>

d141 5
a145 4
<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>
</BODY>
</HTML>
@


1.1
log
@new and revised help documentation for v1.0
@
text
@d1 7
d145 2
@

