So when I scan a server and 666 happens to be open. Nmap will now report “doom” under the “Service” header?
Most people will get a chuckle, but I suspect laymen and even Christian zealots will throw a fit.
Like when a normal person gets an error on their screen and it prints “process closed: child killed by parent”. It will probably raise an eyebrow at the very least, lol.
The idea of globally assigning ports to specific things feels so retro. Back when the world was a lot smaller.
Today it still makes abundant sense for more generic concepts like where you do HTTP or SSH but to register them to specific companies is amusing and nostalgic.
In my RnD testing, when I just need an arbitrary port, 666 is my go to.
(a) It's almost never used by anything else and (b) <3 Doom
Unfortunately, I showed some software in a sprint demo once, using 666 as an arbitrary port. I was very clear that this port can be anything, because the software was made to be configurable by the user, and of course the project manager wrote it down and put it in the "official" and released documentation that the customer must use port 666. facepalm.
I wonder how many protocols/servers that are "officially registered" there are by now completely out of use (as in, truly not actively used by anyone on the planet).
And how many of the listed email addresses still work.
Well, it does about as much as say, when Congress names an Aircraft Carrier, or ISO some day publishes C++ 23 (probably later this year).
Concretely your Linux systems probably have a file named /etc/services which maps the string "doom" to port number 666, much as it maps "ssh" to 22 or "http" to 80.
"BTW, if you see your mom this weekend, be sure and tell her digital sataaaan!"[0] When this was first released, I wonder how digital it was back in 1990.
sybercecurity|1 year ago
rovr138|1 year ago
mdqs 666 tcp
mdqs 666 udp
doom 666 tcp doom Id Software [ddt] [ddt]
doom 666 udp doom Id Software [ddt] [ddt]
ughitsaaron|1 year ago
xyst|1 year ago
Most people will get a chuckle, but I suspect laymen and even Christian zealots will throw a fit.
Like when a normal person gets an error on their screen and it prints “process closed: child killed by parent”. It will probably raise an eyebrow at the very least, lol.
jsheard|1 year ago
CalRobert|1 year ago
https://en.wikipedia.org/wiki/SCO%E2%80%93Linux_disputes
ChrisArchitect|1 year ago
4ad|1 year ago
jvolkman|1 year ago
imwillofficial|1 year ago
Waterluvian|1 year ago
Today it still makes abundant sense for more generic concepts like where you do HTTP or SSH but to register them to specific companies is amusing and nostalgic.
daveslash|1 year ago
(a) It's almost never used by anything else and (b) <3 Doom
Unfortunately, I showed some software in a sprint demo once, using 666 as an arbitrary port. I was very clear that this port can be anything, because the software was made to be configurable by the user, and of course the project manager wrote it down and put it in the "official" and released documentation that the customer must use port 666. facepalm.
solardev|1 year ago
leoh|1 year ago
egberts1|1 year ago
Off-topic: It is nice to see my name amongst the register ports.
brazzy|1 year ago
And how many of the listed email addresses still work.
dfox|1 year ago
wizzwizz4|1 year ago
aarestad|1 year ago
AdmiralAsshat|1 year ago
egberts1|1 year ago
https://www.shodan.io/search/report?query=666
resource_waste|1 year ago
zeroxfe|1 year ago
tialaramex|1 year ago
Concretely your Linux systems probably have a file named /etc/services which maps the string "doom" to port number 666, much as it maps "ssh" to 22 or "http" to 80.
throwitaway222|1 year ago
unknown|1 year ago
[deleted]
ydnaclementine|1 year ago
unknown|1 year ago
[deleted]
wumbo|1 year ago
[deleted]
dylan604|1 year ago
[0]https://www.youtube.com/watch?v=gFjKPLc5qD0