Date: Fri, 4 Aug 1995 22:39:29 +0400 (MSD) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" <ache@astral.msk.su> To: paul@freebsd.org, Paul Traina <pst@shockwave.com> Cc: CVS-commiters@freefall.cdrom.com, cvs-user@freefall.cdrom.com Subject: Re: cvs commit: src/secure/libexec/telnetd ext.h Message-ID: <vCXbc8myQ1@astral.msk.su> In-Reply-To: <199508041326.GAA02096@precipice.shockwave.com>; from Paul Traina at Fri, 04 Aug 1995 06:26:00 -0700 References: <199508041326.GAA02096@precipice.shockwave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199508041326.GAA02096@precipice.shockwave.com> Paul Traina
writes:
>A conservative interpretation of US crypto export laws would lead one to
>believe that not only can you not export the actual crypto code, you cannot
>export code that has CALLS to the crypto code.
Many current sources already violate this calling crypt() function f.e.
This statement isn't looks as true, calls isn't crypto materials, function
body can be simple replaced with non crypto code, as we already
do with crypt().
Remember, new telnet code on ftp is not restricted for export.
>The only difference between secure/*/*telnet* and */*telnet* is that
>the non-secure one has had all of the calls to anything that might
>remotely be considered encryption physically removed.
No, secure/telnetd looks better, it not have "eated login:" bug f.e.,
code is slightly better written too.
--
Andrey A. Chernov : And I rest so composedly, /Now, in my bed,
ache@astral.msk.su : That any beholder /Might fancy me dead -
FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead.
RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vCXbc8myQ1>