2017-08-04 at 2:48 AM UTC
aldra
JIDF Controlled Opposition
I don't think there even is an ssl cert; connection's being handed off to 443 but it's just raw http running there
2017-08-04 at 3:08 AM UTC
-SpectraL
coward
[the spuriously bluish-lilac bushman]
This is an attack on the mothership. All hands to battle stations. This is not a drill. I repeat, this is NOT a drill.
2017-08-04 at 3:20 AM UTC
Originally posted by SBTlauien
Time to update.
Yee, I have an auto renewal script but forgot to set it up to restart the webserver after doing renewal so it was new on the filesystem but still using the cached version in memory.
Originally posted by aldra
aldra@rattex:~$ telnet niggasin.space 443
Trying 167.88.112.107...
Connected to niggasin.space.
Escape character is '^]'.
nigganigganigga
HTTP/1.1 400 Bad Request
Server: nginx/1.6.2
Date: Fri, 04 Aug 2017 02:49:06 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 172
Connection: close
<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.6.2</center>
</body>
</html>
Connection closed by foreign host.
No, there is SSL, you just didn't initiate a handshake which nginx will respond to with the stock bad request page. Even if you submitted a valid HTTP request, you'd get the same result:
[lanny:~]$ telnet niggasin.space 443
Trying 167.88.112.107...
Connected to niggasin.space.
Escape character is '^]'.
GET / HTTP/1.1
HTTP/1.1 400 Bad Request
Server: nginx/1.6.2
Date: Fri, 04 Aug 2017 03:09:50 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 172
Connection: close
<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.6.2</center>
</body>
</html>
Connection closed by foreign host.
The following users say it would be alright if the author of this
post didn't die in a fire!
