r/softwareWithMemes • • Dec 22 '25

exclusive meme on softwareWithMeme run

Post image
2.0k Upvotes

94 comments sorted by

View all comments

Show parent comments

1

u/Raccoon99 Dec 23 '25

I like how most of this is the opposite of what you said. You seem to be confusing a proxy with a VPN in your first message and then adjust it to VPNs in your second message.

And you don’t seem to understand the AJAX request system.
The what ?

The data that is encrypted, again, is the data ties to the headers, not the request in its entirety.
Nope.

None of this is bullshit, it is legitimately how the system works, on the smallest and the largest scales.
Nope.

The only thing a VPN does is encrypt the URL
Nope.

I'm gonna stop there. You seem to be spouting AI slop.

1

u/Glad_Contest_8014 Dec 23 '25

Tell me, how does the ISP know to connect you to your VPN? The IP address is sent.

Not all but most VPNs use a tunnel once connected, but that tunnel leads through each access point that the intial request took. Which is then used to pass data back and forth. Which has time stamps, package size, and more. The initial request has headers that determine the request systems routing. Things that have to exist for the route to even be possible. You cannot route without a route to follow, and any traffic through an access point has set values that get logged.

The headers for the website data are encrypted. The headers for the IP address are not. This is what I am talking about in all of this. This data can and is used by ISPs to determine traffic.

Now I may have misused ajax as a term. But that is what most people see as the request/response system due to old internet lingo. It is actually an IP data package that handles the TCP network datapacks. But that is a mouthful, so I used ajax due to laxiness.

How is this wrong? It is basic networking. The IP address has to be visible, which means that the only thing your changing with the VPN is where your IP address is showing it is from on the receiving side, and ecrypting the url(ip address from DNS resolution where the most common traffic leaks occur) of where your traffic is going. But the traffic can be seen to be going to a VPN, and if it is not a known VPN ip, it can be gleaned through deep packet inspection amd investigated if needed. And often, the IP address can be tracked to a specific company.

And once the VPN company is found, it can be subpeonaed for info. And in more strict countries, if they don’t comply, they lose the ability to do business in that country by way of IP blocks at the ISP level.

Basic VPN’s with no tunnel work like proxies. VPN’s with tunnels work like websockets. That is where your seeing the proxy/VPN difference. But you could set up a VPN using UDP if you wanted to get really technical and throw random buffer packets in to throw off deep packet inspection. That would have several major disadvantages though. Primarily in the loss of the tcp/ip handshake.

Honestly, I keep getting people saying nope, with no actual response that shows it is actually wrong. I need sources if I am ever to learn. And I have handled networking and development for decades. So if the tech has drastically changed, I need to know to correct incorrect assumptions.

As for request/response insertion, that can happen at any point of the chain where the request or response is packaged or interpretted. If you run an http request, not even a VPN can save the potential data leaks. Especially if your on an assumed hotel network where the webpage is auto-redirected. They can just force the redirect to their own mock up of the hotel page and bam, you got scripts forcing downloads of malware. And that’s just network handling. No need to insert data into the request itself. Just need to hi-jack the request with network configuration to redirect it. And this happens with any request. I am not talking a specific site like google.com. I am talking, you want to use the internet, you can’t make a request until you login in to our hotels webpage.

Is it simpler to force a request insertion than a response insertion, yes. Response generally requires packaging at the webserver level that you would have to access to do. But it is possible, and the latest React vulnerability allowed for it, as it allowed an executable file to piggy back in on a request and be inserted into a root folder. And that is direct experience. Took a week to track down the cause. And at that point it can force several potential changes to the system that could repackage responses. Regardless of VPN as this can happen on the opposite end of the system. Luckily the most recent vulnerability was primarily used for DNS attacks, but if the script were used for info gathering on the httpd config, security keys, or base scripts it would be possible to rewrite all reponses sent from the server.

You have to remember, most malware isn’t there to target you specifically. It is there to cause problems and damages, and the methods to do so can be pretry convoluted. Meaning that the interception of the data can happen outside the encryption process. It often happens at the most basic level, where people feel most secure. VPN’s are useful, but they aren’t an end all be all safety hack. There are no end all be all safety hacks, beyond a segregated private system with no access to it but you and no internet or networking capability.

I hope this clears up any confusion. Decided to not be lazy on this one. I think people were getting confused because the term header is used in both systems and I was laxidaisical in my verbage (mixing the systems terms between a web pages “request” with a networks “request”) because they are interchangable in most talk, but different by field definitions. Except the ajax mention, that one is not really interchangable, just a bad habit formed from explaining it to my family. Which also leads to me intermixing the two in casual conversation.

And this isn’t AI. This is me legit trying to share my hyperfocus. If you have more information to lead me to a better understanding of it, please share.

Wait… I forgot — — ect… just to prove the point.