Spanish Translation of Node.js (Part 7) (1180 words)

Node.js It is an open source execution environment for developing web applications. It is an environment in which you can run a program written in JavaScript.

What is it for?
Node.js lights in real-time web applications employing push technology over web sockets. Node.js allows having web applications with real-time, two-way connections, where both, the client and server can initiate communication, allowing them free data exchange. It can handle many concurrent connections at a time. It is built on Chrome’s V8 JavaScript engine and uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. Node.js now plays a critical role in the technology stack of many high-profile companies who depend on its unique benefits.
SOURCE 1
SOURCE 2

Contribution Specifications

Node.js is currently being translated into 33 languages and I am contributing to translate it into Spanish. 55% of the whole the project has been translated.

So far I have translated:

Over this translation I continued translating TLS.md file. I have translated more than 80% of the total file.

Transport layer security (TLS) is a protocol that provides communication security between client/server applications that communicate with each other over the Internet. It enables privacy, integrity and protection for the data that is transmitted between different nodes on the Internet. TLS is a successor to the secure socket layer (SSL) protocol.

Few examples of some strings that mention the value of TLS:

ENGLISH: <0>sessionId</0> - The TLS session identifier

SPANISH: <0>sessionId</0> - El identificador de sesión TLS

ENGLISH: [<0>tls.createServer()</0>][] uses a 128 bit truncated SHA1 hash value
generated from <0>process.argv</0> as the default value of the <0>sessionIdContext</0>
option, other APIs that create secure contexts have no default value.

SPANISH: [<0>tls.createServer()</0>][] utiliza un valor de hash SHA1 truncado de 128 bits generado a partir de <0>process.argv</0> como el valor predeterminado de la opción<0>sessionIdContext</0>, otras API que crean contextos seguros no tienen valor predeterminado.

ENGLISH: If these clients <0>must</0> be supported, the
<1>TLS recommendations</1> may offer a compatible cipher suite.

SPANISH: Si estos clientes <0>deben</0> ser soportados, las <1>recomendaciones de TLS</1> pueden ofrecer un conjunto de cifrado compatible.

This time I learnet two new concepts:

1. ALPN or Application-Layer Protocol Negotiation
What Is ALPN?
It is a TLS (Transport Layer Security) extension that includes the protocol negotiation within the exchange of hello messages. ALPN is able to negotiate which protocol should be handled over a secure connection in a way that is more efficient and avoids additional round trips. The ever-growing in popularity HTTP/2 protocol, makes use of ALPN to further decrease website load times and encrypt connections faster.

How Does ALPN Work?
With ALPN the client will send a list of supported application protocols to the server as part of the TLS ClientHello message. The server then selects a protocol and sends back that protocol in its ServerHello message. The application protocol negotiation can, therefore, be accomplished over one single round trip within the TLS handshake. This method also allows the server to associate a different certificate with each application protocol.

[SOURCE](https://www.keycdn.com/support/alpn)

2. CA or Certificate authority
Certificate Authorities, or Certificate Authorities / CAs, issue Digital Certificates. Digital Certificates are verifiable small data files that contain identity credentials to help websites, people, and devices represent their authentic online identity (authentic because the CA has verified the identity). CAs play a critical role in how the Internet operates and how transparent, trusted transactions can take place online. CAs issue millions of Digital Certificates each year, and these certificates are used to protect information, encrypt billions of transactions, and enable secure communication.
SOURCE

Languages
• Source Language: English
• Translated Language: Spanish

Word Count
Words translated on this contribution: 1180 words. This contribution was made between the 20th and the 22nd of March 2019.

1st contribution
2nd contribution
3rd contribution
4th contribution
5th contribution
6th contribution
Proof of Authorship
The translation was submitted via Crowdin. All relevant information on the following links.
Node.js Crowdin page
My Crowdin Profile
My Crowdin Activity

Examples of my translations