Live data from Hacker News

Knocker, a knock based access control system for your homelab

github.com

141–150 of 175 posts

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

#141
post #125

Earlier quoted context omitted.

Don't compliance regimes like NIST 800-53 require logging access attempts, whether successful or not, and especially for privileged users?

> To balance monitoring and auditing requirements with other system needs, event logging requires identifying the subset of event types that are logged at a given point in time. For example, organizations may determine that systems need the capability to log every file access successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performan…

I was thinking of:

> The need to limit unsuccessful logon attempts and take subsequent action when the maximum number of attempts is exceeded applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by systems are usually temporary and automatically release after a predetermined, organization-defined time period.

https://csf.tools/reference/nist-sp-800-53/r5/ac/ac-7/

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

#142

Earlier quoted context omitted.

Yes, and those two true things are: - You should be using WireGuard. - “Port knocking” is pointless theater.

CVE-2024-26950 is also true, and while I respect your opinion... a VPN has a lot of additional links in the chain trivially broken by competent hostiles or incompetent client installations. IPSec is simply a luxury unavailable on some LANs =3

I don't understand what you think CVE-2024-26950 has to do with this thread. Do you understand what that vulnerability actually is, or did you just go search "WireGuard CVE" to find ammunition?

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

#143

Earlier quoted context omitted.

"We had a secure VPN option set up, but then we had to replace our Ivanti VPN solution so we switched to Fortigate. Then there were some concerns so we jumped to Sonicwall. After that debacle we finally got the budget to go with Cisco and I'm sure everything will be fine now!"

These are what I call, corporate solutions. They're used to make CEOs feel good while deflecting blame, not to actually do the job. See also how nobody gets blamed if AWS goes down, but everyone who used a different host with higher uptime did get blamed when that went down. Open source tools are good at actually doing the job, as long as it's a programmer type of job. We've known how to do unbreakable encryption for…

Cisco spent years marketing every solution as a router or appliance box.

A lot of VPN installations are simply done wrong, and it only takes 1 badly configured client or cloud side-channel to make it pointless. IPSec is not supported on a lot of LANs, and 5k users would prove rather expensive to administer.

Also, GnuPG Kyber will not be supported by VPN software anytime soon, but it would be super cool if it happens. =3

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

#144

Earlier quoted context omitted.

CVE-2024-26950 is also true, and while I respect your opinion... a VPN has a lot of additional links in the chain trivially broken by competent hostiles or incompetent client installations. IPSec is simply a luxury unavailable on some LANs =3

I don't understand what you think CVE-2024-26950 has to do with this thread. Do you understand what that vulnerability actually is, or did you just go search "WireGuard CVE" to find ammunition?

Firewall administrative network port traffic priority is important for systems under abnormal stress.

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

#145
post #125

Earlier quoted context omitted.

> To balance monitoring and auditing requirements with other system needs, event logging requires identifying the subset of event types that are logged at a given point in time. For example, organizations may determine that systems need the capability to log every file access successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performan…

I was thinking of: > The need to limit unsuccessful logon attempts and take subsequent action when the maximum number of attempts is exceeded applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by systems are usually temporary and automatically release after a predetermined, organization-defined time period. https:/…

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.

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

#146

Earlier quoted context omitted.

These are what I call, corporate solutions. They're used to make CEOs feel good while deflecting blame, not to actually do the job. See also how nobody gets blamed if AWS goes down, but everyone who used a different host with higher uptime did get blamed when that went down. Open source tools are good at actually doing the job, as long as it's a programmer type of job. We've known how to do unbreakable encryption for…

PGP has very much had breaks, both in its authenticator and a full-on confidentiality break for the mail plugins, both traceable to the structure of the system itself, and that's before we get into the fundamental DOS flaw that killed the keyservers, which themselves are an antifeature. I don't think you can find a practicing cryptography engineer to stick up for PGP. I don't like or trust OpenVPN. I'd sooner expose…

The key concept is accountability, and if only 7 people have access to a host instance... the damage done by malicious or incompetent actors is kept small.

The biggest weakness in VPN is client-side cross-network leaks.

IPSec is simply a luxury if the LAN supports it, but also an administrative nightmare for >5k users. =3

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

#147

Earlier quoted context omitted.

I don't understand what you think CVE-2024-26950 has to do with this thread. Do you understand what that vulnerability actually is, or did you just go search "WireGuard CVE" to find ammunition?

Firewall administrative network port traffic priority is important for systems under abnormal stress.

I don't know what this even means. Do you understand the vulnerability you cited? Can you explain it here?

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

#148
If you need to manage risk for a legacy service that has a requirement to be internet exposed, I suggest checking out https://knocknoc.io/ for a self-hosted and/or cloud based solution that was not built with vibe coding, but actual customer security use cases. They provide 2FA and/or single sign-on to allow just in time access to internet exposed applications which remain hidden from unauthenticated/approved users.

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

#149

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…

there is a non-zero chance that the human programmer has an interest in producing correct, secure code. there is zero chance than an LLM has the same interest. maybe those two are closer together in some cases, but not in many others.

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

#150

Earlier quoted context omitted.

Firewall administrative network port traffic priority is important for systems under abnormal stress.

I don't know what this even means. Do you understand the vulnerability you cited? Can you explain it here?

The relatively benign legacy kernel level pointer-bug CVE chosen is hardly the worst thing from WireGuard or strongSwan over the years. However, it makes the point a priority reliable network side-channel administrative login is more robust under some use-cases.

Adding layers of complexity rarely improves security, and doesn't usually address the underlying issue of accountability. And I often ponder if a bastion host is even still meaningful in modern clouds. =3

Post reply on HN