> On Wed, Mar 9, 2011 at 6:22 PM, Randy Bush <[email protected]> wrote:
  > >>> I'm personally a fan of keeping things simple .... what's the beef
  > >>> with tcp/22 here?
  > >> The set of source IPs needing access to tcp/22 for mgmt may not be the
  > >> same as the set of IPs needing access to tcp/22 for the rpki service
  > >
  > > the router is the originator of the ssh connection, so there is no guess
  > > as to the port the cache will use. =A0if you are a big fan of ip address
  > > based acls, it is the cache you will be protecting, not the router.
  > 
  > apologies I reversed the info/pkt flow. Ok, so ideally in a sane world
  > I can already scp/ssh from a router to another router (maintenance
  > requirements + code moves + config loads ... last-resort 'ohshit'
  > configs.) Adding a few cache ips where the only thing running on the
  > ip/port combo is this service seems ok to me.
  > 
  > Ideally cache box has 'service' ip and 'maintenance' ip... with
  > different security policies and 'better' service separation than I can
  > get today in the world of routers.
I wonder whether that's how ssh designers intended to support selection of
application service; or: what the commonly used / most appropriate way 
to select one of several application services with access over ssh are.
I never had to use a separate host IP address for using scp for target hosts
that I also have ssh shell sessions with  (and I certainly have used scp
from certain routers targetting my usual Unix ssh accounts).

I'm no ssh expert; is one around and willing to provide some clue, please?

I suspect that if there is no predefined/commonly used  mechanism in place
something as simple as

        prepend to the protocol as piped into the ssh transport
        "originators sends 'this-magic-token-invokes-the-RPKI-cache-server\n'"

could do the job.

  > I'm back to 'why complicate things?'
  > 
  > -Chris


Ruediger Volk
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to