home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!uakari.primate.wisc.edu!ames!bionet!raven.alaska.edu!sxjcb.uacn.alaska.edu!user
- From: sxjcb@orca.alaska.edu (Jay C. Beavers)
- Newsgroups: comp.os.ms-windows.programmer.win32
- Subject: Process Security in NT
- Message-ID: <sxjcb-100992122022@sxjcb.uacn.alaska.edu>
- Date: 10 Sep 92 20:28:27 GMT
- Sender: news@raven.alaska.edu (USENET News System)
- Followup-To: comp.os.ms-windows.programmer.win32
- Organization: University of Alaska Computer Network
- Lines: 24
- Nntp-Posting-Host: sxjcb.uacn.alaska.edu
-
-
- As I impatiently await the arrival of my very backordered NEC CDR-84, I've
- been perusing the documentation that comes with the NT pre-beta SDK and I'm
- surprised to find that NT requires you to log in. This brings up the next
- question which I haven't found an answer to, does NT have user security
- restrictions on processes? I.E. does this process run in the background
- with this security level while a separate process runs with a different
- security level? If so, why all the moaning about lack of multi-user
- support in NT? All the basics are more than present and a telnetd is
- nothing more than a background daemon that hasn't been written yet.
-
- BTW, is anyone thinking of writing a GUI version of telnet or rlogin? Is
- it going to be necessary or is RPC and peer-to-peer networking going to
- totally replace the command-line login metaphor?
-
- Are daemon and process bad words for NT that have been replaced with more
- 'MC (Microsoft Correct)' jargon? Threads means processes, but how about
- daemon? Background thread?
-
- ______________________________________________________________________________
- | jay@seaspray.uacn.alaska.edu
- Jay C. Beavers | sxjcb@orca.alaska.edu
- University of Alaska Computer Network | sxjcb@alaska.bitnet
- ________________________________________|_____________________________________
-