Hello, this is my 39th open source contribution for Utopian and DaVinci as translator. I have been translating different Node.js Files during the past few months.I started translating the "TLS" file, which is very interesting and has a lot of new information that could be useful for those who will start working with Node.js. This file is about security and cipher.
I work with an extensive team of translators team whose performance has been excellent. By this time a 48% of this huge project has been translated in just a few months; I think we are working very fast!
I invite you to read this translation report for more information about this interesting file. Also, you can read my previous reports to have much more information about all of the files I've translated. If you like technology, programming and development, this is a post that you will be interested in.
Repository
https://github.com/nodejs/i18n
Project Details
Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside of a browser. It lets developers use JavaScript to write Command Line tools and for server-side scripting to produce dynamic web page content before the page is sent to the user's web browser. Consequently, Node.js represents a "JavaScript everywhere" paradigm,[6] unifying web application development around a single programming language, rather than different languages for server side and client side scripts.
It looks difficult to understand at first, but let me explain it with the next example.
Imagine that you have been developing a new android app that uses the APIs from Google Maps and Twitter. When testing the app, you realize that both APIs are written in different languages and you must change one of them to make it work, but that's a lot of work and goes against the reasons to use an API. Node.js is the solution to problems like this because it allows the union between different programming languages without affecting its performance.
I decided to translate this project because I'm an engineering student and innovation is my passion; I love creating solutions to problems like this. Also, I like sharing information and a way to do it is translating the content of a big project like this so people around the world can access to it and share it too.
Contribution Specifications
- Translation Overview
This part of the TLS file is about security and cipher, which are very important implementations that take care of all the developer's work. I must say that, as Node.js is a process, there can be some programs that consist on client and server architecture, it means that exists communication between two or more peers. This kind of communication is naturally insecure and that's the reason why Node.js needs cipher on its messages.
TLS is a module that "provides an implementation of the Transport Layer Security (TLS) and Secure Socket Layer (SSL) protocols that is built on top of OpenSSL.". Those protocols work together to create a public/private key infrastructure that provides security. Every server needs a certificate that is a public key that corresponds to a private key; certificates also have the signature of a Certificate Authority.
These are the general concepts that we must know about TLS/SSL in Node.js. Once we understand all these concepts, we can advance and explain some methods involved in this huge and important module.
- Language
The original language of this change log is English and it was translated into Spanish, which is my native language. I have experience translating in projects like Loopring wallet and Yapbam. These projects make me grow and learn a lot about open source projects.
English
Certificates are <0>public keys</0> that correspond to a private key, and that are digitally signed either by a Certificate Authority or by the owner of the private key (such certificates are referred to as "self-signed").
Spanish
Los certificados son <0>claves públicas</0> que corresponden a una clave privada, y que están firmadas digitalmente por una Autoridad de Certificación o por el propietario de la clave privada (dichos certificados están referidos como "auto-firmados").
English
Creating a self-signed certificate using the OpenSSL command-line interface is illustrated in the example below:
Spanish
La creación de un certificado auto-firmado utilizando la interfaz de línea de comandos de OpenSSL se ilustra en el siguiente ejemplo:
English
Practically, this means that even if the server's private key is compromised, communication can only be decrypted by eavesdroppers if the attacker manages to obtain the key-pair specifically generated for the session.
Spanish
En la práctica, esto significa que incluso si la clave privada del servidor está comprometida, la comunicación solo puede ser descifrada por intrusos si el atacante logra obtener el par de claves generadas específicamente para la sesión.
English
ALPN (Application-Layer Protocol Negotiation Extension), NPN (Next Protocol Negotiation) and, SNI (Server Name Indication) are TLS handshake extensions:
Spanish
ALPN (Extensión de Negociación del Protocolo de Capa de Aplicación), NPN (Próxima Negociación de Protocolo) y SNI (Indicación de Nombre de Servidor) son extensiones del establecimiento de comunicación de TLS:
- Word Count
In Crowdin reports, there are 1183 translated words. Nonetheless, some of them are non-translatable, so the translation consist on 1033 words.
Proof of Authorship
You can visit my profile (navx) on Crowdin's website to find proof of authorship. Also, you can visit the Activity tab in the Node.js project and filter my contributions between January 17th and January 19th, which were the dates of the translation and the corrections respectively.
The next link, redirect to my crowdin profile:
https://crowdin.com/profile/navx