From: "J. Lance Cotton" <joe@lightningflash.net>
To: Tim Neu <tim@tneu.visi.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: axspawn and security on the air
Date: Wed, 28 May 2003 10:19:23 -0500 [thread overview]
Message-ID: <3ED4D37B.20700@lightningflash.net> (raw)
In-Reply-To: <20030528151549.GB19391@leo.tneu.visi.com>
Tim Neu wrote:
> On Wed, May 28, 2003 at 10:09:43AM -0500, J. Lance Cotton wrote:
>
>>I just recalled using the s/key one-time-password system at school once, so
>>I will look into that. It seems to be a good solution: secure and
>>low-bandwidth.
>
>
> The only problem is that with a one-time authentication event, it could be fairly easy to hijack a control session in
> mid-stream. (however remote the possibility may be)
>
> One neat solution might be digitally signing each command that requires authentication - but that is out of my
> league!
Way out of my league too. Plus I think the bandwidth requirements for a
signature along with the command is sort of poor amateur practice on the
144.39 APRS frequency, unless I set up a second control radio/TNC on 440. Hmm.
> Good luck! 73s.
Thanks for the advice and help!
-Lance
--
J. Lance Cotton, KJ5O
http://map.findu.com/kj5o-14
joe@lightningflash.net
next prev parent reply other threads:[~2003-05-28 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 14:38 axspawn and security on the air J. Lance Cotton
2003-05-28 15:01 ` Tim Neu
2003-05-28 15:09 ` J. Lance Cotton
2003-05-28 15:15 ` Tim Neu
2003-05-28 15:19 ` J. Lance Cotton [this message]
2003-05-28 16:00 ` M Taylor
2003-05-28 16:01 ` Thomas Osterried
2003-05-28 22:24 ` Ken Koster
2003-05-28 22:49 ` Steve Fraser
2003-06-04 18:46 ` Again TNOS Marco iw7eas
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=3ED4D37B.20700@lightningflash.net \
--to=joe@lightningflash.net \
--cc=linux-hams@vger.kernel.org \
--cc=tim@tneu.visi.com \
/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