Re: SUN RPC portmapper

Chip Christian (chipprincetontele.com)
Wed, 23 Sep 1998 13:31:53 -0400

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Joseph S. D. Yao: "Re: Re[2]: Penetration testing via shrinkware"
• Previous message: Perry E. Metzger: "Re: Re[2]: Penetration testing via shrinkware"
• Maybe in reply to: Richard Christie: "Re[2]: Penetration testing via shrinkware"

Doug Hughes writes:
>There really isn't as far as I know. Some services are relatively fixed
>(e.g. NFS - 2049, network lock manager 4045), but the rest are mostly
>randomly assigned at ports above 32768. When your server registers with
>rpcbind/portmap, portmap assigns it a port. Then, when a client requests
>an RPC service, it contacts portmap/rpcbind to resolve the RPC number
>to a port and protocol (udp,tcp,tli, whatever)

smbresearch.att.com said:
> It's been a few years since I looked at the code, but as I recall
> applications bind to their own ports and simply notify the portmapper
> what they're using.

I might add that the client picks the protocol before asking the
portmapper where to find it. So we map program number + protocol into
port. As with smb, it's been over 5 years since I really did anything
with this stuff.

• Next message: Joseph S. D. Yao: "Re: Re[2]: Penetration testing via shrinkware"
• Previous message: Perry E. Metzger: "Re: Re[2]: Penetration testing via shrinkware"
• Maybe in reply to: Richard Christie: "Re[2]: Penetration testing via shrinkware"

This archive was generated by hypermail 2.0b3 on Sat Jul 17 1999 - 07:11:47 CDT