I'm missing something > strange devices show up for some of our customers' users > how did it load these pages which were often behind an authwall without ever logging in or having auth cookies? Either - The customer has screwed up user auth big time and some X knows that.... lets go with no - OP's data is wrong or they are reading it wrong - They are explaining it badly.
What's happening is that some MiTM Palo Alto networks system is intercepting the HTML contents of the page, waiting a bit, and then rendering that HTML content again in old Chrome on a separate machine. It's like if you go to a authenticated page that only you can see, like https://news.ycombinator.com/flagged?id=aaron695 , did "View Source", copy-and-paste that source into a HTML file, and then you send me the HTML…
10 Second Teleportation
61–70 of 71 posts
Re: 10 Second Teleportation
#62They have a feature that effectively "tests" what the user is about to load in a virtual environment, and sees if that content behaves abnormally. I forgot what they called it. It sounds like this could be it.
Re: 10 Second Teleportation
#63Unrelated to the article directly, it's kinda neat that the site's text selection highlight color is randomized on every mousedown.
Josh on our team is so happy people discovered and liked his easter egg!
Re: 10 Second Teleportation
#64Maybe related somehow to that?
Re: 10 Second Teleportation
#65"Palo Alto Networks" is something that shows up clearer than anything else in my lighttpd logs, as they include the "we're palo alto networks doing research, contact us here(email) for us not to scan" in http request headers. They appear to do full ipv4 range scan many times a day IIRC. Funnily enough I got motivated to try to make my crawler show up the same way in my own server logs by just raw scan breadth, IE by…
> This is an Internet-scale port scanner. It can scan the entire Internet in under 5 minutes, transmitting 10 million packets per second, from a single machine.
Absolutely insane
Re: 10 Second Teleportation
#66Unrelated to the article directly, it's kinda neat that the site's text selection highlight color is randomized on every mousedown.
/* Text Higlight Color /**/ :root { --highlight-color: null; } ::selection { background: var(--highlight-color); color:#FFFFFF; } ::-moz-selection { /* Code for Firefox */ color: #FFFFFF; background: var(--highlight-color); } const colors = ["#F76808", "#30A46C", "#0091FF", "#6E56CF", "#E5484D"]; window.addEventListener("mousedown", (e) => { const color = colors.shift(); document.documentElement.style.setProperty("--…
Re: 10 Second Teleportation
#67Earlier quoted context omitted.
What they choose to investigate is itself revealing. CDNs and large hosting providers for example would be in a position to make inferences by observing and correlating traffic from that origin. I would be trying to obfuscate it using a VPN distributed over a range of countries and IP addresses. That could appear strange to a host, depending on how they implement it.
Except that most open source material is now encrypted. They could see lots of traffic towards Twitter/Facebook/YouTube/google and lots of overseas news sources but would have little insight into actual content.
Re: 10 Second Teleportation
#68Earlier quoted context omitted.
I thought I messed it up! I had no idea this was a thing.
You can always edit it after the fact.
It's bad enough trying to proof my own comments what with being navigated away from that comment (I've a few recent typos caught well outside edit windows which nag on me as I type). Changing submitter's content without notice is ... less than optimal.
I'll note that certain edit features (e.g., year edits) do involve a confirmation, which has in fact proved useful.
Re: 10 Second Teleportation
#69I remember I worked somewhere where they had something like this. Most people had windows machines, but I had a mac that I had installed. My machine wanted me to accept a client certificate from palo alto networks. I did not and kept refusing. I think they had some sort of intrusive mitm proxy that filtered everything everyone was doing/browsing.
The usual way is to require a custom CA for all clients, sounds like an ineffective setup if you can just ignore it. I.e. it should be a intermediate certificate for the proxy you need to acknowledge.
I suspect most of the other non-dev machines in the building had the ca installed by IT.