> For the complete documentation index, see [llms.txt](https://dev.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ishare.eu/version-3.0/introduction/specific-technical-standards/tls.md).

# TLS

HTTP communication within iSHARE is encrypted using TLS versions up to their end of life (EOL). Currently, this means TLS 1.2 or 1.3.

On this page, a brief description of TLS is provided. For the most recent version of the specification, click on [this link](https://tools.ietf.org/html/rfc5246).

### Description <a href="#tls-description" id="tls-description"></a>

Transport Layer Security (TLS) is a cryptographic protocol that describes communication security for computer networks. The first version of TLS 1.0 is built upon and is an upgrade of SSL 3.0 (Secure Sockets Layer).

### Differences and similarities between TLS and SSL <a href="#tls-differencesandsimilaritiesbetweentlsandssl" id="tls-differencesandsimilaritiesbetweentlsandssl"></a>

Both TLS and SSL provide means for data encryption and authentication between applications, machines and servers when data is sent through an insecure network.

The differences between TLS and its forerunner, Secure Sockets Layer (SSL), are the addressed vulnerabilities. TLS, for instance, works with

* a wider variety of hash functions.
* more secure and stronger cypher suites, such as the Advanced Encryption Standard (AES) cypher suites, which are integrated into TLS version 1.1.
* browser security warnings. TLS has more alert descriptions than SSL.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dev.ishare.eu/version-3.0/introduction/specific-technical-standards/tls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.