Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!ames!ucbcad!ucbvax!SPAM.ISTC.SRI.COM!gds
From: gds@SPAM.ISTC.SRI.COM.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Tcp/Ip vs a store & forward network
Message-ID: <8703302132.AA15796@spam.istc.sri.com>
Date: Mon, 30-Mar-87 17:15:03 EST
Article-I.D.: spam.8703302132.AA15796
Posted: Mon Mar 30 17:15:03 1987
Date-Received: Wed, 1-Apr-87 01:55:11 EST
References: <8703301251.AA25896@ucbvax.Berkeley.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 18
Approved: tcp-ip@sri-nic.arpa
Summary: no passwords?


     Which brings me to something I would like to get created:  FTP to
     spool so that no pswds need to make their way around the network.
     If Bitnet can transfer files to/from Unix, VMS, VM, MVS, CDC, etc
     machines - WITHOUT passwords then Tcp/Ip should be able to send
     files around to local spool systems so that the entire concept of
     FTP pswds can be eliminated.

     Hank

I would like to know what sorts of access controls are used in Bitnet to
allow or deny a user access to

* a remote file they own
* a remote file they don't own, but is not protected
* a remote file they don't own, but is protected

and how such users are prevented from sabotaging remote disks ...