wireshark/plugins/opcua
Kovarththanan Rajaratnam 2547ce21bf We no longer support the old plugin API so remove it completely from the build system
svn path=/trunk/; revision=29821
2009-09-09 14:01:57 +00:00
..
AUTHORS
COPYING
ChangeLog From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
Doxyfile
Makefile.am Allow checkapis target to work in out-of-tree builds (s#../../#$(top_srcdir)). 2008-07-29 22:06:37 +00:00
Makefile.common Add missing header file of OpcUa plugin update. 2009-04-06 20:29:01 +00:00
Makefile.nmake We no longer support the old plugin API so remove it completely from the build system 2009-09-09 14:01:57 +00:00
README From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
moduleinfo.h From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
moduleinfo.nmake From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
opcua.c Check our array lengths and refuse to process them if they're too large. 2009-09-09 00:18:15 +00:00
opcua_application_layer.c From Kovarththanan Rajaratnam: 2009-06-22 18:23:58 +00:00
opcua_application_layer.h
opcua_complextypeparser.c From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
opcua_complextypeparser.h Trivial warning fixes: 2009-06-15 02:34:53 +00:00
opcua_enumparser.c From Kovarththanan Rajaratnam: 2009-06-22 18:23:58 +00:00
opcua_enumparser.h From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
opcua_hfindeces.c From Kovarththanan Rajaratnam: 2009-06-22 18:23:58 +00:00
opcua_hfindeces.h From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
opcua_identifiers.h From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
opcua_security_layer.c From Kovarththanan Rajaratnam: 2009-06-22 18:23:58 +00:00
opcua_security_layer.h
opcua_serviceids.h Add missing header file of OpcUa plugin update. 2009-04-06 20:29:01 +00:00
opcua_serviceparser.c From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
opcua_serviceparser.h Trivial warning fixes: 2009-06-15 02:34:53 +00:00
opcua_servicetable.c From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
opcua_simpletypes.c Check our array lengths and refuse to process them if they're too large. 2009-09-09 00:18:15 +00:00
opcua_simpletypes.h
opcua_transport_layer.c Check our array lengths and refuse to process them if they're too large. 2009-09-09 00:18:15 +00:00
opcua_transport_layer.h From Gerhard Gappmeier: 2009-04-06 18:30:04 +00:00
plugin.rc.in Remove the pre-release flag from FILEFLAGS in the resource file. 2008-03-29 23:04:33 +00:00

README

OpcUa Plugin:
=============

This plugin implements the dissection of the OpcUa Binary Protocol.
Author: Gerhard Gappmeier
        ascolab GmbH
        http://www.ascolab.com
	
Overview:
=========

OpcUa (OPC Unified Architecture) is a vendor and platform independent
protocol for automation technology. It is the successor of the
COM/DCOM based specifications OPC DA, OPC Alarm & Events, OPC HDA, etc.
It unifies all this technologies into a single protocol.

The specification describes abstract services that are independent
of the underlying protocol. For now there exist protocol mappings
to a Binary TCP based protocol and a SOAP based Webservice.
Also a hybrid version will be available where the Binary messages are transported
by a single webservice command called "Invoke".

More information about the technology you can find on
http://www.ascolab.com/index.php?file=ua&lang=en.

Protocol Mappings:
==================

Binary (TCP): The fastest and most flexible version (small footprint, no XML and SOAP necessary)
              can easily be tunneled (SSH, IPSEC, etc.), redirected, ...
SOAP version: Easy to implement with verious tools like .Net, JAVA, gSOAP, etc.
              Better to communicate through firewalls via HTTP.
SOAP with Binary Attchment: Combines the advantages of both.
              The messages are encoded as Binary, and transported via SOAP as binary
              attachment.

The OPC Foundation offers a free Opc Ua stack implementation in ANSI C
for all members. This stack implements the binary protocol as well
as the SOAP version. It's easily portable to different kinds of operating
systems from embedded devices to servers.
This makes it easy to implement Opc Ua applications based on this stack
and it is expected that the binary protocol will be the most used
protocol.
Nevertheless it's free to everbody to implement an own stack according
to the specification. An own implementation of the SOAP version 
should be easy with the various SOAP toolkits.

For more information see http://www.opcfoundation.org

Known limitations:
==================

* Only the security policy http://opcfoundation.org/UA/SecurityPolicy#None is supported,
  which means the encryption and signing is turned off.