[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Sun May 16 15:19:49 2004 -->
- <!--x-from-r13: wxvaarl ng ybpnyargfbyhgvbaf.pbz (Xnzrf B. Yvaarl WWW) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected]-weyr.local -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] sshd resource intensive?? -->
- <li><em>date</em>: Sun May 16 15:19:49 2004</li>
- <li><em>from</em>: jkinney at localnetsolutions.com (James P. Kinney III)</li>
- <li><em>in-reply-to</em>: <<a href="msg00671.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00663.html">[email protected]</a>> <[email protected]-weyr.local> <<a href="msg00671.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] sshd resource intensive??</li>
SSH can be a real system hog. Look at the encryption algorithms that are
available and manually select a low overhead/fast one. Blowfish is a
_much_ faster cipher than the default 3des. My understanding of the
process is that a fast block cipher is sufficient for data transfer that
is not critical (i.e. no password exchanges, sensitive data, etc) since
all the hard, sensitive stuff (login) takes place with key exchange.
If there is a need for transfer speed of a large file, encrypt it first,
then transfer the encrypted file using a fast cipher and decrypt on the
far end.
If the network is secured anyway, (i.e. home LAN) and if the openssh on
both ends has been compiled with the optional "-c none" support, you can
use the secure login process with unencrypted data transfer.
--
James P. Kinney III \Changing the mobile computing world/
CEO & Director of Engineering \ one Linux user /
Local Net Solutions,LLC \ at a time. /
770-493-8244 \.___________________________./
<a rel="nofollow" href="http://www.localnetsolutions.com">http://www.localnetsolutions.com</a>
GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00663" href="msg00663.html">[ale] sshd resource intensive??</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
<li><strong><a name="00666" href="msg00666.html">[ale] sshd resource intensive??</a></strong>
<ul><li><em>From:</em> dragon at atlantacon.org (Drag0n)</li></ul></li>
<li><strong><a name="00671" href="msg00671.html">[ale] sshd resource intensive??</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00671.html">[ale] sshd resource intensive??</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00673.html">[ale] sshd resource intensive??</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00671.html">[ale] sshd resource intensive??</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00673.html">[ale] sshd resource intensive??</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00672"><strong>Date</strong></a></li>
<li><a href="threads.html#00672"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>