# HTTP and HTTPS (1)
Hypertext Transfer Protocol (HTTP) is the backbone protocol of the World Wide Web. However, all information carried in HTTP is transmitted in plaintext from the source computer to the destination on t

var unreadAlerts = '1';
Welcome back, purely_cabbage. You last visited: Today, 06:36 AM Log Out
You have one unread private message from dkota titled Welcome to the Forum!
New Reply

Threaded Mode HTTP and HTTPS

Levron
Steroid plug
Posts:
117
Threads:
55
Joined:
Feb 2023
Reputation:
59
Credits: 3.88€ [Donate]
View All
#1
03-16-2023, 07:11 PM
Hypertext Transfer Protocol (HTTP) is the backbone protocol of the World Wide Web. However, all information carried in HTTP is transmitted in plaintext from the source computer to the destination on the internet. HTTP does not protect data from alteration or interception by malicious parties, which is a serious threat to privacy, identity, and information security. All browsing activity should be considered to be at risk.
A common exploit of HTTP is called iFrame (inline frame) injection. Most web-based threats consist of malware scripts that have been planted on webservers. These webservers then direct browsers to infected servers by loading iframes. In iFrame injection, a threat actor compromises a webserver and plants malicious code which creates an invisible iFrame on a commonly visited webpage. When the iFrame loads, malware is downloaded, frequently from a different URL than the webpage that contains the iFrame code.
To address the alteration or interception of confidential data, many commercial organizations have adopted HTTPS or implemented HTTPS-only policies to protect visitors to their websites and services.
HTTPS adds a layer of encryption to the HTTP protocol by using secure socket layer (SSL). This makes the HTTP data unreadable as it leaves the source computer until it reaches the server. Note that HTTPS is not a mechanism for web server security. It only secures HTTP protocol traffic while it is in transit.
Unfortunately, the encrypted HTTPS traffic complicates network security monitoring. Some security devices include SSL decryption and inspection; however, this can present processing and privacy issues. In addition, HTTPS adds complexity to packet captures due to the additional messaging involved in establishing the encrypted connection. This process is summarized in the figure and represents additional overhead on top of HTTP.
Client browser requests a secure page with https://
--------------------------------------------------------------->
web server sends its public key with its certificates
<--------------------------------------------------------------
Client browser ensures that the certificate is unexpired or unrevoked
and was issued by trusted party.
Client browser creates symmetric key and sends it to the server
------------------------------------------------------------------------------>
Server decrypts symmetric key using its private key
Server uses symmetric key to encrypt page and sends it to client
<------------------------------------------------------------------------------
Client browser uses the symmetric key to decrypt the page and display it to the user.

> Quote:"Potential is only the expression of possibility, something that can be accesed accurately only in retrospect."

PM Rate
Report
Expanded
Newbie
Posts:
1
Threads:
0
Joined:
May 2023
Reputation:
0
Credits: 5€ [Donate]
#2
05-22-2023, 06:29 PM
Let me see what is in it
PM Rate
Reply Quote // Report

« Next Oldest | Next Newest »

New Reply

Quick Reply
Message Type your reply to this message here. Signature Disable Smilies | You have selected one or more posts to quote. Quote these posts now or deselect them.

- Subscribe to this thread

Users browsing this thread: purely_cabbage
var thread_deleted = "0"; if(thread_deleted == "1") { $("#quick_reply_form, .new_reply_button, .thread_tools, .inline_rating").hide(); $("#moderator_options_selector option.option_mirage").attr("disabled","disabled"); }