From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: Alexander Povolotsky Message-ID: <9fh4ks$5ou@nntpb.cb.lucent.com> References: <20010604171739.IVMO8623.femail1.sdc1.sfba.home.com@localhost>, Subject: Re: [9fans] Mail on cpu/auth server Date: Tue, 5 Jun 2001 08:26:51 +0000 Topicbox-Message-UUID: b0127e42-eac9-11e9-9e20-41e7f4b1d025 When I am creating a new user (say guest) using auth/changeuser I could see this message Ishwar mentioned: keysfs: bad status key in file But at least it creates the keyfile and creates the password ... For already existant users (glenda, adm, sys etc ) I somehow lost keys at some point (do not remember exactly how ...) and now if I am trying to recreate keys for those users using auth/changeuser - it fails with the error message: changeuser: can't create user "such and such": access permission denied. By the way, I do not have password set for those preexistant ones - how I could set password for those ? So, anyway, now I could reboot the system and log as guest with supplying the password ... Ok, I am looged in ... Running auth/keyfs -p Password: Works ...kind of ... but with the warning again: bad status in key file ... Ok ... going further ... aux/listen tcp auth/listen -t /rc/bin/service.auth No errors or warnings ... Now I am starting the drawterm on my Solaris machine: yarmouth$ drawterm -a 135.17.241.14 -c 135.17.241.14 default depth=8 yarmouth$ !! drawterm -a 135.17.241.14 -c 135.17.241.14 default depth=8 The drawterm window shows up with user "none" - changing to guest .. Supplying the password ... Getting ... ?AS protocol botch: file does not exist. Any hints ? "Ish Rattan" wrote in message news:Pine.LNX.4.30.0106041419420.22193-100000@pali.cps.cmich.edu... > On Mon, 4 Jun 2001, Jonathan Sergent wrote: > > > On Monday, June 4, 2001, at 09:33 AM, Ish Rattan wrote: > > > > > I see the follwing messages in /sys/log/cron > > > > > > host Jun 4 06:52:04 upas: key not found > > > > > > similar message generated every 10 minutes. What key is it referring to? > > > > The one for upas. auth/changeuser upas to give it a key so that cron > > can authenticate as upas. cron must run only on your auth server so > > that it can authenticate as the right user. It does an rx to the target > > host to run the command. > An attempt to use auth/changeuser upas > Passord: > Confirm ..: > keysfs: bad status key in file > ... > 6 keys read > Post id: > > Did 3/27/01 upgrade has anything to do with it? > > Also, what happens if I just remove adm/keys and /adm/keys.who and > recreate them with auth/changeuser??? > > - ishwar