<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: Different ciphers, MAC, compression for inbound and outbound .</TITLE>
<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=870215317-29102002><FONT face=Arial color=#0000ff size=2>Hi
Jason,</FONT></SPAN></DIV>
<DIV><SPAN class=870215317-29102002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=870215317-29102002><FONT face=Arial color=#0000ff size=2>This
is the only valid argument I have heard on this issue. But then again one
would assume that the server side data protected by that very password would be
considered just as protection-worthy. Otherwise, why would they ask for
password to begin with.</FONT></SPAN></DIV>
<DIV><SPAN class=870215317-29102002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=870215317-29102002><FONT face=Arial color=#0000ff size=2>Thanks
for your reply.</FONT></SPAN></DIV>
<DIV><FONT face="Courier New" size=2>------</FONT> <BR><FONT face="Courier New"
size=2>Behnam Behzadi</FONT> </DIV>
<P><FONT face="Courier New" size=2>408-878-6551</FONT> <BR><FONT
face="Courier New" size=2><A href="http://www.riverstonenet.com/"
target=_blank>http://www.riverstonenet.com</A></FONT> </P>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Lacoss-Arnold, Jason
[mailto:Jason.Lacoss-Arnold@agedwards.com]<BR><B>Sent:</B> Tuesday, October
29, 2002 5:02 AM<BR><B>To:</B> Behnam Behzadi<BR><B>Cc:</B>
openssh-unix-dev@mindrot.org; secureshell@securityfocus.com<BR><B>Subject:</B>
RE: Different ciphers, MAC, compression for inbound and outbound
.<BR><BR></FONT></DIV>
<P><FONT size=2>I could see an organization choosing to only encrypt client to
server communications if they only sensitive data they were concerned about is
passwords. This would lower resource utilization, esp. if the clients
usually consume data instead of send it.</FONT></P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Markus Friedl [<A
href="mailto:markus@openbsd.org">mailto:markus@openbsd.org</A>]</FONT>
<BR><FONT size=2>Sent: Tuesday, October 29, 2002 4:25 AM</FONT> <BR><FONT
size=2>To: Behnam Behzadi</FONT> <BR><FONT size=2>Cc: Damien Miller;
openssh-unix-dev@mindrot.org;</FONT> <BR><FONT
size=2>secureshell@securityfocus.com</FONT> <BR><FONT size=2>Subject: Re:
Different ciphers, MAC, compression for inbound and</FONT> <BR><FONT
size=2>outbound .</FONT> </P><BR>
<P><FONT size=2>On Mon, Oct 28, 2002 at 10:43:52AM -0800, Behnam Behzadi
wrote:</FONT> <BR><FONT size=2>> This question is not coming from actual
users. This was raised from the Marketing to Engineering to research the
possibilities if some future customer makes it a requirement.</FONT></P>
<P><FONT size=2>it's possible, it's simple to implement, but i don't see a
reason</FONT> <BR><FONT size=2>for this. it might be very confusing for
users.</FONT> <BR><FONT
size=2>_______________________________________________</FONT> <BR><FONT
size=2>openssh-unix-dev@mindrot.org mailing list</FONT> <BR><FONT size=2><A
href="http://www.mindrot.org/mailman/listinfo/openssh-unix-dev"
target=_blank>http://www.mindrot.org/mailman/listinfo/openssh-unix-dev</A></FONT>
</P><CODE><FONT
size=3><BR><BR>***********************************************************************************<BR>WARNING:
All e-mail sent to and from this address will be received or<BR>otherwise
recorded by the A.G. Edwards corporate e-mail system and is<BR>subject to
archival, monitoring or review by, and/or disclosure to,<BR>someone other than
the
recipient.<BR>************************************************************************************<BR></BLOCKQUOTE></FONT></CODE></BODY></HTML>