Would you be willing to give a few more details about what happened? I'm not interested in the identities of the companies or people, just interested in a high level overview of what happened. We don't hear these stories often.
- Used an APT for hire but I don’t believe they did succeed , still it is quite insane. I was lucky enough to catch a targeted rootkit but issue was quickly remediated. I’ll eventually find a consultant to analyse the Win 11 rootkit. They were definitely not script kiddies.
- Some black hat SEO and shills for hire, but that is expected.
I’m really surprised by hired journalist / APT aspect. Something I never imagined would happen, but apparently it does happen.
There is no way I’ll start another startup unless I receive backing from a huge VC company.
Current economic paradigm is more similar to centralised/controlled economies of USSR. Thus if you want to succeed, you will need friends with connections to central banks.
I wish I had saved a copy of the assignment. It was ridiculous.
C - Redis
Honestly, an immutable OS would be more ideal but it isn’t very realistic. If you are adventurous, it would also be possible to setup a system where host image gets rebuild every night and persistent data gets pulled from a git repo.
I also recommend manually reading/checking the the BIOS EEPROM and re-installing the OS from scratch at least every 6 months. This should mostly eliminate most of the advanced threats.
You can setup an ansible script to re-install everything so it can automated.
However, sometimes programmers forget to remove the debug symbols from the final binaries of the game. Programmers are humans, and humans make mistakes.
Delivering software with debug symbols - wether commercial or non-profit - isn’t a mistake. It is a decision for better bug reports, traces and convenience.Executables/libraries on disk file size will increase with debug symbols. The kernel and loader will look at binary headers and load only what is needed for execution into main-memory. Kernel and loader will not load the debug symbols at runtime, they are useless for them. The debugger will look also at the headers and use them to load the debug symbols, which are need for backtraces. Therefore initial file read from disk will take a little more time but the execution is not affected. Startup speed is usually influenced by loading of further resources, initialization and checks. So you will get a lot for some bytes on the disk.
https://stackoverflow.com/questions/24117063/is-a-program-co...
https://stackoverflow.com/questions/39222698/does-compiling-....
Some people still argue that security by obscurity works and hide everything. I doubt that.
There are ways to convert symbol names on the crash report server, so the claim that you can get better crash report with debug symbols is not correct.
Why you shouldn’t release debug symbols:
* It helps patent/copyright trolls litigate you easier.
* Makes it easier to reverse engineer your binaries, which will help malicious actors and competitors.
* You might lose some trade secrets.
If you are a startup owner, please ensure to never release commercial/close-source binaries with debug symbols. You can thank me later.