From owner-freebsd-security Tue Oct 12 14: 0:24 1999 Delivered-To: freebsd-security@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1833314C32; Tue, 12 Oct 1999 14:00:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id F2B8F1CD4C2; Tue, 12 Oct 1999 14:00:21 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Tue, 12 Oct 1999 14:00:21 -0700 (PDT) From: Kris Kennaway To: Michael Hallgren Cc: Donald Wilde , freebsd-security@freebsd.org Subject: Re: MD5 systems interacting with DES systems In-Reply-To: <015101bf14ed$c4b27e60$5b014b0a@asf.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 12 Oct 1999, Michael Hallgren wrote: > > I don't think this is correct. rlogin and friends do no encryption or > > password authentication themselves, and aren't linked against libcrypt at > > all. So there should be no difference whether or not you have DES > > installed. > > Berkeley r* authenticates over source address, if I'm not seriously > mistaken... Note I said password authentication ;-) > > As for encrypted transport, which it sounds like you were talking about, > > you want either ssh (if the license restrictions are applicable to you - > > or you could port the "last truly free" version which the openbsd guys > > have been cleaning up in their tree), > > Yes, nice. SSH's a VERY good replacement for r* 'and a host of other needs). The license terms can be a bitch, though :-( > Anyone been trying out FreeS/WAN ? Not sure why you'd bother - KAME is the future for FreeBSD. Kris ---- XOR for AES -- join the campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message