From: "Régis Décamps" <regis@decamps.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: ssh access in vhost account
Date: Sun, 15 Oct 2006 17:34:41 +0200 [thread overview]
Message-ID: <42c4f5b20610150834t63a04a66h53d222218423e195@mail.gmail.com> (raw)
In-Reply-To: <200610142040.36021.michaelkintzios@gmail.com>
On 10/14/06, Mick <michaelkintzios@gmail.com> wrote:
> Thanks,
>
> On Saturday 14 October 2006 19:27, Harm Geerts wrote:
> > On Saturday 14 October 2006 19:45, Mick wrote:
> > > I have a vhost account with an ISP and he's given me ssh access - which
> > > is nice. However, his /etc/sshd_config is set to allow passwd
> > > authentication rather than public key and there's no
> > > ~/.ssh/authorised_keys dir/file in my home.
> >
> > How does that matter?
> > You should be able to create that yourself.
>
> Hmm, I can't! This is a FreeBSD server and it's rather locked down with
> respect to normal user access rights.
>
> > ssh doesn't care about vhost
> >
[...]
> So, all I
> need to ask them to do is uncomment #Match User and add my user name and
> options? Like so:
> =================================
> Match User mick
> PubkeyAuthentication yes
> AuthorizedKeysFile ~/.ssh/authorized_keys
> PasswordAuthentication no
> =================================
>
> Is that correct?
Correct, provided you have sufficient permissions to create this file
(or at modify it) on the server, which apparently is not the case yet
--
Régis
http://regis.decamps.info/blog/
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-10-15 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 17:45 [gentoo-user] ssh access in vhost account Mick
2006-10-14 18:27 ` [gentoo-user] " Harm Geerts
2006-10-14 19:40 ` Mick
2006-10-14 20:10 ` Harm Geerts
2006-10-15 15:34 ` Régis Décamps [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42c4f5b20610150834t63a04a66h53d222218423e195@mail.gmail.com \
--to=regis@decamps.info \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox