Re: [9fans] cron auth

Re: [9fans] cron auth

[Fco.J.Ballesteros]

:  You have an old /sys/src/cmd/ip/rexexec.c?

I had an old ip/rexexec.c and I'm an ....

thanks. that was it.

Re: [9fans] cron auth

[Fco.J.Ballesteros]

[-- Attachment #1: Type: text/plain, Size: 237 bytes --]

I start just one factotum (at boot time, the kernel launches one).
What I do is to update its set of keys later, when secstore starts.
I'll check to see if I have an old rexexec version as Presotto said.

Thank u all for your help.

[-- Attachment #2: Type: message/rfc822, Size: 1325 bytes --]

From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cron auth
Date: Fri, 20 Sep 2002 16:23:26 -0700
Message-ID: <3e8e490772796ee4f293b855ba2e305d@collyer.net>

Are you starting a factotum on your auth server explicitly?  The
kernel always starts one (as yourself on a terminal and as bootes on a
cpu server), so you probably shouldn't start a second bootes factotum.

Re: [9fans] cron auth

[Geoff Collyer]

Are you starting a factotum on your auth server explicitly?  The
kernel always starts one (as yourself on a terminal and as bootes on a
cpu server), so you probably shouldn't start a second bootes factotum.

Re: [9fans] cron auth

[presotto]

[-- Attachment #1: Type: text/plain, Size: 42 bytes --]

You have an old /sys/src/cmd/ip/rexexec.c?

[-- Attachment #2: Type: message/rfc822, Size: 1725 bytes --]

From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] cron auth
Date: Fri, 20 Sep 2002 14:03:04 +0200
Message-ID: <8c59d20149472ee5f6d21929e0522979@plan9.escet.urjc.es>

I'm a bit confussed, and perhaps I'm
missing an obvious thing that someone else could just point out.

In my auth server I start cron.
I also start a factotum at boot time (authenticates fine with the fs).
Then I also use the secstore -G option to feed the factotum with the
keys in the secstore.

However, it seems that since time ago cron has not been able
to authenticate other users to run their entries. The error is a
protocol phase error (read in state CNeedProtos).

Any obvious thing?

thanks

[9fans] cron auth

[Fco.J.Ballesteros]

I'm a bit confussed, and perhaps I'm
missing an obvious thing that someone else could just point out.

In my auth server I start cron.
I also start a factotum at boot time (authenticates fine with the fs).
Then I also use the secstore -G option to feed the factotum with the
keys in the secstore.

However, it seems that since time ago cron has not been able
to authenticate other users to run their entries. The error is a
protocol phase error (read in state CNeedProtos).

Any obvious thing?

thanks