Aw man, I thought this was going to be audio sensor that logs you in with a secret physical knocking pattern (like on a door or desk).
Knocker, a knock based access control system for your homelab
31–40 of 175 posts
Re: Knocker, a knock based access control system for your homelab
#32Earlier quoted context omitted.
I guess at least they're being honest, but I would agree - there's a large delta between Al-assistance and Al-driven, and "vibe coding" is one step further (just accepting everything Al does without critique, so long as it "works"). Great for prototyping, really bad for exposing anything of any value to the internet. (Not Anti-Al, just pro-sensible)
Github should have "LLM" as language for repos that self report to be vibe coded or at least this kind of disclosure should be at the top of the readme not after thought. Also the "If you're Anti-AI please don't use this." is pretty funny :D I guess I must be "Anti-AI" when I think this kind of code is wild to rely on.
I fully support the AI self-disclosure, but what I wonder what it is about AI generated code that makes this a separate problem from any other code where you don't know the programmer's competence?
Is it because the AI can generate code that looks like it was made by a competent programmer, and is therefore deceiving you?
But whatever the reason, I think that if we use it as a way to shame the people who do tell us then we can be assured that willingness to disclose it going forward will be pretty abysmal.
Re: Knocker, a knock based access control system for your homelab
#33I had hoped this would allow me to use various patterns of knocking on my desk to perform system actions. Do the cut-and-a-hair-shave knock to log in, or taptaptaptap-wait-tap to lock the screen, etc. Maybe with two microphones you could even distinguish between left and right handed knocks.
...now I'll have to make this myself.
Re: Knocker, a knock based access control system for your homelab
#34Aw man, I thought this was going to be audio sensor that logs you in with a secret physical knocking pattern (like on a door or desk).
That's what I thought was well, like a Morse code detector tied to the lock on the door or something lol
Re: Knocker, a knock based access control system for your homelab
#35Earlier quoted context omitted.
Github should have "LLM" as language for repos that self report to be vibe coded or at least this kind of disclosure should be at the top of the readme not after thought. Also the "If you're Anti-AI please don't use this." is pretty funny :D I guess I must be "Anti-AI" when I think this kind of code is wild to rely on.
I fully support the AI self-disclosure, but what I wonder what it is about AI generated code that makes this a separate problem from any other code where you don't know the programmer's competence? Is it because the AI can generate code that looks like it was made by a competent programmer, and is therefore deceiving you? But whatever the reason, I think that if we use it as a way to shame the people who do tell us t…
[dead]
Re: Knocker, a knock based access control system for your homelab
#36IP based exclusion should not be considered a security measure, not even for a low risk environment like a home lab
> IP based exclusion should not be considered a security measure Apologies in advance if I'm missing something obvious here, but are you saying an IP allow list is not a standard security practice? If so I'd appreciate further explanation.
It's useful when the client always has its own static IP that _doesn't change_ between sessions. In this case, where the public facing IP may be shared by thousands of users, it provides no real security. All you'd have to do to gain access would be getting the client IP and finding some way of getting on the same network. Which in many cases could be as easy as subscribing to the same cell network or other ISP, or connecting to the guest wifi network of an office building.
Re: Knocker, a knock based access control system for your homelab
#37[dead]
More adoption and proliferation of vibe coded apps like yours and the OPs is going to end up being a major disaster. I find it strange for you to say you “released” this when, in the modern era, what you linked is the equivalent of a pastebin bash script. In your case, it looks like ChatGPT has barfed more lines of readme than lines of code!
I'm sorry it didn't resonate with you. The accusation of vibe coding is a bit discouraging, but I don't feel the need to prove anything. I built this in my spare time and shared it in case it's useful to others.
Some of the most helpful code I've used in my career started out as quick scripts or pastebin snippets.
Yes, I used AI to help with the documentation, but I also put in time to edit it and make sure it clearly explains the concept.
Re: Knocker, a knock based access control system for your homelab
#38Earlier quoted context omitted.
Github should have "LLM" as language for repos that self report to be vibe coded or at least this kind of disclosure should be at the top of the readme not after thought. Also the "If you're Anti-AI please don't use this." is pretty funny :D I guess I must be "Anti-AI" when I think this kind of code is wild to rely on.
I fully support the AI self-disclosure, but what I wonder what it is about AI generated code that makes this a separate problem from any other code where you don't know the programmer's competence? Is it because the AI can generate code that looks like it was made by a competent programmer, and is therefore deceiving you? But whatever the reason, I think that if we use it as a way to shame the people who do tell us t…
I think it makes sense for stuff that is fully AI generated to the point where you commit the prompts to git. At that point, they become the real "source code" and the generated code is more of a build artifact. It makes sense to tag the language as "LLM" instead of e.g. "Python" because that's what contributors will be expected to touch when interacting with the codebase.
Re: Knocker, a knock based access control system for your homelab
#39I don't want to be a hater, but exposing access to your homelab through a "fully vibe coded" application (it's mentioned at the bottom of the README) is probably not a good idea. The idea itself sounds fun though
I guess at least they're being honest, but I would agree - there's a large delta between Al-assistance and Al-driven, and "vibe coding" is one step further (just accepting everything Al does without critique, so long as it "works"). Great for prototyping, really bad for exposing anything of any value to the internet. (Not Anti-Al, just pro-sensible)
> Great for prototyping
I must be Doing It Wrong(TM), because my experience has been pretty negative overall. Is there like a FAQ or a HOWTO or hell even a MAKE.MONEY.FAST floating around that might clue me in?
Re: Knocker, a knock based access control system for your homelab
#40I implemented something similar as a caddy module, then I realized that if I was connected to a public wifi network I was actually authorizing the whole bunch of people that were connected to it with me. How do you avoid this, or is it just not important?
It’s the third option: Port knocking is stupid.
https://news.ycombinator.com/item?id=39898061>