←back to thread

I can see your local web servers

(http.jameshfisher.com)
652 points jamesfisher | 5 comments | 28 May 19 07:57 UTC | HN request time: 0.206s | source
Show context
jsty ◴[28 May 19 09:25 UTC] No.20028486[source]▶
"If you see any results like 192.168.0.4:3000 is available!, you should tell your colleague to secure whatever she has running on that port"

Someone's going to access this page at $BIGCORP with an overly trigger-happy IDS and get a fun morning meeting with IT to un-quarantine their machine.

replies(2): >>20028575 #>>20030080 #
1. nostalgk ◴[28 May 19 14:02 UTC] No.20030080[source]▶
Yup, excited for the meeting. Haven't seen those guys in a while.

Was expecting to learn some security techniques, instead got essentially port scanned :)

replies(1): >>20031596 #
2. jschwartzi ◴[28 May 19 16:21 UTC] No.20031596[source]▶
Whereas I'm learning that my network is fairly secure against this type of port scanning.
replies(2): >>20031895 #>>20032747 #
3. ◴[28 May 19 16:49 UTC] No.20031895[source]▶
4. nostalgk ◴[28 May 19 18:09 UTC] No.20032747[source]▶
Of course, mine was too. I'm sure in part due to the diligent security team that will be stopping by my desk in the next few days!
replies(1): >>20035685 #
5. jschwartzi ◴[29 May 19 00:07 UTC] No.20035685{3}[source]▶
Since I work from home I'm both the security team and the guy who inadvertently ran a port scanner in his web browser.