Repository:
https://github.com/nodejs/i18n
Project Details:
Nod.js is one of the best opportunities and experiences developers can have when using Java environments since it gives them the needed tools to use Java coding tasks on an operating system within their computer. Node.js represents a valuable instrument for designing, testing applications and customizing them to developers and business needs. Node.js provides users all the tools they need to make the most of the great number of features JavaScript offers.
Node.js environment improves users’ pcs performance through multiple resources for troubleshooting and processes optimizers. Moreover, it encourages developers to learn alternative routes for completing tasks and for ideating enhanced ways to achieve their goals y using this Java application.
Contribution Specifications:
Translation Overview:
This time, as I stated in my previous post, I continue talking about Crypto.
As it was stated previously, this module of cryptographic functionality that encrypts data by implementing certain certificates such as Cipher and SPKAC works through a compilation of Node.js’ data certificates, such as OpenSSL's hash, HMAC, cipher, decipher, sign, among others.
This module promotes the use of certificates that helps to handle an output generated by the HTML5, whose structures include a public key and a challenge, to implement internally Node.js operations. These certificates are SPKAC, Cipher, Decipher and, DiffieHellman. All of them work together to encrypt of decrypt readable and writable data within the module Crypto on this way: On the one hand, Spkac is the milestone Node.js uses as the OpenSSL SPKAC implementation to internally support its own operations it helps to encrypt data; on the other, Cipher encrypts algorithms and inputs data in the appropriate block size; *Decipher decrypts readable and writable data when plain encrypted data is written to produce unencrypted data on the readable side; and, finally, the DiffieHellman creates public keys and challenges that Crypto uses to exchange with other modules or to turn them into buffers or strings.
The Diffie–Hellman key exchange (DH), which was tmostly the certificate translated, is a method of securely exchanging cryptographic keys over a public channel. Indeed, it is one of the earliest practical examples of public key exchange implemented within the field of cryptography.
For this compilation it was required more documentation since the understanding of the DiffieHellman algorithm and protocol can be complex when you are not related to it. As it is indicated in the Wikipedia website,
“The simplest and the original implementation of the protocol uses the multiplicative group of integers modulo p, where p is prime, and g is a primitive root modulo p. These two values are chosen in this way to ensure that the resulting shared secret can take on any value from 1 to p–1.”
“The Diffie–Hellman key exchange method allows two parties that have no prior knowledge of each other to jointly establish a shared secret key over an insecure channel. This key can then be used to encrypt subsequent communications using a symmetric key cipher. (…) [It] secure[s] encrypted communication between two parties required that they first exchange keys by some secure physical channel, such as paper key lists transported by a trusted courier.”
“Diffie–Hellman key exchange establishes a shared secret between two parties that can be used for secret communication for exchanging data over a public network.”
“The process begins by having the two parties, Alice and Bob, agree on an arbitrary starting color that does not need to be kept secret (but should be different every time (…).The crucial part of the process is that Alice and Bob each mix their own secret color together with their mutually shared color, resulting in orange-tan and light-blue mixtures respectively, and then publicly exchange the two mixed colors. Finally, each of the two mixes the color he or she received from the partner with his or her own private color. The result is a final color mixture that is identical to the partner's final color mixture."
"If a third party listened to the exchange, it would be computationally difficult for this party to determine the secret colors.”
(https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange)
The translation of this module has been different since the documentation is addressed to the scientific and specified translation in the programming and informatic field. Hence, it has been necessary to sped more time reading and searching information that allow the proper understanding of the content of the text. It is a complete challenge.
In the next post, Crypto will be continued. It is a long text with interesting information for developers and interested ones in the use of this Node.js module. Keep tuned!
As they’re seen in the three texts, the following examples show parts of the nature of the document:
Example #1:
English:
The <0>DiffieHellman</0> class is a utility for creating Diffie-Hellman key exchanges.
Spanish:
La clase <0>DiffieHellman</0> es útil para crear intercambios en la clave Diffie-Hellman.Example #2:
English:
Computes the shared secret using <0>other_public_key</0> as the other party's public key and returns the computed shared secret.Spanish:
Computa el secreto compartido usando <0>otherPublicKey</0> como la clave pública de la otra parte y devuelve el secreto compartido computado.Example #3:
English:
If <0>output_encoding</0> is given a string is returned; otherwise, a [<0>Buffer</0>][] is returned.Spanish:
Una string es devuelta si el <0>outputEncoding</0> es dado; de no ser así, un [<0>Buffer</0>][] es devuelto.
Languages:
This translation was from English to Spanish.
I am a translator in Spanish, English and French. I also work as an English and Spanish teacher as a second or foreign language. I have worked with technical translations in different topics being this one interesting due to the technical terms and use when translating.
Word Count:
Words translated were: 1043.
Total amount words translated in this project: 5581
Pervious Contributions to this Project:
- Contribution n. 1: Domain.md, published on September 19th.
- Contribution n. 2: Debugger.md, published on October 7th.
- Contribution n. 3: Maintaining npm.md, Debugger.md, and Punycode.md, published on October 20th.
- Contribution n. 4: Crypto.md, published on October 23rd.
Proof of Authorship:
Proof of authorship is verifiable by clicking in my Crowdin profile, especially in my contribution by checking my activity, and in the translated text Crypto.
