[PATCH] ssh-copy-id should do chmod go-w

mouring at etoh.eviladmin.org mouring at etoh.eviladmin.org
Thu Oct 4 04:19:46 EST 2001


You know.. thinking about this.. I really hate the idea of
any script mucking around with my ~/  permissions.  That is seriously
asking for trouble.

chmod 700 .ssh; chmod 600 .ssh/authorized_keys

makes more sense.  Changing ~/ permissions is a local policy issue, and I
know I get peaved when something changes my policy without asking.

- Ben

On Wed, 3 Oct 2001, Matthew Vernon wrote:

> mouring at etoh.eviladmin.org writes:
>  >
>  > Technically should it not be 'chmod 600'  just to ensure we have
>  > all permissions right.
>
> OK. This version does that.
>
> Matthew
>
> --- contrib/ssh-copy-id.orig	Thu Sep 27 21:47:44 2001
> +++ contrib/ssh-copy-id	Thu Sep 27 21:47:52 2001
> @@ -33,7 +33,7 @@
>    exit 1
>  fi
>
> -{ eval "$GET_ID" ; } | ssh $1 "test -d .ssh || mkdir .ssh ; cat >> .ssh/authorized_keys ; chmod g-w . .ssh .ssh/authorized_keys"
> +{ eval "$GET_ID" ; } | ssh $1 "test -d .ssh || mkdir .ssh ; cat >> .ssh/authorized_keys ; chmod 600 . .ssh .ssh/authorized_keys"
>
>  cat <<EOF
>  Now try logging into the machine, with "ssh '$1'", and check in:
>
>
> --
> Rapun.sel - outermost outpost of the Pick Empire
> http://www.pick.ucam.org
>




More information about the openssh-unix-dev mailing list