News for hackers. Stuff that matters.
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by the8472 on Monday May 27, 2024 @05:46PM (#40495061)
I wish it were just some old boxen from 20 years ago. $employer STILL does port-based firewalling and thinks it's great policy. Just getting SSH to github requires requesting an exemption.

edit: spelling

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by frutiger on Monday May 27, 2024 @06:22PM (#40495325)
> some old boxens

Aside: in this vernacular, plural of ox is oxen; plural of box is boxen. “boxens” is never appropriate.

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by akira2501 on Monday May 27, 2024 @07:41PM (#40495875)
DNS SRV. So much promise. Ultimately just became "I know where exchange is!"
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by mschuster91 on Tuesday May 28, 2024 @04:35AM (#40498676)
> $employer STILL does port-based firewalling and thinks it's great policy.

And they're not wrong either, it by definition disables not just a whole class of (admittedly outdated) communication channels for malware (such as IRC), but also other stuff you don't want to happen on your network either: bittorrent, people running online games during work...

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by dewey on Tuesday May 28, 2024 @12:47PM (#40502718)
Isn’t it trivial to run these on another port?
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by p_l on Tuesday May 28, 2024 @04:42PM (#40505398)
It is