Admin... by accident!

You may have chosen to be an admin. I didn't!

  • Home
  • FreeBSD
  • GNU/Linux
  • Security
  • Network
  • Virtualization
  • Politics
  • Github
  • Donate
  • Me

A brief introduction to SSL/TLS certificates

April 26, 2017 by Albert Valbuena

SSL stands for Secure Sockets Layer and it an old implementation of a crytographic protocol. TLS, or Transport Layer Security, is a new one. They are both used to have privacy in the communications between different parties. They are used to secure email, web browsing, instant messaging, etc

These protocols work in a complex way for me to describe in just a few lines and be accurate. All I can say is any communication there are two parties involved, sever and client (your website and someone else’s computer), happens in a private manner. This privacy is achieved by encrypting the communications making the channel secure. The cryptography is provided by complex mathematic algorithms so even if someone captures the communication between the two ends it will be very difficult, or even impossible, to see the content in it.

“But… come on! I just plan to have a small website, nothing big, I am not building a bank. I don’t really need this.”

This is what your brain is actually telling you right now. Don’t listen to it. Listen to me. If you just plan to have a website where the only user login in will be you, just skip this chapter and anything related to SSL/TLS appearing in this guide. However the possibility you are planning to have a site where some users will log in is beyond the plausible. Almost everyone building a website is planning to have users who will have profiles, who will share or build content, who will upload pictures, or something. If you need a log in SSL/TLS is at the time of writing very recommendable. In the near future, just a few months from now Google will mark any website with a login capability as insecure if that login is not performed using an SSL/TLS connection.

There are options for this and since the sign of times seems to be embracing crypto communications, it will become inevitable. Event though this may seem silly at some point. The crypto communication creates overhead and processing all this takes away speed and performance from the sites. Sniffing a username and a password from some forum or dark site on the internet also means someone is in the middle of that communication. The real problem is someone is wiretapping the ISP, the web server, your router, or your computer. Crypto solves one problem. If you look at the big picture though, it solves just a portion of it. The real problem may not be just plain text after all.

If you find the articles in Adminbyaccident.com useful to you, please consider making a donation.

Use this link to get $200 credit at DigitalOcean and support Adminbyaccident.com costs.

Get $100 credit for free at Vultr using this link and support Adminbyaccident.com costs.

Mind Vultr supports FreeBSD on their VPS offer.

 

Filed Under: FreeBSD, GNU/Linux, Security

Recent Posts

  • How to install Redis for WordPress on FreeBSD
  • How to compile cloudflared in FreeBSD 13/14
  • How to configure FreeBSD to use a webcam (version 12 and 13)
  • Symbolic and Hard Links in UNIX and Linux
  • How to import iocage jails to Bastille on FreeBSD 13
  • How to load and unload kernel modules in Linux
  • How to use find in GNU/Linux and FreeBSD
  • How to install Mate on FreeBSD 12/13
  • How to install Nessus 10 on FreeBSD 12
  • How to enable TLS traffic from the origin server on Cloudflare Argo Tunnel
  • How to use Cloudflare’s Argo Tunnel service to publish a website on FreeBSD 12/13
  • How to setup MariaDB master-slave replication on FreeBSD
  • How to upload a FreeBSD custom image on DigitalOcean
  • How to install Drupal 9 on FreeBSD 13.0
  • How to manage site visitors based on IP Geolocation
  • How to enable Geolocation in AWStats on FreeBSD 13.0
  • How to install AWStats on FreeBSD 13.0
  • How to configure Modsecurity 3 for WordPress on FreeBSD
  • How to configure Apache HTTP with a TLS reverse proxy backend on FreeBSD
  • How to detect a WAF – Web Application Firewall

Archives

  • November 2024
  • October 2024
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • February 2023
  • January 2023
  • December 2022
  • April 2022
  • March 2022
  • October 2021
  • September 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • September 2018
  • June 2018
  • May 2018
  • April 2018
  • February 2018
  • January 2018
  • November 2017
  • April 2017

RSS Admin… by accident!

  • How to install Redis for WordPress on FreeBSD
  • How to compile cloudflared in FreeBSD 13/14
  • How to configure FreeBSD to use a webcam (version 12 and 13)
  • Symbolic and Hard Links in UNIX and Linux
  • How to import iocage jails to Bastille on FreeBSD 13
  • How to load and unload kernel modules in Linux
  • How to use find in GNU/Linux and FreeBSD
  • How to install Mate on FreeBSD 12/13
  • How to install Nessus 10 on FreeBSD 12
  • How to enable TLS traffic from the origin server on Cloudflare Argo Tunnel

Copyright © 2025 · Magazine Pro Theme on Genesis Framework · WordPress · Log in