<[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Secured by aspStation
Sender: [EMAIL PROTECTED]
Precedence: bulk
Mailing-List: contact <[EMAIL PROTECTED]> ; run by MajorDomo
List-Id: Secure Coding Mailing List <sc-l.securecoding.org>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <http://www.securecoding.org/list/>
List-Unsubscribe: <http://www.securecoding.org/list/>
List-Help: <http://www.securecoding.org/list/charter.php>
List-Archive: <http://lists.virus.org>
Delivered-To: mailing list [EMAIL PROTECTED]
Delivered-To: moderator for [EMAIL PROTECTED]
ljknews wrote:
> A significant difference from DECnet is that with TCP/IP any user on the
> system can open up a channel (to use a neutral term) to receive incoming
> traffic, potentially providing a capability to the outside world without
> the least bit of authentication. With DECnet (Phase IV or Phase V) on
> VMS such actions require getting a special privilege from the system
> manager (potentially granted to a specific program rather than to the
> programmer).
Hm? You mean they had to have privs on VMS to allocate a listening
port? What does that matter? DECNet doesn't only run on VMS. Years
ago, I used to be a network admin at a place that had thousands of Win95
and Mac boxes running DECNet. No such restriction, there. Had it been
DECNet/OSI that won instead of IP, I don't believe there would be any
significant difference.
BB
