Here I thought it was going to be about telnet or something
PleaseLetMeOut@lemmy.dbzer0.com
on 15 Jul 17:03
collapse
Fun Fact: I once worked with a team that were mapping Iran’s internet infrastructure… for reasons. One of the ways we were able to zero in on the more important systems was because we kept finding these weird Cisco routers that had Telnet exposed to the open internet. All of which just so happened to share neighboring IPs (or close enough) with some pretty serious government systems. Fun times.
I’m not a CISCO tech, so I don’t know the specifics beyond that. But I do remember that the Telnet connection would permanently ban any IP that failed even a single password attempt. So they had that going for them, I guess lol
prettybunnys@sh.itjust.works
on 15 Jul 18:51
nextcollapse
I once worked for a fairly large multinational and was the main data center admin.
We ordered two separate comcast business account lines to serve as an emergency management network juuuuuuuuuuuust in case everything enterprise level went down. A true catastrophe somewhere else.
My boss put a windows xp box on it, and it alone with a single linux router in between it any the internet, totally insecure except for fail2ban and port knocking.
The entire time we were waiting for the rest of the data center to be wired it stood up, never being penetrated. Maybe a month or so.
BUT we’d banned basically the entire public IP space.
This was back in the early 2010s
PleaseLetMeOut@lemmy.dbzer0.com
on 15 Jul 19:04
collapse
I’ve actually seen medical offices setup similarly. Some random computer in a back office with all of their patient data on it, completely exposed to the internet, protected by nothing but a few Windows Firewall rules limiting the connections to a few IP blocks. Just so they can share information office-to-office for say… a root canal and dental crown to be done on the same day, but at 2 separate locations due to limited space.
I’d run out of fingers if I were to count the number of times I’ve seen similar setups, 3-4 toes would be needed at least.
prettybunnys@sh.itjust.works
on 15 Jul 19:10
collapse
Terrifying.
We did it just as a for funsies test, when we actually began to put equipment in it was all properly secured.
MysteriousSophon21@lemmy.world
on 16 Jul 05:32
collapse
Telnet is a nightmare for security since it sends everything in plaintext - even with IP banning, anyone sniffing the network could intercept credentials and payload data without needing to guess passwords at all.
whats_a_lemmy@midwest.social
on 15 Jul 14:21
nextcollapse
threaded - newest
TLDR: They are talking about Chinese coders hired by MS have access to DoD related code, not a computer program.
Thanks. Was going to say that, too.
I will hand it to the writer: good use of clickbait. It got me and it was technically accurate.
Thank you for being on the front lines of the click bait war.
Here I thought it was going to be about telnet or something
Fun Fact: I once worked with a team that were mapping Iran’s internet infrastructure… for reasons. One of the ways we were able to zero in on the more important systems was because we kept finding these weird Cisco routers that had Telnet exposed to the open internet. All of which just so happened to share neighboring IPs (or close enough) with some pretty serious government systems. Fun times.
I’m not a CISCO tech, so I don’t know the specifics beyond that. But I do remember that the Telnet connection would permanently ban any IP that failed even a single password attempt. So they had that going for them, I guess lol
I once worked for a fairly large multinational and was the main data center admin.
We ordered two separate comcast business account lines to serve as an emergency management network juuuuuuuuuuuust in case everything enterprise level went down. A true catastrophe somewhere else.
My boss put a windows xp box on it, and it alone with a single linux router in between it any the internet, totally insecure except for fail2ban and port knocking.
The entire time we were waiting for the rest of the data center to be wired it stood up, never being penetrated. Maybe a month or so.
BUT we’d banned basically the entire public IP space.
This was back in the early 2010s
I’ve actually seen medical offices setup similarly. Some random computer in a back office with all of their patient data on it, completely exposed to the internet, protected by nothing but a few Windows Firewall rules limiting the connections to a few IP blocks. Just so they can share information office-to-office for say… a root canal and dental crown to be done on the same day, but at 2 separate locations due to limited space.
I’d run out of fingers if I were to count the number of times I’ve seen similar setups, 3-4 toes would be needed at least.
Terrifying.
We did it just as a for funsies test, when we actually began to put equipment in it was all properly secured.
Telnet is a nightmare for security since it sends everything in plaintext - even with IP banning, anyone sniffing the network could intercept credentials and payload data without needing to guess passwords at all.
Wow. That’s pretty bad.
That program could, with grok it will
Windows isn’t little-known.