Comment by jedberg

1. SSL. For a long time I didn't even know TLS was the "same thing", but even now that I know it is, I still say SSL 9 times out of 10.

2. 38 - Started working in 2011, but my first forays into network programming was in something like 2004-2005.

Looked over onto my other screen and sure enough the function I'd literally minutes before added an if statement to went

        public Builder sslCertNotBefore(Instant sslCertNotBefore) {
            if (sslCertNotBefore.isAfter(MAX_UNIX_TIMESTAMP)) {
                sslCertNotBefore = MAX_UNIX_TIMESTAMP;
            }
            this.sslCertNotBefore = sslCertNotBefore;
            return this;
        }

I think possibly part of the problem is that we as programmers typically don't deal with TLS directly. The code above is part of a system I wrote that extracts detailed certificate information from HTTPS connections, and man was it ever a hassle to wrestle all the information I was interested in out of the java standard library.

Sure on the one hand it's easier to not mess up if it's all automatic and out of sight, but at the same time, it's not exactly beneficial to the spread of deeper awareness of how TLS actually works when it's always such a black box.

I think most people call it SSL because they use OpenSSL library to deal with secure communication have SSL in their names. Openssl being the most dominant one). Other libraries are BoringSSL, LibreSSL, wolfSSL etc.

Libraries with TLS in their names are less frequently used

GnuTLS, mbedTLS, s2n-tls and RustTLS.

I usually say SSL, because it has a greater chance of being understood than the more correct TLS (nobody uses SSL 3.0 anymore). It's also in the name of many SSL (I mean, TLS) libraries, like the classic OpenSSL.

But yeah, I learned about SSL back in the crypto wars days of the 1990s, back when you had to pirate the so-called "US only" version of Netscape if you wanted decent SSL encryption, so I might be just using the old term out of habit.

I say "https" because sometimes even regular people know what that means.

These days I tend to say "TLS" more and more, but until just a year or two ago it was almost always "SSL". And "SSL" still slips out occasionally.

I'm 51, started working in IT in the mid 90's.

1. I say both somewhat 50/50. I say SSL instinctively, and TLS when I think about it and remember we don't say SSL anymore. It's been like that for around 10 years now, before that I'd only say SSL.

2. I started programming professionally in 1998 and I'm in my early 50s.

I say HTTPS certificate.

If I need to specifically say SSL or TLS, it's SSL (as in OpenSSL, LibreSSL, BoringSSL, SSL certificates, Qualys SSL Labs, SSL Server Test). TLS is a made up name for SSL.

I do say e.g. "TLSv1.2" if I need to name the specific protocol, that's about it.

I was working before 1999.

I always say HTTPS because in the context of my area of speciality, the details of how HTTPS works don't matter and neither do secure communication protocols besides HTTPS.

Reflex is to say SSL but usually correct myself to TLS. Started in IT in 2006 (was a nerd a few years before that though)

1) SSL, even though I know the difference. More accurately, I know there is a difference, but SSL gets the point across.

2) before 1999. IIRC, the first SSL certificate I was involved with getting required the use of a fax machine.

SSL, 27. I would call it `tls` in code, though (and maybe “SSL/TLS” in docs, for clarity).

(1) SSL

(2) 37. I've been an Internet user since ~1995 and been working in tech since 2004.

Nice try, targeted advertiser!

Mid 30s, SSL.

I work in cybersecurity and all the tools in the firewall/cert world still say "SSL decryption" and "SSL certificate". TLS is just a "major version" of SSL in my mind.

SSL - In my 40s, over 20 plus years.

When do I say TLS, when that one annoying guy joins the call that always corrects you. Everyone hates him, and he doesn’t care.

1. SSL

2. I’m old enough to remember 56-bit SSL encryption in browsers

TLS: Rolls off the tounge easier. Feels nicer in mouth. Easier to slur smoothly. Flows better on keyboard.

It's the ergonomic choice (;

1. SSL

2. I'm 56 and was active in computer clubs in the late 80s, no network, no hard drive, thousands of floppy's.

SSL, started computer science in 2010

SSL. Working as a sysadmin since 2010. It just feels more right to me, and honestly, it hasn’t been until recently that I’ve noticed more of a concerted effort to rebrand it to TLS — not sure if that’s just my perception or not.

Nobody ever says "TLS Certificate". It's only an "SSL Certificate". On that alone, it's just easier to stick to "SSL" for consistency and everyone knows what you mean.

SSL 42-started studying security in mid 90s as a teen started working 2000

TLS. 1989.

Even today, people and marketing pages promote "SSL" term. Unless you specifically google, "What is the deference between SSL and TLS?" most people would have no idea what TLS is.

I tell my developers to be compliant that they need to use TLS/SSL

1. SSL (probably https in that specific scenario)

2. Graduated and started in 2015.

To users: https

To devs: SSL

Did not start working before 1999. Started using Linux in 2003.

1. SSL 2. Started working in 2000, right on the boundary

1. Cloudflare could probably use my choice of the day as another source for their randomness.

2. Started my first IT job on a computer networking team in 2012.

I say TLS, and started working in the field in 1994.

1. TLS 2. 22. Started in 2024, but the SSL terminology is still widely used in the systems that I currently work with :p

TLS probably. 2004

I think the TLS v1.2 pushed me that way

SSL, started programming in maybe 2012. Possibly because of HTTPS or similarity with SSH.

Almost always ssl. Started professionally in 1999. But! mTLS is always mTLS

1. SSL

2. Started working before 1999

1. TLS

2. Started working after 1999

SSL. Started working in the mid 90's.

TLS (outside dealing with PG options named like sslmode)

No

SSL, born 1997

SSL. Started working around 2000.

1. SSL 2. 57

SSL, 40s