axspawn and security on the air

From: J. Lance Cotton (lqlh.zbomrx@mailit.tunk.net)
Date: Wed May 28 2003 - 17:38:18 EEST

  • Next message: Tim Neu: "Re: axspawn and security on the air"

    Hi,

    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.

    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.

    Is insecurity of this type just a given with regard to wireless amateur
    connections?

    -Lance 

    -- 
J. Lance Cotton, KJ5O
http://map.findu.com/kj5o-14
htexhat.chrzokqx@gotanet.se

    -
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to qhboa@fibretech.net
More majordomo info at  http://vger.kernel.org/majordomo-info.html

    This archive was generated by hypermail 2b30 : Wed May 28 2003 - 17:38:34 EEST