Réf. : Réf. : [9fans] Auth & cron

Réf. : Réf. : [9fans] Auth & cron

[boyd.roberts]

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




you miss the point.  you have to physically enter some data.
this involves the data, a keyboard and your fingers.  read the auth
protocol docs.



                                                                  
 (Embedded                                                        
 image moved   "Fco. J. Ballesteros" <nemo@gsyc.escet.urjc.es>    
 to file:      18/07/2000 18:07                                   
 pic20955.pcx)                                                    
                                                                  



Veuillez répondre à 9fans@cse.psu.edu

Pour: 9fans@cse.psu.edu
cc:    (ccc: Boyd ROBERTS/EST/DOSI/BANQUE_INDOSUEZ/FR)
Objet:    Réf. : [9fans] Auth & cron



[-- Attachment #2: Type: text/plain, Size: 901 bytes --]


>>>>> "boyd" == boyd roberts <boyd.roberts@ca-indosuez.com> writes:

    boyd> but how do you auth the user?  there is no setuid.  you

Just like you are doing it now to run processes on the cpu server.
But you'll keep your `cron' process running forever.

The only bad point I see is that a cpu server reboot will drop your
cron entries.

    boyd> so you gotta enter some data to auth yourself.  this data
    boyd> must _never_ cross the wire.  so if you say server x is my
    boyd> preferred cron server, just how is server x's cron going to
    boyd> get the auth data to allow the cron to 'run as you'?

How are you doing that to run your process on your cpu sever?  IMHO it
can be done the same way. But, as I said, I may be missing something.


--
    ()    ascii ribbon campaign - against html mail
    /\                          - against microsoft attachments



[-- Attachment #3: pic20955.pcx --]
[-- Type: application/octet-stream, Size: 2427 bytes --]

Réf. : Réf. : [9fans] Auth & cron

[Fco. J. Ballesteros]

>>>>> "boyd" == boyd roberts <boyd.roberts@ca-indosuez.com> writes:

    boyd> you miss the point.  you have to physically enter some data.
    boyd> this involves the data, a keyboard and your fingers.  read
    boyd> the auth protocol docs.

Already read them; but let's re-read them.... done :-)

As I thought, you authenticate (using your keyboard and your
fingers;-) ) when you boot your terminal.

But, after you got your terminal running, you can use cpu to run your
`cron' process on a cpu server. If the cron process keeps on hanging
around even after you reboot your terminal, it can maintain your cron
entries.

The cron process is already authenticated and should be able to spam
new processes to run your cron entries. 

What I don't like is 

1: rebooting your cpu server makes your cron die and forget your
   entries. 
   (a workaround would be to check that it is running when you log in,
    and spawn a new cron otherwise; but that's not a fix).

2: one process per-user rather than one per site (although that may be ok).

-- 
    ()    ascii ribbon campaign - against html mail 
    /\                          - against microsoft attachments