From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: Alexander Povolotsky Message-ID: <9c4063$8t7@nntpa.cb.lucent.com> References: <20010424123215.A0CC919AEA@mail.cse.psu.edu> Subject: Re: [9fans] Drawterm vs Authentication Server Date: Tue, 24 Apr 2001 13:54:26 +0000 Topicbox-Message-UUID: 8e27a334-eac9-11e9-9e20-41e7f4b1d025 I was under the impression (per following e-mail, I am attaching below ), that on the terminal Plan 9 machine, there will be a problem with running keyfs. in regards to readable /dev/key........ -----Original Message----- From: Russ Cox [mailto:rsc@plan9.bell-labs.com] Sent: Wednesday, April 18, 2001 10:18 AM To: ap80@lucent.com Subject: RE: FW: drawterm connection failure You need to set up an authentication server. That's a bit more complex. You need to start by running auth/keyfs (see the man page) and then adding users with auth/changeuser. To run the keyfs, though, you need to have a readable /dev/key (normally found only on cpu servers). The easiest way to do this is build a new kernel. Specifically, edit /sys/src/9/port/auth.c, and in the keyread() function change if(!cpuserver || !iseve()) error(Eperm); to if(!iseve()) error(Eperm); and then rebuild your kernel. Russ wrote in message news:20010424123215.A0CC919AEA@mail.cse.psu.edu... > There's nothing special about the auth server except for who knows > that its the auth server. You can always start auth/keyfs and run > aux/listen -t /rc/bin/service.auth on any machine and transform it > into an auth server. > > If you want no authentication, you can change both cpu and drawterm. If > you look closely at the cpu command, you'll see that it negotiates > authentication mechanism. If you change cpu.c and drawterm.c to allow > a null authentication mechanism, you'll have what you want. Look at > authmethod in both programs.