-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That's exactly what I was looking for!
Thanks for the patch.
Trevor
On 09/05/2011 09:56 PM, Kelsey Hightower wrote:
> Right now the way the patch works is that root will create the file
> and chown it to what ever user is specified when using the
>
Right now the way the patch works is that root will create the file
and chown it to what ever user is specified when using the
ssh_authorized_key type. If you want the key to be owned by root, just
specify root as the user.
--
You received this message because you are subscribed to the Google Gro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isn't it wonderful when you sound like a complete idiot on a public forum?
So, lesson #1 is to not post before the morning caffeine.
That said, I just re-tested this on Fedora 15 and SSH doesn't care if the
authorized_keys file is owned by the user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ssh_authorized_keys can be owned by anyone.
Think of how git works. The file is owned by git/gitosis/whatever, but you log
in as yourself. This is the whole point of ssh_authorized_keys and one
way that it can be abused.
In my tests, SSH doesn't car
One use case where it may not be desirable to have users own the keys
is in centralized ssh key setups backed by LDAP and PAM
authentication. In this specific case all keys are stored in a central
location such as /etc/ssh-public-keys/*.pub. The keys are only read by
PAM (root) during the authentic
> I have not taken the time to look, in detail, at this yet, but we
> should consider at least the greater scope of changes that were made
> in that commit before we absorb this.
>
> Daniel
Yeah, I should have searched the repo for previous commits, good
catch.
--
You received this message becau
