| Title: | Zap Technical Conference |
| Notice: | ZAP Version 5.3 is available. See note 1.1 |
| Moderator: | ZAPDEV::MACONI |
| Created: | Mon Feb 24 1986 |
| Last Modified: | Mon May 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 170 |
| Total number of notes: | 492 |
Zap V3.5
It is easy to fool Zap into thinking your UIC is [1,4], you just
have to take your time logging in!!!
I have had a number of cases where Zap was not killing processes
when it was expected to. I ran Zap with debug on and found that
Zap thought the UIC of the process was [1,4]. I found I could
quite easily fool Zap by taking a long time at the Username and
Password prompts when logging in.
My guess is that Zap does a scan while I am logging in and associates
my UIC and PID at that time. Up until the time the UAF record is
verified my UIC will be [1,4]. If Zap first finds me before my real
UIC is in effect it will always think I'm [1,4].
..Paul
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 25.1 | Problem corrected | MRMFG1::K_MACONI | The Doctor | Tue Oct 07 1986 17:50 | 12 |
This problem occurred because Zap determines the uic of the process
the first time it encounters it on the system. This would result
in any process which was detected while it was in LOGINOUT being
permanently assigned the [1,4] uic. This problem has been corrected
by forcing Zap to update the uic of every process each time it is
scanned on the system. Also, a message is written out to the Zap
log file each time it encounters a process which has changed its
uic.
These changes are incorporated in version 3.5-1 of Zap. To obtain
this version, see note 1.1
| |||||
| 25.2 | disable uic change message | ZGOV01::CTTAN | I am therefore I am | Wed Dec 10 1986 19:15 | 2 |
Is there any way that I can tell zap not to write out the message
that it has changed any process uic to the log file?
| |||||
| 25.3 | V3.6-1 (Create date 15-DEC-86) | MRMFG1::K_MACONI | The Doctor | Mon Dec 15 1986 10:50 | 11 |
There is no facility to turn off the messages that Zap writes to
its log file. However, your message did bring to my attention that
many times when a user logs into the system, Zap warns you that
its uic has changed from [1,4] to [x,y].
A new version, V3.6-1, has been created which does not log when
a user changes its uic FROM [1,4]. This means that you will only
receive a message when a user changes FROM any uic OTHER THAN [1,4].
(Changes TO [1,4] will be noted).
Keith Maconi
| |||||