From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Bates <abates@omeganetserv.com>
Subject: Re: SSH and the NONE option
Date: Thu, 14 Jul 2005 09:12:40 -0600
Message-ID: <1121353960.6146.1.camel@localhost>
References: <MAEBLGENFLMMCIMBCMPOOEJICKAA.la6gha@robenel.com>
 <Pine.LNX.4.44.0507121017130.16595-100000@srv01.compumont.com>
 <20050714075909.GB2932@linux-mips.org> <42D634B6.7050807@home.se>
 <e524c532050714075327e61990@mail.gmail.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-hams-owner@vger.kernel.org>
In-reply-to: <e524c532050714075327e61990@mail.gmail.com>
Sender: linux-hams-owner@vger.kernel.org
List-Id: <linux-hams.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Jim Bayer <kc9aop@gmail.com>
Cc: Per Crusefalk <perpetum@home.se>, Ralf Baechle DL5RB <ralf@linux-mips.org>, Bill Vodall <wa7nwp@jnos.org>, linux-hams@vger.kernel.org


> 
> So it seems we've come full circle.
> 
> Everything in Amature Radio is clear text, so any protocol for
> authentication has to be OK.  Your ID and password comes along in
> clear text and that's that.  I guess frequent password changes are the
> only answer to comfort with security.
> 
> Seems like ftp and rcp may be the best bet.
> 

If a two factor authentication scheme could be used, then that's the
ticket.... a challenge response authentication for example... more
elegant would be something using a hashed password based on a passcode
and revolving token.  Let's be creative, there are more ways then just
"ssh"

Andrew