Remote username from port number?

[Selden Ball]

Given the information provided in SYS$REM_ID
(remote ip address and port number),
what's the best way to determine the username associated with the telnet
(or other tcp/ip) client, when that client software is running on another
member of the same VMS cluster?

I have to believe that this is "an already solved problem."

All cluster members are running Multinet, of course.

So far today, what I've come up with is the following:

From the IP address one can determine the remote cluster decnet node name
using a table lookup.

One could then use rsh or equivalent to the remote node to get the output of
MULTINET SHOW/CONNECTIONS=PID
and search that list for the port number to obtain the owning process id.

One could then search the output of
SHOW USERS/FULL/NODE=whatever
for the process id and obtain the associated username.

But that's gross :-)

Thanks for whatever help you can provide.

Selden

[Geoff Bryant]

Not giving much thought to this, but...

Post by Selden Ball
Given the information provided in SYS$REM_ID
(remote ip address and port number),
what's the best way to determine the username associated with the telnet
(or other tcp/ip) client, when that client software is running on another
member of the same VMS cluster?
I have to believe that this is "an already solved problem."
All cluster members are running Multinet, of course.
From the IP address one can determine the remote cluster decnet node name
using a table lookup.
One could then use rsh or equivalent to the remote node to get the output of
MULTINET SHOW/CONNECTIONS=PID
and search that list for the port number to obtain the owning process id.
One could then search the output of
SHOW USERS/FULL/NODE=whatever
for the process id and obtain the associated username.

For the last parrt there is f$getjpi(pid,"username") which will work in a
cluster across nodea.

Post by Selden Ball
But that's gross :-)
Thanks for whatever help you can provide.
Selden

-------------------------------------------------------------
Geoff Bryant ***@process.com
TCPware/MultiNet/PMDF/SSH/PreciseMail Engineering
Process Software http://www.process.com/
959 Concord St.
Framingham, MA 01701 USA

[Selden E Ball Jr]

Post by Geoff Bryant
Not giving much thought to this, but...

[...]

Post by Geoff Bryant

Post by Selden Ball
One could then search the output of
SHOW USERS/FULL/NODE=whatever
for the process id and obtain the associated username.

For the last parrt there is f$getjpi(pid,"username") which will work in a
cluster across nodea.

Thanks!

But there's still the problem of getting the port to pid association.

s.

[Ken Connelly]

Check out user_access.c in the multinet examples directory
(multinet_root:[multinet.examples]).

-ken

Post by Selden Ball
Given the information provided in SYS$REM_ID
(remote ip address and port number),
what's the best way to determine the username associated with the telnet
(or other tcp/ip) client, when that client software is running on another
member of the same VMS cluster?
I have to believe that this is "an already solved problem."
All cluster members are running Multinet, of course.
From the IP address one can determine the remote cluster decnet node name
using a table lookup.
One could then use rsh or equivalent to the remote node to get the output of
MULTINET SHOW/CONNECTIONS=PID
and search that list for the port number to obtain the owning process id.
One could then search the output of
SHOW USERS/FULL/NODE=whatever
for the process id and obtain the associated username.
But that's gross :-)
Thanks for whatever help you can provide.
Selden

[Ken Connelly]

Can that updated example source be made available on the Process web site?

- ken

Note that the user_access.c example needs updating for MultiNet 5.0 and later. The code assumes a BSD 4.3 format sockaddr, and it could have either a BSD 4.3 or BSD 4.4 format with MultiNet 5.0 and later. We have updated the example for MultiNet 5.2.
-----Original Message-----
Sent: Tuesday, October 17, 2006 10:21 PM
Subject: Re: Remote username from port number?
Check out user_access.c in the multinet examples directory
(multinet_root:[multinet.examples]).
-ken

Post by Selden Ball
Given the information provided in SYS$REM_ID
(remote ip address and port number),
what's the best way to determine the username associated with the telnet
(or other tcp/ip) client, when that client software is running on another
member of the same VMS cluster?
I have to believe that this is "an already solved problem."
All cluster members are running Multinet, of course.
From the IP address one can determine the remote cluster decnet node name
using a table lookup.
One could then use rsh or equivalent to the remote node to get the output of
MULTINET SHOW/CONNECTIONS=PID
and search that list for the port number to obtain the owning process id.
One could then search the output of
SHOW USERS/FULL/NODE=whatever
for the process id and obtain the associated username.
But that's gross :-)
Thanks for whatever help you can provide.
Selden

[Richard Whalen]

Note that the user_access.c example needs updating for MultiNet 5.0 and later. The code assumes a BSD 4.3 format sockaddr, and it could have either a BSD 4.3 or BSD 4.4 format with MultiNet 5.0 and later. We have updated the example for MultiNet 5.2.

-----Original Message-----
From: Ken Connelly [mailto:***@uni.edu]
Sent: Tuesday, October 17, 2006 10:21 PM
To: info-***@process.com
Subject: Re: Remote username from port number?


Check out user_access.c in the multinet examples directory
(multinet_root:[multinet.examples]).

-ken

Post by Selden Ball
Given the information provided in SYS$REM_ID
(remote ip address and port number),
what's the best way to determine the username associated with the telnet
(or other tcp/ip) client, when that client software is running on another
member of the same VMS cluster?
I have to believe that this is "an already solved problem."
All cluster members are running Multinet, of course.
From the IP address one can determine the remote cluster decnet node name
using a table lookup.
One could then use rsh or equivalent to the remote node to get the output of
MULTINET SHOW/CONNECTIONS=PID
and search that list for the port number to obtain the owning process id.
One could then search the output of
SHOW USERS/FULL/NODE=whatever
for the process id and obtain the associated username.
But that's gross :-)
Thanks for whatever help you can provide.
Selden

[Richard Whalen]

The updated example can be obtained through anonymous FTP to ftp.multinet.process.com. CD to the patches directory, then CD to the multinet051 directory.

-----Original Message-----
From: Ken Connelly [mailto:***@uni.edu]
Sent: Thursday, October 19, 2006 8:45 AM
To: info-***@process.com
Subject: Re: Remote username from port number?


Can that updated example source be made available on the Process web site?

- ken

Note that the user_access.c example needs updating for MultiNet 5.0 and later. The code assumes a BSD 4.3 format sockaddr, and it could have either a BSD 4.3 or BSD 4.4 format with MultiNet 5.0 and later. We have updated the example for MultiNet 5.2.
-----Original Message-----
Sent: Tuesday, October 17, 2006 10:21 PM
Subject: Re: Remote username from port number?
Check out user_access.c in the multinet examples directory
(multinet_root:[multinet.examples]).
-ken

Post by Selden Ball
Given the information provided in SYS$REM_ID
(remote ip address and port number),
what's the best way to determine the username associated with the telnet
(or other tcp/ip) client, when that client software is running on another
member of the same VMS cluster?
I have to believe that this is "an already solved problem."
All cluster members are running Multinet, of course.
From the IP address one can determine the remote cluster decnet node name
using a table lookup.
One could then use rsh or equivalent to the remote node to get the output of
MULTINET SHOW/CONNECTIONS=PID
and search that list for the port number to obtain the owning process id.
One could then search the output of
SHOW USERS/FULL/NODE=whatever
for the process id and obtain the associated username.
But that's gross :-)
Thanks for whatever help you can provide.
Selden