)]}'
{
  "commit": "139ebb3128d0a38e6ad47a326d7cf1536fb53984",
  "tree": "66e9130e1a9b8b11719e72c847901de1f7e4de80",
  "parents": [
    "fe1ff7f973ff3c30514416f56dce54046ecce9ff"
  ],
  "author": {
    "name": "Robert Lubos",
    "email": "robert.lubos@nordicsemi.no",
    "time": "Wed Oct 15 14:34:15 2025 +0200"
  },
  "committer": {
    "name": "Anas Nashif",
    "email": "anas.nashif@intel.com",
    "time": "Mon Oct 20 11:26:26 2025 -0400"
  },
  "message": "net: sockets: tls: Validate credentials when registering on a socket\n\nSo far the TLS/DTLS credentials would only be validated upon first use,\ni. e. when TLS/DTLS handshake was initiated. This could lead to some\nconfusion, especially when trying to understand the reason of the\nhandshake failure, as it wasn\u0027t clear whether the handshake failed due\nto peer sending bad certificate or due to local configuration issues.\n\nThis commit attempts to improve this, by pre-validating the credentials\nas soon as they are configured on a socket with TLS_SEC_TAG_LIST socket\noption. That way, in case bad credentials are configured on a socket, or\nmore commonly, mbed TLS is misconfigured to handle certain credential\ntype, it will be caught early during socket configuration, instead of\nduring the handshake.\n\nSigned-off-by: Robert Lubos \u003crobert.lubos@nordicsemi.no\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6f4919dc99e72c3960e3df593fe4ae240639ca8d",
      "old_mode": 33188,
      "old_path": "subsys/net/lib/sockets/sockets_tls.c",
      "new_id": "695af671646852594c5fe4a09e80f7179071f385",
      "new_mode": 33188,
      "new_path": "subsys/net/lib/sockets/sockets_tls.c"
    }
  ]
}