2634: Red Line Through HTTPS - Revision history

Beret: /* Explanation */

2024-09-17T23:59:10Z

‎Explanation

Beret: /* Explanation */ Grammar

2024-09-17T23:58:48Z

‎Explanation: Grammar

172.71.178.51: /* Explanation */ Expand on what can cause “insecure” https

2023-07-07T18:44:32Z

‎Explanation: Expand on what can cause “insecure” https

172.69.22.119 at 07:06, 23 March 2023

2023-03-23T07:06:09Z

Beret: Removed incomplete tag

2022-11-26T04:50:41Z

Removed incomplete tag

Kynde: /* Explanation */ Added a bit in from the original explanation. But agree there was a lot of over explanation

2022-11-19T15:45:04Z

‎Explanation: Added a bit in from the original explanation. But agree there was a lot of over explanation

Beret: /* Explanation */ added incomplete tag

2022-11-19T08:22:50Z

‎Explanation: added incomplete tag

Beret: /* Explanation */ I redid the entire explanation. It was too much. It was very badly written. I'll accept any corrections to errors I have made here, but please do not revert this page to the state I found it in.

2022-11-19T08:20:52Z

‎Explanation: I redid the entire explanation. It was too much. It was very badly written. I'll accept any corrections to errors I have made here, but please do not revert this page to the state I found it in.

172.69.33.207: /* Explanation */ done

2022-08-24T20:17:30Z

‎Explanation: done

172.70.135.120: /* Explanation */ i dont have any but there should be exactly because i dont right?

2022-06-21T01:39:27Z

‎Explanation: i dont have any but there should be exactly because i dont right?

@@ Line 9: / Line 9: @@
 ==Explanation==
-This comic pokes fun at the lack of security implied by an unverified {{w|https}} connection as implied by the "red line through  (<span style="color:red"><s>https</s></span>)". https is an extension to the http protocol which (among other things) verifies that the server owns the domain name. “Insecure” https is usually caused by invalid TLS certificates, which can be an indication that an attacker is intercepting the connection (the attacker doesn’t have access to the certificates). However reasons for “insecure” https are often benign.
+This comic pokes fun at the lack of security implied by an unverified {{w|https}} connection as implied by the "red line through  (<span style="color:red"><s>https</s></span>)". https is an extension to the http protocol which (among other things) verifies that the server owns the domain name. “Insecure” https is usually caused by invalid TLS certificates, which can be an indication that an attacker is intercepting the connection (the attacker doesn’t have access to the certificates). However reasons for “insecure” https are often benign:
 * The certificates expired, and the site maintainers have not asked for new certificates.

@@ Line 9: / Line 9: @@
 ==Explanation==
-This comic pokes fun at the lack of security implied by an unverified {{w|https}} connection as implied by the "red line through  (<span style="color:red"><s>https</s></span>)". https is an extension to the http protocol which (among other things) verifies that the server owns the domain name. “Insecure” https is usually caused by invalid TLS certificates, which can be an indication that an attacker is intercepting the connection (the attacker doesn’t have access to the certificates). However reasons for “insecure” https are often caused by benign reasons:
+This comic pokes fun at the lack of security implied by an unverified {{w|https}} connection as implied by the "red line through  (<span style="color:red"><s>https</s></span>)". https is an extension to the http protocol which (among other things) verifies that the server owns the domain name. “Insecure” https is usually caused by invalid TLS certificates, which can be an indication that an attacker is intercepting the connection (the attacker doesn’t have access to the certificates). However reasons for “insecure” https are often benign.
 * The certificates expired, and the site maintainers have not asked for new certificates.

@@ Line 9: / Line 9: @@
 ==Explanation==
