News for hackers. Stuff that matters.
Re:I wrote the SQL query in 5 mins. Why does my engineer say... by kogepathic on Wednesday May 24, 2017 @04:42PM (#14413286)
> Sometimes we overcomplicate the simplest shit.

Indeed. Why not use nc and telnet on port 443 to test? Linux already has nc and Windows already has telnet.

Re:I wrote the SQL query in 5 mins. Why does my engineer say... by reddit_clone on Wednesday May 24, 2017 @04:49PM (#14413336)
Indeed writing a _webserver_ to test connectivity sounds a bit non-simple.
Re:I wrote the SQL query in 5 mins. Why does my engineer say... by sofaofthedamned on Wednesday May 24, 2017 @06:15PM (#14413898)
The endpoint at their end was Windows. No nc. Apologies if that wasn't clear. I was testing our end reaching their endpoint at port 443.
Re:I wrote the SQL query in 5 mins. Why does my engineer say... by catmanjan on Wednesday May 24, 2017 @07:57PM (#14414366)
nc is the client, if you could host a webserver surely you could have run nc...
Re:I wrote the SQL query in 5 mins. Why does my engineer say... by kogepathic on Thursday May 25, 2017 @01:51AM (#14415519)
Actually I misunderstood and thought the server was Linux.

You could of course use nc as the client too, but it would be an additional install on Windows. [0]

And nc wouldn't help if the firewall was stateful and actually expected to see HTTPS traffic on port 443, so I do see their logic of putting an actual webserver there.

But without sufficient detail, it does seem at first glance to be overkill ;-)

[0] https://joncraton.org/blog/46/netcat-for-windows/

Re:I wrote the SQL query in 5 mins. Why does my engineer say... by sofaofthedamned on Wednesday May 24, 2017 @04:53PM (#14413377)
Good point, but the dudes at the other end had no idea. I had to give them an .exe, which was better than a .msi.

Bear in mind the server was at the Windows end, so no good with telnet over that side...