Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Knocker, a knock based access control system for your homelab

github.com

Post reply on HN
Print view View original

171–175 of 175 posts

Re: Knocker, a knock based access control system for your homelab

#171

Post by xenophonf »

eitland wrote: post #76
xenophonf wrote: post #39

Earlier quoted context omitted.

> 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?

No. You have just missed the two last steps. Here is the full explanation, and it is the same as it has always been on HN: 1. Make prototype 2. Magic happens here 3. Make lots of $$$ Great for prototyping only makes it easier to get to step 2, but done correctly, it certainly does that. As proven by the nice app I have running on my laptop, but probably won't make any money from.

I haven't been able to get useful prototypes out of LLMs, for that matter.

Re: Knocker, a knock based access control system for your homelab

#172

Post by akerl_ »

hrimfaxi wrote: post #169
akerl_ wrote: post #145

Earlier quoted context omitted.

That’s almost always going to be a setting in your IDP, not based on log capture/retention. The IDP will have some settings for max fails before lockout, and apply it by counting.

A centralized IDP that touches every service is not mandated by NIST though. So while you are right that an IDP can handle that, the organization may not have the IDP integrated with a given system and you will still need compensating controls or mitigations. Outright incredulity over logging failed access attempts is surprising.

Did I express outright incredulity about logging failed attempts?

If you’re a company trying to meet a compliance regime and you don’t already have a central IDP, that’s step zero. None of the NIST requirements say “you must have an IDP”, but a massive portion of them are trivial with an IDP and a massive pain in the ass (both to implement and evidence to auditors) without one.

Re: Knocker, a knock based access control system for your homelab

#173

Post by nextlevelwizard »

Eisenstein wrote: post #32
nextlevelwizard wrote: post #28

Earlier 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…

LLMs and Humans fundamentally write different kind of code.

As humans we segment functionality and by nature avoid extra work as much as possible. Meaning reading someone else's code even if they are less competent makes sense and you can see the intention.

With LLM code everything is mixed together with no rime or reason and unless separately specified old useless functionality won't be cleaned out just because it is no longer used.

Also just the fact that people who use LLMs to vibe code bigger things usually aren't capable of reviewing what is going on in the first place, but if you are dangerous enough yourself to write a bigger piece of software you probably do know something about the problem on a deeper level and can test it.

I don't really see shaming. If you vibe code something and you are proud of it good for you, but LLMs currently are not capable of creating good software.

Re: Knocker, a knock based access control system for your homelab

#174

Post by sneak »

lucideer wrote: post #110
sneak wrote: post #107

Earlier quoted context omitted.

Not really. Most things people run in homelabs have tons of cloud dependencies. Try running Home Assistant offline, for example.

I run home assistant offline. I've never encountered any issues, except for the little weather widget that comes enabled by default not working. I know there's plenty of HA integrations that require some cloud service but the core application is very offline-friendly...

You can’t even install it offline. It has to contact Docker Hub to pull all its images.

Re: Knocker, a knock based access control system for your homelab

#175

Post by eitland »

xenophonf wrote: post #171
eitland wrote: post #76

Earlier quoted context omitted.

No. You have just missed the two last steps. Here is the full explanation, and it is the same as it has always been on HN: 1. Make prototype 2. Magic happens here 3. Make lots of $$$ Great for prototyping only makes it easier to get to step 2, but done correctly, it certainly does that. As proven by the nice app I have running on my laptop, but probably won't make any money from.

I haven't been able to get useful prototypes out of LLMs, for that matter.

I have, with minimal time invested (half an hour here and there while commuting or waiting for something).

And it was very useful because

- I realized it wouldn't sell well anyway,

- but it did scratch my itch.

Post reply on HN