-This comic pokes fun at the lack of security implied by a poor {{w|https}} connection as implied by the "red line through  (<span style="color:red"><s>https</s></span>)". The red line is supposed to be a clear warning to the user that the connection is not secure, and that anything about the site, or that you send to the site (like passwords) may be observed or modified in transit by anyone.
+This comic pokes fun at the lack of security implied by an unverified {{w|https}} connection as implied by the "red line through  (<span style="color:red"><s>https</s></span>)". https is an extension to the http protocol which (among other things) verifies that the server owns the domain name. “Insecure” https is usually caused by invalid TLS certificates, which can be an indication that an attacker is intercepting the connection (the attacker doesn’t have access to the certificates). However reasons for “insecure” https are often caused by benign reasons:
 Although a lack of the https protocol in a web process does allow for third party tampering and deception, it also implies that the site is rather old; and, if it has been maintained for this long, it is probably not malicious, as most malicious sites are either reported and taken down or allowed to become defunct by their operators after a short amount of time.
 The title text essentially explains the joke, noting that maintaining a website costs money and that there are regulatory agencies responsible for taking down sketchy domains, and so if a website is still up despite these obstacles, it is probably trustworthy.

← Older revision		Revision as of 07:06, 23 March 2023
Line 16:		Line 16:

	The title text essentially explains the joke, noting that maintaining a website costs money and that there are regulatory agencies responsible for taking down sketchy domains, and so if a website is still up despite these obstacles, it is probably trustworthy.		The title text essentially explains the joke, noting that maintaining a website costs money and that there are regulatory agencies responsible for taking down sketchy domains, and so if a website is still up despite these obstacles, it is probably trustworthy.
		+
		+	A similar question was asked on [[1256: Questions]].

	==Transcript==		==Transcript==

← Older revision		Revision as of 04:50, 26 November 2022
Line 8:		Line 8:

	==Explanation==		==Explanation==
−	~~{{incomplete\| Needs to be more thoroughly explained, but not TOO thoroughly for the love of god!}}~~

	This comic pokes fun at the lack of security implied by a poor {{w\|https}} connection as implied by the "red line through (<span style="color:red"><s>https</s></span>)". The red line is supposed to be a clear warning to the user that the connection is not secure, and that anything about the site, or that you send to the site (like passwords) may be observed or modified in transit by anyone.		This comic pokes fun at the lack of security implied by a poor {{w\|https}} connection as implied by the "red line through (<span style="color:red"><s>https</s></span>)". The red line is supposed to be a clear warning to the user that the connection is not secure, and that anything about the site, or that you send to the site (like passwords) may be observed or modified in transit by anyone.

@@ Line 10: / Line 10: @@
 {{incomplete| Needs to be more thoroughly explained, but not TOO thoroughly for the love of god!}}
-This comic pokes fun at the lack of security implied by a poor {{w|https}} connection as implied by the "red line through https". Although a lack of the https protocol in a web process does allow for third party tampering and deception, it also implies that the site is rather old; and, if it has been maintained for this long, it is probably not malicious, as most malicious sites are either reported and taken down or allowed to become defunct by their operators after a short amount of time.
+This comic pokes fun at the lack of security implied by a poor {{w|https}} connection as implied by the "red line through  (<span style="color:red"><s>https</s></span>)". The red line is supposed to be a clear warning to the user that the connection is not secure, and that anything about the site, or that you send to the site (like passwords) may be observed or modified in transit by anyone.
 The title text essentially explains the joke, noting that maintaining a website costs money and that there are regulatory agencies responsible for taking down sketchy domains, and so if a website is still up despite these obstacles, it is probably trustworthy.

← Older revision		Revision as of 08:22, 19 November 2022
Line 8:		Line 8:

	==Explanation==		==Explanation==
		+	{{incomplete\| Needs to be more thoroughly explained, but not TOO thoroughly for the love of god!}}

	This comic pokes fun at the lack of security implied by a poor {{w\|https}} connection as implied by the "red line through https". Although a lack of the https protocol in a web process does allow for third party tampering and deception, it also implies that the site is rather old; and, if it has been maintained for this long, it is probably not malicious, as most malicious sites are either reported and taken down or allowed to become defunct by their operators after a short amount of time.		This comic pokes fun at the lack of security implied by a poor {{w\|https}} connection as implied by the "red line through https". Although a lack of the https protocol in a web process does allow for third party tampering and deception, it also implies that the site is rather old; and, if it has been maintained for this long, it is probably not malicious, as most malicious sites are either reported and taken down or allowed to become defunct by their operators after a short amount of time.

