Re: [Freebsd-security] Re: Multi-User Security

From: Doug Barton (DougB_at_FreeBSD.org)
Date: 06/09/04

  • Next message: Peter Rosa: "Hacked or not ?"
    Date: Wed, 9 Jun 2004 05:03:02 -0700 (PDT)
    To: "Crist J. Clark" <cjc@FreeBSD.org>
    
    

    On Mon, 7 Jun 2004, Crist J. Clark wrote:

    > On Sun, Jun 06, 2004 at 11:38:55PM -0700, Doug Barton wrote:
    >> On Wed, 19 May 2004, Dan Rue wrote:
    >>
    >>> You obviously havn't tried to chroot scponly users.. _that's_ the tricky
    >>> part. Especially if you want it to scale up beyond a handful of users.
    >>> If i'm wrong - fill me in i'd love to hear how to do it.
    >>
    >> Have you considered using ~/.ssh/authorized_keys to restrict the account
    >> from tty access? This would allow you to do commands (like scp) without
    >> the risk of the user getting an actual shell.
    >
    > $ ssh host /bin/sh
    >
    > You don't need a tty to get an interactive shell.

    You can also enforce what commands the user can run to prevent this.
    Read sshd(8) for more information.

    Doug

    -- 
         This .signature sanitized for your protection
    _______________________________________________
    freebsd-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
    

  • Next message: Peter Rosa: "Hacked or not ?"

    Relevant Pages

    • Re: [Freebsd-security] Re: Multi-User Security
      ... Especially if you want it to scale up beyond a handful of users. ... > from tty access? ... This would allow you to do commands without ... You don't need a tty to get an interactive shell. ...
      (FreeBSD-Security)
    • Re: [SLE] SSH question
      ... > logins from still issuing other commands. ... An interactive shell, invoked with e.g. 'ssh user@host', is allowed. ... A non-interactive shell, invoked with e.g. 'ssh user@host ls', is not allowed. ... new group, make those users a member of that group, and put above code ...
      (SuSE)
    • Re: preserve history in the interactive python
      ... and I find it hard typing/pasting the commands ... from the previous interactive shell. ... I can preserve the history in the shell? ...
      (comp.lang.python)
    • Re: bash and trap problem with control-c
      ... $ bash script.sh ... or chmod +x script.sh and ... source runs the commands in the current interactive shell, ...
      (comp.os.linux.development.apps)
    • preserve history in the interactive python
      ... and I find it hard typing/pasting the commands from the previous interactive shell. ... is there anyway that I can preserve the history in the shell? ...
      (comp.lang.python)