On Fri, 19 Jan 2007 09:53:23 -0600 Kirk Strauser wrote:
>> Why not? Group write is plenty enough for someone else to replace the
>> .ssh directory with another one, so sshd checks for that.
>
> To replace it with another 700 directory owned by the user, containing a 40=
> file also owned by the u
On Friday 19 January 2007 9:10 am, Ceri Davies wrote:
> Why not? Group write is plenty enough for someone else to replace the
> .ssh directory with another one, so sshd checks for that.
To replace it with another 700 directory owned by the user, containing a 400
file also owned by the user?
--
On Thu, Jan 18, 2007 at 05:00:56PM -0600, Kirk Strauser wrote:
> On Thursday 18 January 2007 16:44, Christian Baer wrote:
>
> > The problem was not the authorized_keys file itself, it was my home
> > directory.
>
> I don't think so. More likely, it was the .ssh directory itself.
Why not? Group
Kirk Strauser wrote:
>> The problem was not the authorized_keys file itself, it was my home
>> directory.
> I don't think so. More likely, it was the .ssh directory itself.
Nope. :-)
The only thing I changed was /usr/home/christian from mode 770 to mode 750.
Then it worked. I'm guessing it wa
On Thursday 18 January 2007 16:44, Christian Baer wrote:
> The problem was not the authorized_keys file itself, it was my home
> directory.
I don't think so. More likely, it was the .ssh directory itself.
--
Kirk Strauser
pgpXWYQbAuWpq.pgp
Description: PGP signature
On Thu, 18 Jan 2007 12:14:34 -0600 Noel Jones wrote:
> Did you copy the displayed "Public key for pasting into OpenSSH" from
> PuttyGEN, or did you paste the actual contents of the public key?
> Putty's on-disk format for public keys is not compatible with OpenSSH.
Yeah, I got that right. sshd wa
On Thu, 18 Jan 2007 11:50:52 -0600 Parker Anderson wrote:
> Have you verified the permissions of the authorized_keys file on the
> server? If you have permissions set too loose (e.g. unneeded
> read/write permission to groups/other users), sshd may be refusing to
> trust that file.
The directory
On 1/18/07, Christian Baer <[EMAIL PROTECTED]> wrote:
The whole thing should be pretty trivial: I created a key using PuTTY,
copied the public key to ~/.ssh/authorized_keys (everthing in one line),
chose the private key in PuTTY and tried to log in. All I got in
response was: "Server refused out
Hello Christian,
On 1/18/07, Christian Baer <[EMAIL PROTECTED]> wrote:
Hi peeps!
This may not seem to be a real FreeBSD-issue, but I've gotten this to
run on several other machines, just not my Sun running FreeBSD. To
clarify this: I haven't really tried this on any other FreeBSD system
recentl
Hi peeps!
This may not seem to be a real FreeBSD-issue, but I've gotten this to
run on several other machines, just not my Sun running FreeBSD. To
clarify this: I haven't really tried this on any other FreeBSD system
recently though. I'm probably just to thick to get it right, so go ahead
and insu
10 matches
Mail list logo
