News for hackers. Stuff that matters.
Re:Log4Shell update: second Log4j vulnerability published by shakna on Wednesday December 15, 2021 @06:25AM (#29564491)
In an org that named their servers after planets, we turned off "Mars" (which was actually completely and utterly undocumented) and discovered it was the bridge between the intranet and the internet. However, upon turning it back on... Nothing came up again.

There were no logs to try and work out which processes needed to launch for it to do its job, causing several days of website downtime (not a simple website - dozens of interconnected services). We ended up taking the phone off the hook because we kept getting calls of "is it fixed yet?"

Re:Log4Shell update: second Log4j vulnerability published by jatone on Wednesday December 15, 2021 @10:07AM (#29566935)
future reference: next time just firewall the network and see what blows up rofl.
Re:Log4Shell update: second Log4j vulnerability published by hamburglar on Wednesday December 15, 2021 @11:46AM (#29568366)
A bit of network analysis to identify services that are being called before turning things off would probably be wise, too.
Re:Log4Shell update: second Log4j vulnerability published by shakna on Wednesday December 15, 2021 @09:08PM (#29574015)
The story with Mars is quite a bit more complicated than I've written, but we did scan it, and then try and isolate it, for a few weeks before we tried the restart. Let's just say there was a lot of redundancy that only broke once it couldn't ping at a very specific time.