[Info-vax] DECnet V proxy problem...
VAXman- at SendSpamHere.ORG
VAXman- at SendSpamHere.ORG
Thu Mar 12 12:13:49 EDT 2009
In article <00017df4$0$2129$c3e8da3 at news.astraweb.com>, JF Mezei <jfmezei.spamnot at vaxination.ca> writes:
>VAXman- @SendSpamHere.ORG wrote:
>
>> HERE$: SHOW INTRUSION
>> Intrusion Type Count Expiration Source
>> --------- ---- ----- ---------- ------
>> NETWORK SUSPECT 1 12-MAR-2009 06:58:16.37 LOCAL:.HERE::SYSTEM
>
>
>Quick ! Send the FBI over to VAXman's house, he trying to break into a
>computer !
>
>
>
>> HERE$ MCR AUTHORIZE
>> UAF> SHOW/PROXY HERE::*
>> LOCAL:.HERE::*
>> * (D)
>>
>
>
>On the real decnet, there is a NCP> SHOW EXECUTOR CHAR
> and this shows whether proxies are enabled for inbound and outbound.
>
>Perhaps the Decnet 5 equivalent might give you some insight into whether
>proxy processing is enabled or disabled ?
>
>If you have proxies defined, and doing decnet work generates intrusion
>alarms, then it would logically point to the executor not processing
>proxies.
>
On the NOT SO REAL DECnet, this is:
$ MCR NCL SHOW NODE 0 SESSION CONTROL APPLICATION FAL ALL CHARACTERISTICS
A bit more verbose but...
This shows:
HERE$ MCR NCL SHOW NODE 0 SESSION CONTROL APPLICATION FAL ALL CHARACTERISTICS
Node 0 Session Control Application FAL
at 2009-03-12-11:12:33.816-04:00Iinf
Characteristics
Client = <Default value>
Addresses =
{
number = 17
}
Outgoing Proxy = True
Incoming Proxy = True
Outgoing Alias = True
Incoming Alias = True
Node Synonym = True
Image Name = SYS$SYSTEM:FAL.EXE
User Name = <Default value>
Incoming OSI TSEL = <Default value>
OutgoingAlias Name = <Default value>
Network Priority = 0
Besides, proxy works from other nodes, just not from itself.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
http://www.quirkfactory.com/popart/asskey/eqn2.png
"Well my son, life is like a beanstalk, isn't it?"
More information about the Info-vax
mailing list