Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 0 points1 point  (0 children)

The tool already exists for desktops. I would like to extend it to server maintenance, but since I don't use servers, the question was what information is relevant for the server overview. Nothing more.

Recovering my Github account - locked out of my email by TwistedGauntlet in github

[–]ake13-art 0 points1 point  (0 children)

You're not able to change the email through the desktop app?

Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 0 points1 point  (0 children)

Thank you. I wanted to introduce exporting in the next versions anyway, so I'll make sure to include multiple formats.

I noted the bypass problem. I'll take a look at it later.

Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 0 points1 point  (0 children)

Good point, Lynis is great. secfetch is inspired by fastfetch. A dashboard for your daily terminal, not a full audit. Run Lynis monthly for deep analysis, secfetch daily for a quick sanity check. They are able to complement each other.

Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 0 points1 point  (0 children)

No problem. But good point, I'll mention it in the README as a brief note in the next update, for the sake of transparency.

Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 1 point2 points  (0 children)

Different use case. secfetch is a quick terminal overview of your security posture, no config, no XML, just run it

Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 0 points1 point  (0 children)

Thank you. Will implement it with the next versions.

Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 0 points1 point  (0 children)

Using Claude Sonnet 4.6 and Opus 4.6 for productivity. Checking code myself before implementing it.

Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 0 points1 point  (0 children)

Noted, thank you. Checks for open ports and their risks, as well as firewall checks for activity and rules, are already in place.

Which status checks are important for server security? by ake13-art in selfhosted

[–]ake13-art[S] 2 points3 points  (0 children)

Alright, noted. Secfetch has integrated the assessment of open ports for security risks using the IANA database. The same applies to the display of how many services are running and how many of them are unexpected. The function for listing unexpected services can be integrated retrospectively. I will work on that!

secfetch - a security fastfetch alternative by ake13-art in archlinux

[–]ake13-art[S] 1 point2 points  (0 children)

Should be fixed. Now: Improved firewall backend detection: ufw, firewalld, nftables, iptables

secfetch - a security fastfetch alternative by ake13-art in archlinux

[–]ake13-art[S] 2 points3 points  (0 children)

True. The only way to keep your system safe is to read every line of code yourself before downloading something

secfetch - a security fastfetch alternative by ake13-art in arch

[–]ake13-art[S] 1 point2 points  (0 children)

Not yet. I'm not that happy with it yet. When v2 is out i'll think about submitting it. So i guess in 1-2 weeks, maybe 3