KNOWN ISSUES for V1.8.0
=======================

This file contains information about technical limitations and other known issues.


Technical Limitations:
----------------------

uaserver:

 - The generic encoder only supports ExtensionObjects with numeric TypeIds,
   which is normally always the case.

xml2c: The Code generator does not support the following features yet.

 - Opaque NodeIds

uaencoder:

 - The JSON non-reversible encoding does not support namespace indices other
   than 0 in the data (e.g. when encoding nodeids or qualified names).
 - In the JSON encoding only DatatypeIds are support as TypeIds for extension
   objects but not EncodingIds. This allows PubSub/MQTT use-cases but no
   client-server transport with JSON encoding like WebSockets.

mbedTLS:

  - The mbedTLS backend does not support exporting password encrypted
    private key files. Loading is supported, though.
    See https://github.com/Mbed-TLS/mbedtls/issues/1372
  - The mbedTLS backend does not support the usage of PKCS11 libraries
    for accessing crypto HW.
    See https://github.com/Mbed-TLS/mbedtls/issues/3006
    There are plans to replace this with the PSA interface in the future.

Mocana NanoCrypto:

 - This library is deprecated due to a lack of users.

Known issues:
-------------

* Compiler issues: With clang 3.5.0 the following warning occurs using string constants in strcmp and strsep:
  "warning: array index 2 is past the end of the array (which contains 2 elements) [-Warray-bounds]"
  Code example: 'strcmp(var, ".")'.

  This is a compiler bug, not a code issue!

  Occurrences:
  - src/platform/file.c:461
  - src/platform/file.c:462
  - src/uabase/variant.c:1341
  - src/config/config_loader.c:92
  - src/uafileformat/file_writer.c:394
  - src/uafileformat/file_writer.c:411

  This happens with "clang version 3.5.0-10 (tags/RELEASE_350/final)" on Debian 8 (Jessie),
  it is fixed with "clang version 3.8.1-24 (tags/RELEASE_381/final)" on Debian 9 (Stretch).

  This could also be a ccache problem according to this:
  https://bugzilla.redhat.com/show_bug.cgi?id=1350086

* Static Address Spaces are not supported for MS Visual Studio before VS2015.
  This is due to missing C99 support in older VS versions. The generated address
  space tables require designated initializers. Note that VS2013 claims to
  support it, but the implementation is buggy and will not work as expected.

* PubSub issues:

  - Permission checks on GetSecurityKeys and SetSecurityKeys use only default checks
    but do not handle special cases required for specification compliance