On 2013-06-15 18:51, Paul_Koning at
Dell.com wrote:
On Jun 15, 2013, at 11:14 AM, Johnny Billquist wrote:
On 2013-06-15 17:03, Paul_Koning at
Dell.com wrote:
On Jun 15, 2013, at 9:19 AM, Johnny Billquist wrote:
...
Proxy access is not standardized or documented (at the protocol level). I think it's
simply this: the access control fields in the session control protocol are optional. If
they are omitted, it's up to the receiving node to decide what to do about it (if the
application protocol in question has the notion of access control). In some systems, the
answer is "reject". In others, the answer is "use a default account"
(RSTS has this).
Well, proxy is something that needs to be enabled on both sides for it to work, so it
definitely involves passing some information in the packets. So it has to be documented
somewhere. Keep searching.
I don't think so. RSTS has no notion of proxy, but I distinctly remember having
proxies on VMS work when accessed from RSTS with no access control specified.
No. It has to be enabled on both sides. Easy to test. If I just turn off outgoing proxy on
a VMS node, proxy access does not work on RSX for the incoming connection. No matter what
I do on the RSX side.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic
trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" -
B. Idol