tenny@ootool.dec.com (Dave Tenny) (03/04/91)
Thanks to everyone who replied on security. To summarize for interested parties, the universal comments were: - watch out for wheel accounts - get ahold of COPS and run it (a system for checking file securities, etc..) and one thing which nobody suggested, and which I missed initially: - check the online sysadmin and the *printed* documentation which comes with 2.0 on security. There's quite a bit. I missed the latter, since I tend to forget to include sysadmin in my searches, and must have my librarian looking in the wrong places. Further, I almost never expect there to be anything *I* would be interested in reading in the 2.0 manuals, since I tend to live a life of emacs and Objc. Now for my next question: I bought a "Hayes Compatible" Packard-Bell 2400Plus modem to use with the NeXT. I have a Mac modem cable, and a 68030 board. At this point, all I'm trying to do is allow dialups to the machine, and dialout. I'm having the following problems, and I can't tell if it is because - the modem might be incompatible - the cable might be incompatible - NeXT getty entries and ttydb/cub don't work as advertised. The symptoms are this: - I set the modem to the params listed in the sysadmin manual. However, my modem doesn't understant the &Q_ and &V_ directives. (If I remember correctly, I don't have my notes with me). I'm hoping these are minor and not necessary things. The modem *does* recognize the other 20 or so directives. I use Hayes 2400 settings. - The first time I dial the machine, it will answer. - All subsequent attempts at dialing fail. Either the modem doesn't answer, or when it does, the system just ignores all of what transpires. No login prompt. My getty entry has tried just about everything for dev ttydb. The args to getty are "-D9600" or "-D2400" or "-d2400" (I made an entry for this and linked it in to the speed search chain). I've also tried passing ttydb as an explicit arg to getty in the quoted string of the ttys file. I've tried "dialup", "unknown", and "vt100" for terminal types. I've tried "on" and "respond" for the state switch. Nothing seems to improve the situation. It does appear that after the first dialup things just go to hell. Further, according to the manual, ttydb for inbound modem calls, and cub for outbound dialing, should arbitrate in some useful way. But after receiving one dialup and subsequently disconnecting, all attempts to use /dev/cub receive "device busy" errors. Only a % kill -HUP 1 to reset the getty processes will release the device. Then I can dial out again, until such time as a dialin happens. Clues? I've read all the docs I can find. I'll try to borrow a REAL Hayes modem to see if my modem is at fault. But maybe there are some known situations in NeXTAnswers or something. I'm still working at getting ftp access to NeXTAnswers. Dave