Comment on HoneyWire: Open-source, zero-agent cyber canaries for your homelab (Thinkst/OpenCanary alternative)
irmadlad@lemmy.world 3 days ago
Do I understand correctly that with HoneyWire you deploy ‘false assets’? I guess along the lines of a honeypot but the ability to deceive bots and other nefarious actors into thinking there are specific assets that they might want to exploit?
Looks like the following from github:
Suite of Official HoneyWires: Includes native TCP Tarpit, Web Router Decoy, File Canary (FIM), ICMP Canary, and Network Scan Detector.
I don’t see any AI disclosure on github or here OP. Can you specificy how AI has been used on this project?
AI Disclosure: As a student and solo developer/maintainer, I used AI as a “junior dev” during project development to help accelerate boilerplate writing and documentation. All core architecture, system structure, and security logic were fully designed and implemented by me.
irmadlad@lemmy.world 3 days ago Ok, so see this AI Disclosure would be helpful in the original post. You’re going to get downvoted either way, but at least it’s upfront. Don’t take it personal, it’s just that there is a faction of very vocal anti-AI users here.
My 2p.
I appreciate the feedback and the 2p! I definitely don’t take it personally. I completely understand the skepticism around AI in this community, which is why I don’t hide it. At the end of the day, the core engine, the distroless container architecture, and the threat model were entirely engineered by me. HoneyWire is fully open-source and transparent, so anyone is welcome to audit the codebase. I also have several other public, non-AI projects on my GitHub if anyone wants to vet my background. But fair point I’ll make sure to be more upfront about using it as a scaffolding tool in future posts
irmadlad@lemmy.world 3 days ago Can you specificy how AI has been used on this project?
I cannot. I’m not the dev.
andreicscs@lemmy.world 3 days ago
That’s exactly how it works. You deploy these low-interaction decoys (traps) across your internal network to act as tripwires. Since legitimate users have no reason to touch them, any interaction is a high-fidelity alert indicating a potential breach or lateral movement. Right now, you can spin up a few different types of traps, like a network scan detector that sits completely quietly and triggers an alert if it detects a port or network scan hitting that specific node, or a Web Router Login Page, that looks like a legacy admin interface and instantly alerts you if someone tries to brute-force or log in. The best part about HoneyWire’s architecture is that developing new sensors is the easiest part, so the ecosystem is designed to be highly extensible as the community grows.
That’s very interesting. Thanks.
Now for the burning question on everyone’s mind…was this vibe coded, or AI assisted in any way? I don’t outright reject AI assisted projects, but of course my concerns are always security. Also, what is the depth of your experience coding?
Thanks
andreicscs@lemmy.world 3 days ago
No issue that’s a completely fair question, yes AI was used as an accelerator for writing boilerplate code, scaffolding the initial UI layout, and helping me structure the documentation. However, the core security logic, container architecture, and threat model were entirely designed and verified by me. I have about 8-9 years of software development experience. While HoneyWire is my first major public release, it’s the culmination of years of building internal tools, network utilities, and lab environments.
Because security is the primary focus, I deliberately designed the architecture to minimize risks. I highly encourage you to review the source code on GitHub, I’d be happy to receive feedback about the architecture or any threat-modeling critiques!