mizo@helium.Berkeley.EDU (Hideo Mizoguchi) (11/17/90)
Hi, I have just got an old cube. Now I have a trouble with kermit. I got souce files for kemit by 'tip' and '~t' and compiled them on my cube. With lots of 'warnings' it compiled anyway. My question is which device to set in 'set line' command in kermit. My modem is hooked up to sereal A port. Since I have never owned unix machine myself, I don't know much about those /dev/*** files. Please reply directly to mizo@helium.berkeley.edu Thank you Hideo Mizoguchi Graduate student , University of California at Berkeley
nates@sporobolus.NREL.ColoState.EDU (Nate Sammons) (05/26/91)
Hello out there,
I have a problem with Kermit. (C-Kermit 5A(170) ALPHA, 23 Apr 91, NeXT)
I get it 'made' and then I run it, type:
C-Kermit>set modem-dialer hayes //no problem
C-Kermit>set line /dev/cua //PROBLEM
Then it says:
/dev/cua: Permission denied
Sorry, access to tty device denied
Can anyone out there help me??
-Nate Sammons
<nates@Sporobolus.NREL.ColoState.Edu>
<nsammons@Lobo.RMHS.Colorado.Edu>hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) (05/26/91)
In article <15140@ccncsu.ColoState.EDU> nates@sporobolus.NREL.ColoState.EDU (Nate Sammons) writes:
Then it says:
/dev/cua: Permission denied
Sorry, access to tty device denied
Either chmod +w /dev/cua or chown uucp /usr/local/bin/kermit (or
wherever you put kermit , e.g., /LocalApps/kermit).
Greetings,
Hardy
-------****-------
Meinhard E. Mayer (Hardy); Department of Physics, University of California
Irvine CA 92717; (714) 856 5543; hardy@golem.ps.uci.edu or MMAYER@UCI.BITNETmadler@nntp-server.caltech.edu (Mark Adler) (05/27/91)
Hardy Mayer suggests to the fellow having /dev/cu* access problems: >> Either chmod +w /dev/cua or chown uucp /usr/local/bin/kermit (or >> wherever you put kermit , e.g., /LocalApps/kermit). Well, not exactly. The first suggestion will work, but it is the decidedly unkosher way to do it. The second way won't work, since it is incomplete. It is however half of the kosher solution. You need to: chown uucp kermit chmod u+s kermit as root. The first command makes uucp the owner of the kermit executable. The second command gives kermit the permissions of it's owner (uucp) when it runs. This then allows kermit to use the /dev/cu* devices, since they are also owned by uucp, and their permissions are crw------- (only the owner and root can read or write to them). The reason its done this way is to restrict access to the /dev/cu* ports to those programs that deal with UUCP lock files properly, such as kermit, tip, cu, and uucp. This makes sure that only one program can think it owns the serial port. Don't worry about security problems, since kermit knows how to handle being run setuid, and files are read or written using the permissions of the person running kermit--not the permissions of uucp. (This is true of 5A or later versions of C-Kermit--the fellow has 5A(170).) Mark Adler madler@tybalt.caltech.edu