On Fri, Oct 08, 2010 at 10:05:50AM +0200, Andrea Conti wrote:
> Now, the remote sshd is never sent any information about what is
> connected to the local end of the pipe (which is not even known to
> ssh!), so there is no way to alter its behavior depending on that.
>
> IOW, nothing in the setup y
On Thu, 7 Oct 2010 15:38:24 -0700 (PDT), BRM wrote:
> > I think for ssh to work the user needs a valid shell, not nologin, so
> > you can't do both of those suggestions.]
>
> Wouldn't a shell-less account per just provide the ability to use
> SFTP/SCP? Those don't require a shell to operate.
On 08/10/2010 0:28, Willie Wong wrote:
>> You can't do that on a per-command basis. You'd be trying to control the
>> authentication method accepted by sshd on B according to which command
>> is run on A -- something sshd on B knows nothing about.
>>
>
> That's partially false. See my response in
- Original Message
> From: "cov...@ccs.covici.com"
> To: gentoo-user@lists.gentoo.org
> Sent: Thu, October 7, 2010 6:21:15 PM
> Subject: Re: [gentoo-user] Copying a file via ssh with no password, keeping
> the
>system safe
>
> Momesso Andrea wrote
On Thu, Oct 07, 2010 at 08:40:31PM +0200, Andrea Conti wrote:
> > Is there a way to allow only one single command from a single cronjob to
> > operate passwordless, while keeping all the other connections secured by
> > a password?
>
> You can't do that on a per-command basis. You'd be trying to c
Momesso Andrea wrote:
>
> Quoting Andrea Conti :
>
> > On 07/10/2010 18:45, Momesso Andrea wrote:
> >
> >> Setting up a public key, would do the job, but then, all the connections
> >> between the servers would be passwordless, so if server A gets
> >> compromised, also server B is screwed.
> >
Quoting Andrea Conti :
On 07/10/2010 18:45, Momesso Andrea wrote:
Setting up a public key, would do the job, but then, all the connections
between the servers would be passwordless, so if server A gets
compromised, also server B is screwed.
Well, not really... public key authentication work
On 07/10/2010 18:45, Momesso Andrea wrote:
> Setting up a public key, would do the job, but then, all the connections
> between the servers would be passwordless, so if server A gets
> compromised, also server B is screwed.
Well, not really... public key authentication works on a per-user basis,
On Thu, Oct 07, 2010 at 02:14:47PM -0400, Willie Wong wrote:
> On Thu, Oct 07, 2010 at 06:45:49PM +0200, Momesso Andrea wrote:
> > I need to set up a cron job to transfer a file every day from server A
> > to server B.
> >
> > I'd like to do that via ssh and with no user assistance, completely
On Thu, Oct 07, 2010 at 06:45:49PM +0200, Momesso Andrea wrote:
> I need to set up a cron job to transfer a file every day from server A
> to server B.
>
> I'd like to do that via ssh and with no user assistance, completely
> automated.
>
> Setting up a public key, would do the job, but then,
On 7 Oct 2010, at 17:45, Momesso Andrea wrote:
> I need to set up a cron job to transfer a file every day from server A to
> server B.
>
> I'd like to do that via ssh and with no user assistance, completely automated.
>
> Setting up a public key, would do the job, but then, all the connections
Hi list,
I need to set up a cron job to transfer a file every day from server A
to server B.
I'd like to do that via ssh and with no user assistance, completely automated.
Setting up a public key, would do the job, but then, all the
connections between the servers would be passwordless, s
12 matches
Mail list logo
