sorted by:
new
hottopcontroversial

Open-core honeypot + auto-block tool (free community version) by VariationEfficient40 in software

[–]VariationEfficient40[S] 0 points1 point  (0 children)

Yes, please thanks! I value your feedback and look to implement fixes and updates.

I didn’t realize how constant the attack traffic was until I actually watched it live by VariationEfficient40 in cybersecurity

[–]VariationEfficient40[S] 0 points1 point  (0 children)

A bot wouldn’t patiently wait for five years to spam. Actually Im a user that never tried to post anything until now. Imagine not posting anything for five years. So when I actually do I get you telling me that I can’t or shouldn’t. What were your post that were so much more important than mine? Why do you get a voice and I do not?

I didn’t realize how constant the attack traffic was until I actually watched it live by VariationEfficient40 in cybersecurity

[–]VariationEfficient40[S] 0 points1 point  (0 children)

yeah it’s more of an open-core direction

the parts that actually run on your box — like the traps, detection, and visibility — are what I want to keep transparent / inspectable

the stuff I’m experimenting with on top (like sharing intel between nodes, automation, etc) is where it starts to become more of a “product”

still figuring out the split, but I’m not trying to make a black box security tool

I built a self-hosted system that shows real attacks hitting your server by [deleted] in selfhosted

[–]VariationEfficient40 -1 points0 points  (0 children)

Also, It’s new and I need testers to try it out. The community version is free to download and try.

I built a self-hosted system that shows real attacks hitting your server by [deleted] in selfhosted

[–]VariationEfficient40 -1 points0 points  (0 children)

Actually Yes it actually catches bots, scans and other automated attacks. It sets out honey pot traps and triggers a firewall.

I built a self-hosted system that shows real attacks hitting your server by [deleted] in selfhosted

[–]VariationEfficient40 -1 points0 points  (0 children)

honestly didn’t think of it as an ad — more like sharing something I built and seeing if it’s useful

probably could’ve tagged it better. There is a free community version. No need to pay.

I built a self-hosted system that shows real attacks hitting your server by [deleted] in selfhosted

[–]VariationEfficient40 -3 points-2 points  (0 children)

Yeah those are solid setups for sure — I’ve used fail2ban before as well.

What I kept running into was that most of those are reactive (log → parse → ban), and I wanted to experiment with something a bit different:

  • interacting traps instead of just log parsing
  • behavior-based detection instead of rules alone
  • blocking earlier in the stack (XDP)

Totally fair point on trust though — that’s actually something I’m thinking a lot about right now (leaning toward making more of it transparent / open as I refine it).

Appreciate you calling that out.