

if you can’t work out what knocking might have to do with whitelisting then i’m not sure what you hoped to contribute towards reducing misconceptions in the conversation


if you can’t work out what knocking might have to do with whitelisting then i’m not sure what you hoped to contribute towards reducing misconceptions in the conversation


would you classify out of band whitelisting by IP (or other session characteristic[s]) as having no security merit whatsoever?
would you classify it as purely a decision regarding network congestion & optimisation?
you’re ofc free to define these things however you wish, but in a form which is helpful to OP’s question i’m not sure i follow you.
it’s funny, i visited there once with a friend, we also discussed fairies in that area. i wonder what is the cause of such a seeming coincidence.


to reduce attack-surface, if there’s no reason for the port to be open, don’t open it.


while the most bare bones knocking implementation may be classed as obscurity, there’s certainly plenty of implementations which i wouldn’t class as obscurity.


People iterate through all the IPv4 addresses since there are only 4,294,967,296 possible addresses. There are 340,282,366,920,938,463,463,374,607,431,768,211,456 possible IPv6 addresses
i love your thinking!!
do you have a backup in case you accidentally find yourself locked out from an ipv4-only network?
no, that illustration apparently came 12 years later
anyway as an 1800s fairy tale for children, imo i think it’s fine to view it through the lens of whichever culture you want. the trouble imo begins when trying to ascribe something to the story which it certainly did not contain - even that is probably basically harmless if you’re just confused or something, but it certainly becomes a problem when it’s used to justify unfairly shitting on someone else for a slightly different yet completely harmless alternative depiction.
it’s even worse than that cos the original text never said ariel’s human version race, they just assumed it lol.
and before anyone says yes but its written by a dane, my response is yes but it’s a fairy tale, anything is possible. why assume and then get angry based on your assumption?
well yeah most of its operating software was derived from opensource projects, but capitalists exploited those opensource project without giving much if anything back, so…


is the machine the problem? that seems more like a philosophical or semantic debate.
the machine is not fit for the advertised purpose.
to some people that means the machine has a fault.
to others that means the human salesperson is irresponsibly talking bs about their unfinished product
imo an earnest reading of the logs has to acknowledge at least potential evidence of openai’s monetisation loop at play in a very murky situation.


i’m a piece of shit
and obviously lying about how well it worked out for me, or i wouldn’t be here forcing a smile for the camera and spruiking my latest bs


agreed, not a single chance i’m pre-ordering


sound logic right here.
that said the gameplay demos today weren’t terrible


thanks i got that far ;)
but what is it about eg.
etc that makes you think its bad news?
the previous games i’m 100% with you, 2042 was beyond embarrassing. the publisher, nothing need be said lol. the dev cycle i’m going to assume is suspciously fast?
yep, there’s this weird trend to demonise cute animals.
you can’t even fucking mention koalas on reddit without some arsehole telling us they all have chlamydia every 53 seconds.
according to them, all dolphins suck, all ducks are shit, and all cute little marsupials who never harmed a fly are secretly evil incarnate.
what if all humans were judged by the actions of some humans? that’s a frying pan i’d rather not be in…


another former fan here, could you pls expand a bit on what you’re feeling with these points and what it means? i don’t know enough about each of them to realise what you meant?
“Meet me in the middle, says the unjust man.
You take a step towards him, he takes a step back.
Meet me in the middle, says the unjust man.”
ok fair enough, sorry i may have misinterpreted what you meant.
it sounds like your argument is that if the attacker doesn’t know the service is running then the assertion that this reduces the risk profile is classified as an obscurity control - this argument is correct under these conditions.
however, certain knocking configurations are not obscurity, because their purpose & value does not depend on the hope that the attacker is unaware of the service’s existence but rather to reduce the attacker’s window of access to the service with a type of out of band whitelisting. by limiting the attacker’s access to the service you are reducing the attack surface.
you can imagine it like a stack call trace, the deeper into the trace you go, every single instruction represents the attack surface getting larger and larger. the earlier in the trace you limit access to the attacker, you are by definition reducing the attack surface.
in case i’ve misinterpreted what you meant. susceptibility to a replay attack does not mean something isn’t a security measure. it means it’s a security measure with a vulnerability. ofc replay attacks in knocking is a well known problem addressed long ago.
perhaps the other source of miscommunication is for us to remember that security is about layers, because no single layer is ever going to be perfect.