← Older revision		Revision as of 20:17, 24 August 2022
Line 8:		Line 8:

	==Explanation==		==Explanation==
−	~~{{incomplete\|Created by a SPY AGENCY THAT PRETENDS TO NOT BE DISCUSSED - Please change this comment when editing this page. Do NOT delete this tag too soon.}}~~

	Some web browsers display https with a red line through it (<span style="color:red"><s>https</s></span>) to indicate that there is a problem with the HTTPS connection. The red line is supposed to be a clear warning to the user that the connection is not secure, and that anything about the site, or that you send to the site (like passwords) may be observed or modified in transit by anyone. This danger is true of HTTP connections as well, but HTTPS connections are used for secure communications such as banking and email.		Some web browsers display https with a red line through it (<span style="color:red"><s>https</s></span>) to indicate that there is a problem with the HTTPS connection. The red line is supposed to be a clear warning to the user that the connection is not secure, and that anything about the site, or that you send to the site (like passwords) may be observed or modified in transit by anyone. This danger is true of HTTP connections as well, but HTTPS connections are used for secure communications such as banking and email.

@@ Line 20: / Line 20: @@
 When you see this red line, the proper thing to do is first to download the certificate and pin it in the system's store. This will raise a notice if it ever changes. For homemade certificates, called "self-signed", this is a normal situation. Nowadays self-signed certificates are no longer needed for normal public websites. The second thing to do is to contact the owner, and the community, via channels that are more secure, and engage the situation until it is properly addressed.
-There are a wide variety of reasons why an HTTPS connection might not be secure. A list of reasons associated with dangerous misconfigurations can be found on badssl.com[https://badssl.com/]. An HTTPS certificate (which offers reassurance that your information won't be stolen by a third party) is free to set up at for example https://letsencrypt.org, and takes only a few minutes, although note that this is not a barrier for someone building a site intentionally to steal your information.  A phisher could set up a site with HTTPS and have it trick you into giving up your info for some time before being caught and brought down. You can do this to your neighbor using free man-in-the-middle software, and they will be shown the red line indicating that you did so. The outdated-ness of the red line through the https refers to the situation of people not renewing their certificates when a site is abandoned; the expression mocks a common mistake of coming up with any relevent excuse to avoid the confusing situation of not being able to rely on https to verify you are communicating with the real website you visited.
+There are a wide variety of reasons why an HTTPS connection might not be secure. A list of reasons associated with dangerous misconfigurations can be found on badssl.com[https://badssl.com/]. An HTTPS certificate (which offers reassurance that your information won't be stolen by a third party) is free to set up at for example https://letsencrypt.org, and takes only a few minutes, although note that this is not a barrier for someone building a site intentionally to steal your information.  A phisher could set up a site with HTTPS and have it trick you into giving up your info for some time before being caught and brought down. You can do this to your neighbor using free man-in-the-middle software, and they will be shown the red line indicating that you did so. The outdated-ness of the red line through the https refers to the situation of people not renewing their certificates when a site is abandoned; the expression mocks a common mistake of coming up with any relevant excuse to avoid the confusing situation of not being able to rely on https to verify you are communicating with the real website you visited.
-The title text uses two very circumstantial (and not really dependable) details as if they were factors reinforcing the misplaced trust. For the first, you may perhaps think that if someone is still paying domain/hosting fees that they are still confident about their site's content. For the second, the search engines/archives appear to have not lost ''their'' confidence in it for whatever reason. There are problems with both these assumptions, and it does little to restore sanity to the already shaky understanding being exhibited. It is misusing a norm of factors of trust, in sarcasm around poor security of the modern day.
+The title text uses two very circumstantial (and not really dependable) details as if they were factors reinforcing the misplaced trust. For the first, you may perhaps think that if someone is still paying domain/hosting fees that they are still confident about their site's content. For the second, the search engines/archives appear to have not lost ''their'' confidence in it for whatever reason. There are problems with both these assumptions     <!-- e.g.? -->     , and it does little to restore sanity to the already shaky understanding being exhibited. It is misusing a norm of factors of trust, in sarcasm around poor security of the modern day.
 ==Transcript==