Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!panda!genrad!decvax!decwrl!ucbvax!HGRRUG51.BITNET!KROON
From: KROON@HGRRUG51.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: PSIAUTHORIZE V3.2
Message-ID: <8609100652.AA06929@ucbvax.Berkeley.EDU>
Date: Sun, 24-Aug-86 09:05:00 EDT
Article-I.D.: ucbvax.8609100652.AA06929
Posted: Sun Aug 24 09:05:00 1986
Date-Received: Wed, 10-Sep-86 21:59:25 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 19
Approved: info-vax@sri-kl.arpa

Is there anyone out there who has experience with PSIAUTHORIZE? Does it work
as you expected? Motive for these question is the following:

When we first installed PSI (V3.2) I played somewhat with PSIAUTHORIZE but
couldn't really get it to do what I wanted. I don't remember exactly what
went wrong, but I remember one thing very cleary: I could let PSIAUTHORIZE
crash with access violations, stack dumps and all these nice things, by
feeding it a few relatively simple commands taken almost exactly from the
samples in the documentation. I decided to forget about PSIAUTHORIZE because
I believed we could do without it. I've learned better now from experiences
that, as I believe, need no further explanation.

I want to use the PSIAUTHORIZE facilities. I you found that
it is unreliable I can stop trying and wait for a next release. If
you are using it succesfully, could you please send me a copy of your
PSI_SECURITY.COM (with scrambled DTE numbers and usernames of course)
to find out what I did wrong?

Thanks a lot. Peter A. Kroon.