Re: axspawn and security on the air

From: Ken Koster (terhi.victor@logonet.com)
Date: Thu May 29 2003 - 01:24:47 EEST

  • Next message: Steve Fraser: "Re: axspawn and security on the air"

    In a previous message, KJ5O says

    >I am working on setting up an digi-ned based APRS digipeater and I want to
    >have ax25d listen for a very restricted set of connections for remote
    >administering of the digipeater.
    >
    >I plan on restricting connections to local-only (no digi-hops) connections
    >from authorized admin callsigns. Based on what I read in the AX.25 HOWTO, I
    >should use an axspawn command to open up a shell once the connection is made.

    >The background to my question is this: If I leave the password for an admin
    >user blank, some rogue user could easily change their TNC to use an admin
    >callsign and wreak havoc. If I require a password for user login, the password
    >is transmitted plaintext, right? Same situation as before.

    Why bother with axspawn at all? Since you're making direct connections
    just use SSH, it's not unusable at 1200b, maybe a bit slow but I do it all
    the time.

    >
    >This machine will hopefully, eventually be connected to the Internet, where
    >ssh connections are more bandwidth-appropriate, but I want to have the ability
    >to remote administer this computer over the air with minimal possibility for
    >abuse.

    I remote administer five of our local machines with SSH, some at 1200b, some
    at 9600b and several hops away. VI is even usable at 9600, tolerable
    at 1200 :-)

    Ken, N7IPB
    -
    To unsubscribe from this list: send the line "unsubscribe linux-hams" in
    the body of a message to terhi.victor@logonet.com
    More majordomo info at http://vger.kernel.org/majordomo-info.html

    This archive was generated by hypermail 2b30 : Thu May 29 2003 - 01:21:20 EEST