clehaxze

u/clehaxze@reddthat.com
7 posts · 13 comments

Recent posts

Recent comments

I haven't. There's a official Samsung repair center next to my workplace . I gone there expecting a faster turnaround.But was informed they only process phones and earbuds. I had to mail the SSD instead.

Going to do that in the weekend. Also bought a new SSD from Kingston since is is also my work machine. Can't have it down for too long.

Not professional sysadmin. I run my homelab and handles a few servers at work. I don't use IDS. So may be irrelevant.

  • WAF to stop HTTP parameter pollution and request smuggling
  • Fail2ban on SSH and move ssh away from port 22
  • Setup LAN recursive resolver and disallowed outbound raw DNS

For me, a lot more emphasis is on defending the application

  • Setup systemd unit hardening
  • Use Landlock LSM to whitelist directories (modifying source needed). Stops directory traversal and command execution
  • TLS or stunnel between application and database
  • Point DNS to local resolver
  • LD_PRELOAD hardened allocator

I'm currently looking into the Linux port of pledge to further reduce post exploit attack surface. But the project is not mature enough for production, yet.

For me the saying "work on your passion and you won't work a day" is very true. Why would I not experiment with crazy code in the product when I don't have time in the day. Or trying out new cryptography and see how it absolutely beats current protocols.

With that said. It's also important to have time with you family/boy/grilfriends. They are also important

on Lemmy is confusing · c/asklemmy · 1 pts · 3y

That's the exact point. reddthat.com or lemmy.world servers can blow up into pieces and none of users living on other servers would be affected. Unlike Reddit, where a single company can decide they want to do something stupid and everyone had to obey.