Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Conversation

Notices

Embed this notice
SwiftOnSecurity (swiftonsecurity@infosec.exchange)'s status on Monday, 06-Jan-2025 11:57:58 JST SwiftOnSecurity

Fun fact a previous employer used a country's TLD as their internal domain (???) and that basically made me who I am today on the Windows networking stack
https://infosec.exchange/@ftp_alun/113777709036127647
In conversation about 12 days ago from infosec.exchange permalink
Attachments
1. No result found on File_thumbnail lookup.
  
  Alun Jones (@ftp_alun@infosec.exchange)
  
  from Alun Jones
  
  @SwiftOnSecurity I once had to deal with a customer that was running their internal network on a class A that wasn't being used. Somehow it worked for them until they tried to get some Windows machines in. The Windows machines didn't communicate with anything on their network. "So what unused Class A did you install your network on? 10.*?" "No, 127.*." ... "And that's been working for you?" "Right up until we tried to use Windows. Windows is a piece of shit, can't do simple ordinary networking." "No, Windows right here is obeying all the RFCs. Your Suns are sending out traffic they should be keeping internal. You need to renumber your entire network."
- Jeff "never puts away anything, especially oven mitts" Cliff, Bringer of Nightmares 🏴‍☠️🦝🐙 🇱🇧🧯 🇨🇦🐧 likes this.
- Embed this notice
  Chris Siebenmann (cks@mastodon.social)'s status on Monday, 06-Jan-2025 11:57:58 JST Chris Siebenmann
  in reply to
  
  @SwiftOnSecurity Once upon a time, we had a subdomain .rw.<thing>.utoronto.ca, and we had software that used short names like '*.rw' for authorization, and we didn't notice that .rw had become a ccTLD.
  And that is why people from Rwanda could read Usenet from our news server for a while.
  ('RW' was and is the abbreviation of a building name at the university.)
  
  In conversation about 12 days ago permalink
  
  Haelwenn /элвэн/ :triskell: likes this.

Public

Conversation

Notices

Feeds