From: Andrew Bates <abates@omeganetserv.com>
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
Subject: Re: SSH and the NONE option
Date: Thu, 14 Jul 2005 09:12:40 -0600 [thread overview]
Message-ID: <1121353960.6146.1.camel@localhost> (raw)
In-Reply-To: <e524c532050714075327e61990@mail.gmail.com>
>
> 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
next prev parent reply other threads:[~2005-07-14 15:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 8:21 [PATCH] First cut of PR430 / extended 6pack driver Ralf Baechle DL5RB
2005-07-11 21:59 ` YAPP File Transfer with Linux Bill Vodall WA7NWP
2005-07-11 22:06 ` Curt, WE7U
2005-07-11 22:12 ` Curt, WE7U
2005-07-12 11:42 ` Rodolfo Brasnarof
2005-07-12 14:13 ` Bill Vodall
2005-07-12 14:21 ` Digi-ned output file and logrotate Bill Vodall
2005-07-12 15:24 ` Jim Bayer
2005-07-12 14:56 ` YAPP File Transfer with Linux Bob Nielsen
2005-07-12 14:55 ` Bill Vodall
2005-07-12 15:28 ` Bob Nielsen
2005-07-12 17:05 ` Bill Vodall
2005-07-12 18:07 ` Robert Eliassen
2005-07-12 18:51 ` Jeremy Utley
2005-07-12 19:11 ` Bill Vodall WA7NWP
2005-07-13 7:53 ` Robert Eliassen
2005-07-13 11:03 ` Tomi Manninen
2005-07-13 14:41 ` Chuck Hast
2005-07-13 17:51 ` Dave Platt
2005-07-14 0:19 ` Bob Nielsen
2005-07-12 20:51 ` Michael Taylor
2005-07-12 22:03 ` Bill - WA7NWP
2005-07-12 23:56 ` Chuck Hast
2005-07-12 15:13 ` Robert Eliassen
2005-07-12 15:22 ` SSH and the NONE option Bill Vodall
2005-07-12 16:55 ` Ralf Baechle DL5RB
2005-07-12 17:02 ` Bill Vodall
2005-07-12 18:04 ` Jonathan Lassoff
2005-07-12 19:08 ` Bill Vodall WA7NWP
2005-07-12 20:00 ` Jim Bayer
2005-07-12 20:43 ` Michael Taylor
2005-07-12 20:41 ` Michael Taylor
2005-07-12 21:57 ` Bill - WA7NWP
2005-07-12 22:19 ` Dennis Boone
2005-07-14 7:59 ` Ralf Baechle DL5RB
2005-07-14 9:47 ` Per Crusefalk
2005-07-14 14:53 ` Jim Bayer
2005-07-14 15:12 ` Andrew Bates [this message]
2005-07-14 17:01 ` Dave Platt
2005-07-14 15:27 ` Bob Snyder
2005-07-14 16:28 ` Jonathan Lassoff
2005-07-14 19:02 ` Bob Snyder
2005-07-14 19:28 ` Curt, WE7U
2005-07-14 20:43 ` Bob Snyder
2005-07-30 1:31 ` SSH and the NONE option - more Bill - WA7NWP
2005-07-30 8:19 ` Robert Snyder
2005-08-01 11:34 ` Ralf Baechle DL5RB
2005-08-02 13:20 ` Bill Vodall
2005-07-14 19:51 ` SSH and the NONE option Andrew Bates
2005-07-14 16:01 ` Ralf Baechle DL5RB
2005-07-16 9:28 ` Arno Verhoeven - PE1ICQ
2005-07-13 12:39 ` YAPP File Transfer with Linux Rodolfo Brasnarof
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1121353960.6146.1.camel@localhost \
--to=abates@omeganetserv.com \
--cc=kc9aop@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=perpetum@home.se \
--cc=ralf@linux-mips.org \
--cc=wa7nwp@jnos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox