Hi, As given in NASL reference guide, get_rpc_port(program, protocol) calls the portmapper and gets the port where the service specified by the parameters is located. program is a RPC number and protocol may be IPPROTO_TCP or IPPROTO_UDP. If the portmapper could not be reached or the service is down, the function returns 0.
You can refer programs given below for the function usage. bootparamd.nasl:port = get_rpc_port(program:RPC_PROG, protocol:IPPROTO_UDP); cachefsd_overflow.nasl:port = get_rpc_port(program:RPC_PROG, protocol:IPPROTO_UDP); knfs_dos.nasl:port = get_rpc_port(program:100003, protocol:IPPROTO_UDP); mountd_overflow.nasl:port = get_rpc_port(program:100005, protocol:IPPROTO_UDP); netinfo_passwd.nasl:function get_rpc_port(protocol) netinfo_rpc.nasl:function get_rpc_port(protocol) nfs_dotdot.nasl:port2 = get_rpc_port(program:100003, protocol:IPPROTO_UDP); nfs_fsirand.nasl:port = get_rpc_port(program:100005, protocol:IPPROTO_TCP); etc. On Feb 9, 2008 1:16 AM, marco <[EMAIL PROTECTED]> wrote: > Hi all, > I just subscribed to the mailing list, and here you go with my first > question: > > I wonder how to get the function get_rpc_port works, it is defined in > the misc_function.inc library. > The syntax is supposed to get a program number and the protocol. What > does the parameter "program" is meant to be? I have the hunch it is > related to some kinda portmapping translation but I suppose there > should be a static mapping between a program number and its related > process' name. For example I'd like to issue the program number > concerning firefox in order to get the port where the process is > listening to. > > thank you in advance > > -- > Marco > _______________________________________________ > Nessus mailing list > [email protected] > http://mail.nessus.org/mailman/listinfo/nessus > -- Thanks, Pavithra.H Research Analyst, ThirdBrigade Labs Bangalore
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
