Importance of OpenSSL (part 1)

If you're using a modern desktop (laptop , too) computer that's not running OpenBSD or some obscure form of Linux, then your computer most likely comes with 'openssl' packaged by default.

*'What is open OpenSSL?'*

OpenSSL is a software is a software package, written in 'C', that contains an expansive suite of cryptographic ciphers, digests, encryption mechanisms, and other commands that utilize or interact with cryptography in some facet.

Its most common usage is enabling the processing of various cryptographic primitives in our browser (that we may not pay attention to), such as:

A) Assessing whether a website has a 'secure' certificate or not [this is what enables your browser to assess website certificates + your SSL connection strength to other sites; which is an extremely important process for users & general user security]

B) Connecting & establishing a secure connection with various websites (with any level of cryptographic strength at all) ; this is a critical facet of the 'handshake' process that's classically included in TLS

C) Running any sort of cryptographic operation on our computers for things such as storing user passwords / generating or verifying checksums / etc.

D) This goes w/o saying (probably) - but if you're a blockchain user and you're using software that generates your wallet's keys client side (which it absolutely should be), then it is more than likely that openssl is interfaced in order to process and compute the cryptographic operations necessary there as well

—

There are obviously several other very noteworthy and critical crypto libraries, such as:

1. 'WebCrypto API' = Comes pre-packaged in Firefox + Chrome. is meant to provide capability for performing cryptographic operations in the browser (client side) ; this is part of what makes such a thing possible. Well written web apps will insert functions that are designed to call upon this functionality in one's browser in order to generate / utilize / utilize data provided or extracted from certain cryptographic operations that logic dictates should not be performed server side.

2. GPG = GPG comes equipped with its own library. It also benefits from (a solid explanation of its cryptographic properties is broken down here: https://hashrocket.com/blog/posts/encryption-with-gpg-a-story-really-a-tutorial) ; there are certain complementary cryptographic libraries that can be utilized by gpg via API though, such as:
a.) 'libgcrypt' (url = https://gnupg.org/software/libgcrypt/index.html)

b.) 'ntbtls' (url =https://gnupg.org/software/ntbtls/index.html)

there are other popular implementations listed on GnuPG's actual website, which users can look up at their leisure.

LibreCryptography

Importance of OpenSSL (part 1)

If you're using a modern desktop (laptop , too) computer that's not running OpenBSD or some obscure form of Linux, then your computer most likely comes with 'openssl' packaged by default.

*'What is open OpenSSL?'*

OpenSSL is a software is a software package, written in 'C', that contains an expansive suite of cryptographic ciphers, digests, encryption mechanisms, and other commands that utilize or interact with cryptography in some facet.

Its most common usage is enabling the processing of various cryptographic primitives in our browser (that we may not pay attention to), such as:

A) Assessing whether a website has a 'secure' certificate or not [this is what enables your browser to assess website certificates + your SSL connection strength to other sites; which is an extremely important process for users & general user security]

B) Connecting & establishing a secure connection with various websites (with any level of cryptographic strength at all) ; this is a critical facet of the 'handshake' process that's classically included in TLS

C) Running any sort of cryptographic operation on our computers for things such as storing user passwords / generating or verifying checksums / etc.

D) This goes w/o saying (probably) - but if you're a blockchain user and you're using software that generates your wallet's keys client side (which it absolutely should be), then it is more than likely that openssl is interfaced in order to process and compute the cryptographic operations necessary there as well

—

There are obviously several other very noteworthy and critical crypto libraries, such as:

1. 'WebCrypto API' = Comes pre-packaged in Firefox + Chrome. is meant to provide capability for performing cryptographic operations in the browser (client side) ; this is part of what makes such a thing possible. Well written web apps will insert functions that are designed to call upon this functionality in one's browser in order to generate / utilize / utilize data provided or extracted from certain cryptographic operations that logic dictates should not be performed server side.

2. GPG = GPG comes equipped with its own library. It also benefits from (a solid explanation of its cryptographic properties is broken down here: https://hashrocket.com/blog/posts/encryption-with-gpg-a-story-really-a-tutorial) ; there are certain complementary cryptographic libraries that can be utilized by gpg via API though, such as:
a.) 'libgcrypt' (url = https://gnupg.org/software/libgcrypt/index.html)

b.) 'ntbtls' (url =https://gnupg.org/software/ntbtls/index.html)

there are other popular implementations listed on GnuPG's actual website, which users can look up at their leisure.

Hashrocket

Encryption with gpg, a story (really, a tutorial)

GPG is a compatible replacement of PGP. That, in and of itself, is confusing.

hottg.com/librecryptography/138

106 viewsApr 27, 2020 at 20:16