HP3000-L Archives

September 1995, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lee - Courtney <[log in to unmask]>
Reply To:
Lee - Courtney <[log in to unmask]>
Date:
Sat, 16 Sep 1995 22:47:01 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
. . . piggy backing on Rogers $PLUG ALERT$. . .
 
Chris,
 
SAFE/3000 provides what you want to accomplish today. The nice thing about
being implemented on AIF:Procedure Exits is that our logon authentication
code sees ALL the network logons that come into the system - including
those that bypass Logon-UDCs, including FTP. We have a Fortune 5 customer
who has been using SAFE for the last few years to authenticate FTP access to
their 3000 from a TANDEM system.
 
You can also use SAFE file access rules to control what can be touched
with FTP(or anything else for that matter). One thing we've tried to get
away from is reliance on MPE capabilities to enforce and define access
control on the system - not granular enough and too hard to get HP to
change/enhance/add. The mainframe approach of defining access rules and
providing discretionary access controls is much more secure and easier to
use.
 
Give me a call for more info, FTP security white paper, or PC demo diskette.
 
Regards,
 
Lee Courtney
Monterey Software Group Inc.
Cupertino California
Voice:  408-253-1778
E-Mail: [log in to unmask]

ATOM RSS1 RSS2