• 0 Posts
  • 24 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle

  • The cli.

    I have used management interfaces like coxkpit in the last but i do not really like it that much. I have E-Mail Notifications setup for updates via aptitude and monitor using prometheus and grafana and get additional notifications via prometheus alarm manager.

    For an easy to use docker interface i use dockge, since i found it in this use case to be faster with a good, working, independend Interface.

    But for the Linux underneath, for all 10-20 servers i managae, CLI.





  • To achieve a compromised update you either need to compromise the update infrastructure AND the key or the infratstructure AND exploit the local updater to accept the invalid or forged signature.

    As i said, to compromise a signature checked update over the internet you need to compromise both, the distributing infrastructure AND the key. With just either one its not possible. (Ignoring flaws in the code ofc)









  • The ‘immediate attacks’ ppl mention is just static background noise. Server / scripts that run trying to find misconfigured, highly out to date or exploitable endpoints/servers/software.

    Once you update your software, set up basic brute force protection and maybe regional blocking, you do not have to worry about this kind of attack.

    Much more scary are so called 0-Day attacks.

    1. No one will waste an expensive exploit on you
    2. It sometimes can happen that 0-Days that get public get widly exploited and take long time to get closed like for example log4shell was. Here is work necessary to inform yourself and disable things accorsing to what is patched and what not.

    As i already said, no one will waste time on you, there are so much easier targets out there that do not follow those basic rules or actually valuable targets.

    There is obviously more that you can do, like hiding everything behind a VPN or advanced thread detections. Also choosing the kind of software you want to run is relevant.







  • None of those things are necessary. Like I don’t even have email configured on my server because I don’t need it at all except when the developer unnecessarily integrates it to the extent that it breaks it.

    Depending on the view, a functioning service something like password reset is necessary. To design the software that it can ship without functioning password can or cannot make sense, depening on the design choices. Depending on what else got send via e-mail designing the software around that can be challenging and burdening for the future of developing.

    If the setup required you to setup e-mail, the software and then also the developer can always assume there is a communication path to the individual user.

    As i said, it can and cannot make sense, but saying

    That makes no sense.

    and not even trying to put yourself into other shoes just does not make sense.