Mirror/zeek
1
0
Fork 0
mirror of https://github.com/zeek/zeek.git synced 2025-10-16 13:38:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
zeek/doc/scripts/base/bif/plugins/Zeek_RPC.events.bif.zeek.rst
Tim Wojtulewicz e90d8f37f1 Regenerate docs with src and script changes
2025-10-14 16:30:32 +00:00

1320 lines
54 KiB
ReStructuredText
Raw Blame History

:tocdepth: 3
base/bif/plugins/Zeek_RPC.events.bif.zeek
=========================================
.. zeek:namespace:: GLOBAL
:Namespace: GLOBAL
Summary
~~~~~~~
Events
######
========================================================= ==========================================================================
:zeek:id:`mount_proc_mnt`: :zeek:type:`event` Generated for MOUNT3 request/reply dialogues of type *mnt*.
:zeek:id:`mount_proc_not_implemented`: :zeek:type:`event` Generated for MOUNT3 request/reply dialogues of a type that Zeek's MOUNTv3
analyzer does not implement.
:zeek:id:`mount_proc_null`: :zeek:type:`event` Generated for MOUNT3 request/reply dialogues of type *null*.
:zeek:id:`mount_proc_umnt`: :zeek:type:`event` Generated for MOUNT3 request/reply dialogues of type *umnt*.
:zeek:id:`mount_proc_umnt_all`: :zeek:type:`event` Generated for MOUNT3 request/reply dialogues of type *umnt_all*.
:zeek:id:`mount_reply_status`: :zeek:type:`event` Generated for each MOUNT3 reply message received, reporting just the
status included.
:zeek:id:`nfs_proc_create`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *create*.
:zeek:id:`nfs_proc_getattr`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *getattr*.
:zeek:id:`nfs_proc_link`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *link*.
:zeek:id:`nfs_proc_lookup`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *lookup*.
:zeek:id:`nfs_proc_mkdir`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *mkdir*.
:zeek:id:`nfs_proc_not_implemented`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of a type that Zeek's NFSv3
analyzer does not implement.
:zeek:id:`nfs_proc_null`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *null*.
:zeek:id:`nfs_proc_read`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *read*.
:zeek:id:`nfs_proc_readdir`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *readdir*.
:zeek:id:`nfs_proc_readlink`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *readlink*.
:zeek:id:`nfs_proc_remove`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *remove*.
:zeek:id:`nfs_proc_rename`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *rename*.
:zeek:id:`nfs_proc_rmdir`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *rmdir*.
:zeek:id:`nfs_proc_sattr`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *sattr*.
:zeek:id:`nfs_proc_symlink`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *symlink*.
:zeek:id:`nfs_proc_write`: :zeek:type:`event` Generated for NFSv3 request/reply dialogues of type *write*.
:zeek:id:`nfs_reply_status`: :zeek:type:`event` Generated for each NFSv3 reply message received, reporting just the
status included.
:zeek:id:`pm_attempt_callit`: :zeek:type:`event` Generated for failed Portmapper requests of type *callit*.
:zeek:id:`pm_attempt_dump`: :zeek:type:`event` Generated for failed Portmapper requests of type *dump*.
:zeek:id:`pm_attempt_getport`: :zeek:type:`event` Generated for failed Portmapper requests of type *getport*.
:zeek:id:`pm_attempt_null`: :zeek:type:`event` Generated for failed Portmapper requests of type *null*.
:zeek:id:`pm_attempt_set`: :zeek:type:`event` Generated for failed Portmapper requests of type *set*.
:zeek:id:`pm_attempt_unset`: :zeek:type:`event` Generated for failed Portmapper requests of type *unset*.
:zeek:id:`pm_bad_port`: :zeek:type:`event` Generated for Portmapper requests or replies that include an invalid port
number.
:zeek:id:`pm_request_callit`: :zeek:type:`event` Generated for Portmapper request/reply dialogues of type *callit*.
:zeek:id:`pm_request_dump`: :zeek:type:`event` Generated for Portmapper request/reply dialogues of type *dump*.
:zeek:id:`pm_request_getport`: :zeek:type:`event` Generated for Portmapper request/reply dialogues of type *getport*.
:zeek:id:`pm_request_null`: :zeek:type:`event` Generated for Portmapper requests of type *null*.
:zeek:id:`pm_request_set`: :zeek:type:`event` Generated for Portmapper request/reply dialogues of type *set*.
:zeek:id:`pm_request_unset`: :zeek:type:`event` Generated for Portmapper request/reply dialogues of type *unset*.
:zeek:id:`rpc_call`: :zeek:type:`event` Generated for RPC *call* messages.
:zeek:id:`rpc_dialogue`: :zeek:type:`event` Generated for RPC request/reply *pairs*.
:zeek:id:`rpc_reply`: :zeek:type:`event` Generated for RPC *reply* messages.
========================================================= ==========================================================================
Detailed Interface
~~~~~~~~~~~~~~~~~~
Events
######
.. zeek:id:: mount_proc_mnt
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 929 929
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`MOUNT3::info_t`, req: :zeek:type:`MOUNT3::dirmntargs_t`, rep: :zeek:type:`MOUNT3::mnt_reply_t`)
Generated for MOUNT3 request/reply dialogues of type *mnt*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
MOUNT is a service running on top of RPC.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: The arguments passed in the request.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: mount_proc_mnt mount_proc_umnt
mount_proc_umnt_all mount_proc_not_implemented
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: mount_proc_not_implemented
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 990 990
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`MOUNT3::info_t`, proc: :zeek:type:`MOUNT3::proc_t`)
Generated for MOUNT3 request/reply dialogues of a type that Zeek's MOUNTv3
analyzer does not implement.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param proc: The procedure called that Zeek does not implement.
.. zeek:see:: mount_proc_mnt mount_proc_umnt
mount_proc_umnt_all mount_proc_not_implemented
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: mount_proc_null
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 905 905
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`MOUNT3::info_t`)
Generated for MOUNT3 request/reply dialogues of type *null*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
MOUNT is a service running on top of RPC.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
.. zeek:see:: mount_proc_mnt mount_proc_umnt
mount_proc_umnt_all mount_proc_not_implemented
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: mount_proc_umnt
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 950 950
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`MOUNT3::info_t`, req: :zeek:type:`MOUNT3::dirmntargs_t`)
Generated for MOUNT3 request/reply dialogues of type *umnt*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
MOUNT is a service running on top of RPC.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: The arguments passed in the request.
.. zeek:see:: mount_proc_mnt mount_proc_umnt
mount_proc_umnt_all mount_proc_not_implemented
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: mount_proc_umnt_all
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 971 971
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`MOUNT3::info_t`, req: :zeek:type:`MOUNT3::dirmntargs_t`)
Generated for MOUNT3 request/reply dialogues of type *umnt_all*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
MOUNT is a service running on top of RPC.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: The arguments passed in the request.
.. zeek:see:: mount_proc_mnt mount_proc_umnt
mount_proc_umnt_all mount_proc_not_implemented
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: mount_reply_status
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 1007 1007
:Type: :zeek:type:`event` (n: :zeek:type:`connection`, info: :zeek:type:`MOUNT3::info_t`)
Generated for each MOUNT3 reply message received, reporting just the
status included.
:param n: The connection.
:param info: Reports the status included in the reply.
.. zeek:see:: mount_proc_mnt mount_proc_umnt
mount_proc_umnt_all mount_proc_not_implemented
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_create
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 287 287
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::diropargs_t`, rep: :zeek:type:`NFS3::newobj_reply_t`)
Generated for NFSv3 request/reply dialogues of type *create*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: TODO.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status
rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_getattr
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 54 54
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, fh: :zeek:type:`string`, attrs: :zeek:type:`NFS3::fattr_t`)
Generated for NFSv3 request/reply dialogues of type *getattr*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param fh: TODO.
:param attrs: The attributes returned in the reply. The values may not be valid if
the request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status
rpc_call rpc_dialogue rpc_reply file_mode
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_link
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 228 228
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::linkargs_t`, rep: :zeek:type:`NFS3::link_reply_t`)
Generated for NFSv3 request/reply dialogues of type *link*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: The arguments passed in the request.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status rpc_call
nfs_proc_symlink rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_lookup
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 112 112
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::diropargs_t`, rep: :zeek:type:`NFS3::lookup_reply_t`)
Generated for NFSv3 request/reply dialogues of type *lookup*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: The arguments passed in the request.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status
rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_mkdir
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 316 316
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::diropargs_t`, rep: :zeek:type:`NFS3::newobj_reply_t`)
Generated for NFSv3 request/reply dialogues of type *mkdir*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: TODO.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status
rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_not_implemented
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 456 456
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, proc: :zeek:type:`NFS3::proc_t`)
Generated for NFSv3 request/reply dialogues of a type that Zeek's NFSv3
analyzer does not implement.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param proc: The procedure called that Zeek does not implement.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_null nfs_proc_read nfs_proc_readdir nfs_proc_readlink nfs_proc_remove
nfs_proc_rmdir nfs_proc_write nfs_reply_status rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_null
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 25 25
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`)
Generated for NFSv3 request/reply dialogues of type *null*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_read nfs_proc_readdir nfs_proc_readlink
nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_read
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 141 141
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::readargs_t`, rep: :zeek:type:`NFS3::read_reply_t`)
Generated for NFSv3 request/reply dialogues of type *read*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: The arguments passed in the request.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_remove nfs_proc_rmdir
nfs_proc_write nfs_reply_status rpc_call rpc_dialogue rpc_reply
NFS3::return_data NFS3::return_data_first_only NFS3::return_data_max
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_readdir
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 432 432
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::readdirargs_t`, rep: :zeek:type:`NFS3::readdir_reply_t`)
Generated for NFSv3 request/reply dialogues of type *readdir*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: TODO.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readlink
nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_readlink
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 170 170
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, fh: :zeek:type:`string`, rep: :zeek:type:`NFS3::readlink_reply_t`)
Generated for NFSv3 request/reply dialogues of type *readlink*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param fh: The file handle passed in the request.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status
nfs_proc_symlink rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_remove
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 345 345
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::diropargs_t`, rep: :zeek:type:`NFS3::delobj_reply_t`)
Generated for NFSv3 request/reply dialogues of type *remove*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: TODO.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_rmdir nfs_proc_write nfs_reply_status rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_rename
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 403 403
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::renameopargs_t`, rep: :zeek:type:`NFS3::renameobj_reply_t`)
Generated for NFSv3 request/reply dialogues of type *rename*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: TODO.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rename nfs_proc_write
nfs_reply_status rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_rmdir
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 374 374
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::diropargs_t`, rep: :zeek:type:`NFS3::delobj_reply_t`)
Generated for NFSv3 request/reply dialogues of type *rmdir*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: TODO.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_write nfs_reply_status rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_sattr
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 83 83
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::sattrargs_t`, rep: :zeek:type:`NFS3::sattr_reply_t`)
Generated for NFSv3 request/reply dialogues of type *sattr*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: The arguments passed in the request.
:param rep: The attributes returned in the reply. The values may not be
valid if the request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status
rpc_call rpc_dialogue rpc_reply file_mode
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_symlink
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 199 199
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::symlinkargs_t`, rep: :zeek:type:`NFS3::newobj_reply_t`)
Generated for NFSv3 request/reply dialogues of type *symlink*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: The arguments passed in the request.
:param rep: The attributes returned in the reply. The values may not be
valid if the request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rmdir nfs_proc_write nfs_reply_status
nfs_proc_link rpc_call rpc_dialogue rpc_reply file_mode
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_proc_write
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 258 258
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`, req: :zeek:type:`NFS3::writeargs_t`, rep: :zeek:type:`NFS3::write_reply_t`)
Generated for NFSv3 request/reply dialogues of type *write*. The event is
generated once we have either seen both the request and its corresponding
reply, or an unanswered request has timed out.
NFS is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
information about the service.
:param c: The RPC connection.
:param info: Reports the status of the dialogue, along with some meta information.
:param req: TODO.
:param rep: The response returned in the reply. The values may not be valid if the
request was unsuccessful.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rmdir nfs_reply_status rpc_call
rpc_dialogue rpc_reply NFS3::return_data NFS3::return_data_first_only
NFS3::return_data_max
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: nfs_reply_status
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 475 475
:Type: :zeek:type:`event` (n: :zeek:type:`connection`, info: :zeek:type:`NFS3::info_t`)
Generated for each NFSv3 reply message received, reporting just the
status included.
:param n: The connection.
:param info: Reports the status included in the reply.
.. zeek:see:: nfs_proc_create nfs_proc_getattr nfs_proc_lookup nfs_proc_mkdir
nfs_proc_not_implemented nfs_proc_null nfs_proc_read nfs_proc_readdir
nfs_proc_readlink nfs_proc_remove nfs_proc_rmdir nfs_proc_write rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_attempt_callit
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 770 770
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, status: :zeek:type:`rpc_status`, call: :zeek:type:`pm_callit_request`)
Generated for failed Portmapper requests of type *callit*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param status: The status of the reply, which should be one of the index values of
:zeek:id:`RPC_status`.
:param call: The argument to the original request.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_dump pm_request_callit
pm_attempt_null pm_attempt_set pm_attempt_unset
pm_attempt_getport pm_attempt_dump pm_bad_port rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_attempt_dump
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 744 744
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, status: :zeek:type:`rpc_status`)
Generated for failed Portmapper requests of type *dump*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param status: The status of the reply, which should be one of the index values of
:zeek:id:`RPC_status`.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_dump pm_request_callit
pm_attempt_null pm_attempt_set pm_attempt_unset
pm_attempt_getport pm_attempt_callit pm_bad_port rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_attempt_getport
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 720 720
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, status: :zeek:type:`rpc_status`, pr: :zeek:type:`pm_port_request`)
Generated for failed Portmapper requests of type *getport*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param status: The status of the reply, which should be one of the index values of
:zeek:id:`RPC_status`.
:param pr: The argument to the original request.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_dump pm_request_callit
pm_attempt_null pm_attempt_set pm_attempt_unset pm_attempt_dump
pm_attempt_callit pm_bad_port rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_attempt_null
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 643 643
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, status: :zeek:type:`rpc_status`)
Generated for failed Portmapper requests of type *null*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param status: The status of the reply, which should be one of the index values of
:zeek:id:`RPC_status`.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_dump pm_request_callit
pm_attempt_set pm_attempt_unset pm_attempt_getport
pm_attempt_dump pm_attempt_callit pm_bad_port rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_attempt_set
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 669 669
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, status: :zeek:type:`rpc_status`, m: :zeek:type:`pm_mapping`)
Generated for failed Portmapper requests of type *set*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param status: The status of the reply, which should be one of the index values of
:zeek:id:`RPC_status`.
:param m: The argument to the original request.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_dump pm_request_callit
pm_attempt_null pm_attempt_unset pm_attempt_getport
pm_attempt_dump pm_attempt_callit pm_bad_port rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_attempt_unset
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 695 695
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, status: :zeek:type:`rpc_status`, m: :zeek:type:`pm_mapping`)
Generated for failed Portmapper requests of type *unset*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param status: The status of the reply, which should be one of the index values of
:zeek:id:`RPC_status`.
:param m: The argument to the original request.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_dump pm_request_callit
pm_attempt_null pm_attempt_set pm_attempt_getport
pm_attempt_dump pm_attempt_callit pm_bad_port rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_bad_port
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 796 796
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, bad_p: :zeek:type:`count`)
Generated for Portmapper requests or replies that include an invalid port
number. Since ports are represented by unsigned 4-byte integers, they can
stray outside the allowed range of 0--65535 by being >= 65536. If so, this
event is generated.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param bad_p: The invalid port value.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_dump pm_request_callit
pm_attempt_null pm_attempt_set pm_attempt_unset
pm_attempt_getport pm_attempt_dump pm_attempt_callit rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_request_callit
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 619 619
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, call: :zeek:type:`pm_callit_request`, p: :zeek:type:`port`)
Generated for Portmapper request/reply dialogues of type *callit*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param call: The argument to the request.
:param p: The port value returned by the call.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_dump pm_attempt_null
pm_attempt_set pm_attempt_unset pm_attempt_getport
pm_attempt_dump pm_attempt_callit pm_bad_port rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_request_dump
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 594 594
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, m: :zeek:type:`pm_mappings`)
Generated for Portmapper request/reply dialogues of type *dump*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param m: The mappings returned by the server.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_getport pm_request_callit pm_attempt_null
pm_attempt_set pm_attempt_unset pm_attempt_getport
pm_attempt_dump pm_attempt_callit pm_bad_port rpc_call
rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_request_getport
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 571 571
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, pr: :zeek:type:`pm_port_request`, p: :zeek:type:`port`)
Generated for Portmapper request/reply dialogues of type *getport*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param pr: The argument to the request.
:param p: The port returned by the server.
.. zeek:see:: pm_request_null pm_request_set pm_request_unset
pm_request_dump pm_request_callit pm_attempt_null pm_attempt_set
pm_attempt_unset pm_attempt_getport pm_attempt_dump
pm_attempt_callit pm_bad_port rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_request_null
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 495 495
:Type: :zeek:type:`event` (r: :zeek:type:`connection`)
Generated for Portmapper requests of type *null*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
.. zeek:see:: pm_request_set pm_request_unset pm_request_getport
pm_request_dump pm_request_callit pm_attempt_null pm_attempt_set
pm_attempt_unset pm_attempt_getport pm_attempt_dump
pm_attempt_callit pm_bad_port rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_request_set
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 521 521
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, m: :zeek:type:`pm_mapping`, success: :zeek:type:`bool`)
Generated for Portmapper request/reply dialogues of type *set*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param m: The argument to the request.
:param success: True if the request was successful, according to the corresponding
reply. If no reply was seen, this will be false once the request
times out.
.. zeek:see:: pm_request_null pm_request_unset pm_request_getport
pm_request_dump pm_request_callit pm_attempt_null pm_attempt_set
pm_attempt_unset pm_attempt_getport pm_attempt_dump
pm_attempt_callit pm_bad_port rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: pm_request_unset
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 547 547
:Type: :zeek:type:`event` (r: :zeek:type:`connection`, m: :zeek:type:`pm_mapping`, success: :zeek:type:`bool`)
Generated for Portmapper request/reply dialogues of type *unset*.
Portmapper is a service running on top of RPC. See `Wikipedia
<https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
service.
:param r: The RPC connection.
:param m: The argument to the request.
:param success: True if the request was successful, according to the corresponding
reply. If no reply was seen, this will be false once the request
times out.
.. zeek:see:: pm_request_null pm_request_set pm_request_getport
pm_request_dump pm_request_callit pm_attempt_null pm_attempt_set
pm_attempt_unset pm_attempt_getport pm_attempt_dump
pm_attempt_callit pm_bad_port rpc_call rpc_dialogue rpc_reply
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to
register a port for it or add a DPD payload signature.
.. zeek:id:: rpc_call
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 861 861
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, xid: :zeek:type:`count`, prog: :zeek:type:`count`, ver: :zeek:type:`count`, proc: :zeek:type:`count`, call_len: :zeek:type:`count`)
Generated for RPC *call* messages.
See `Wikipedia <https://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
about the ONC RPC protocol.
:param c: The connection.
:param xid: The transaction identifier allowing to match requests with replies.
:param prog: The remote program to call.
:param ver: The version of the remote program to call.
:param proc: The procedure of the remote program to call.
:param call_len: The size of the *call_body* PDU.
.. zeek:see:: rpc_dialogue rpc_reply dce_rpc_bind dce_rpc_message dce_rpc_request
dce_rpc_response rpc_timeout
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to add a
call to :zeek:see:`Analyzer::register_for_ports` or a DPD payload
signature.
.. zeek:id:: rpc_dialogue
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 833 833
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, prog: :zeek:type:`count`, ver: :zeek:type:`count`, proc: :zeek:type:`count`, status: :zeek:type:`rpc_status`, start_time: :zeek:type:`time`, call_len: :zeek:type:`count`, reply_len: :zeek:type:`count`)
Generated for RPC request/reply *pairs*. The RPC analyzer associates request
and reply by their transaction identifiers and raises this event once both
have been seen. If there's not a reply, this event will still be generated
eventually on timeout. In that case, *status* will be set to
:zeek:enum:`RPC_TIMEOUT`.
See `Wikipedia <https://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
about the ONC RPC protocol.
:param c: The connection.
:param prog: The remote program to call.
:param ver: The version of the remote program to call.
:param proc: The procedure of the remote program to call.
:param status: The status of the reply, which should be one of the index values of
:zeek:id:`RPC_status`.
:param start_time: The time when the *call* was seen.
:param call_len: The size of the *call_body* PDU.
:param reply_len: The size of the *reply_body* PDU.
.. zeek:see:: rpc_call rpc_reply dce_rpc_bind dce_rpc_message dce_rpc_request
dce_rpc_response rpc_timeout
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to add a
call to :zeek:see:`Analyzer::register_for_ports` or a DPD payload
signature.
.. zeek:id:: rpc_reply
:source-code: base/bif/plugins/Zeek_RPC.events.bif.zeek 886 886
:Type: :zeek:type:`event` (c: :zeek:type:`connection`, xid: :zeek:type:`count`, status: :zeek:type:`rpc_status`, reply_len: :zeek:type:`count`)
Generated for RPC *reply* messages.
See `Wikipedia <https://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
about the ONC RPC protocol.
:param c: The connection.
:param xid: The transaction identifier allowing to match requests with replies.
:param status: The status of the reply, which should be one of the index values of
:zeek:id:`RPC_status`.
:param reply_len: The size of the *reply_body* PDU.
.. zeek:see:: rpc_call rpc_dialogue dce_rpc_bind dce_rpc_message dce_rpc_request
dce_rpc_response rpc_timeout
.. todo:: Zeek's current default configuration does not activate the protocol
analyzer that generates this event; the corresponding script has not yet
been ported. To still enable this event, one needs to add a
call to :zeek:see:`Analyzer::register_for_ports` or a DPD payload
signature.
Reference in a new issue View git blame Copy permalink