

and it’s much easier to DRM


and it’s much easier to DRM


exactly
default: on
user: explicitly turns off
random “update”: defaults back on
Now wait 1 year


i’m not an expert, but here’s my take.
personally i question when such movements take power that we should interpret it as consent by the public majority.
part of the reason the public apparently bestow power to the machinery of government is because the machinery is supposed to protect them from this very thing happening.
the fact that it is happening, means such a rise in fact did not occur within the correct functioning of that machine.
therefore we should probably question whether we should interpret it as consent by the majority.
and if its not consent by the majority, then in some ways the picture is both bleaker and brighter.
brighter, because you’re not surrounded by quite so many evil fucks as they wanted you to believe
bleaker, well, probably don’t need to explain that bit


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.


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.
I fucking hate this timeline.
my first thought as well…how did we get to the point that this is a valid topic?
(not a comment about you OP, just the state of the world)


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?
i feel like this is a good place to mention the ship shipping ships


can you pls explain what you mean in more depth?
your original post is sufficiently vague that tbh i don’t blame people for assuming you were just bootlicking? [which probably says more about the state of the world than you as an individual, but honestly it’s not clear what you’re trying to say?]
we all know a random citizen/local business presenting an identical calibre of evidence of repeated crimes would be extremely unlikely to routinely receive this degree of resource allocation.
so if it’s an idealised aspirational universal “order” you’re talking about then obviously noone’s buying it - and i don’t think you are either. so what do you mean?


searching for ‘phpbb <topic name>’ can usually bring up a few struggling to dead forums for niche communities which are being sadly absorbed into bigtech monoliths


a ridiculous number of arguments are because people misunderstand what they’re actually arguing over.
it’s crazy how helpful it can be to stop, and check what they meant before responding to it.
apart from the obvious benefits, it can also make a nice pause for everyone to calm just a little, and also shows you’re making an effort to understand which can be helpful too.
tar pits target the scrapers.
were you talking also about poisoning the training data?
two distinct (but imo highly worthwhile) things
tar pits are a bit like turning the tap off (or to a useless trickle). fortunately it’s well understood how to do it efficiently and it’s difficult to counter.
poisoning is a whole other thing. i’d imagine if nothing comes out of the tap the poison is unlikely to prove effective. there could perhaps be some clever ways to combine poisoning with tarpits in series, but in general they’d be deployed separately or at least in parallel.
bear in mind to meaningfully deploy a tar pit against scrapers you usually need some permissions on the server, it may not help too much for this exact problem in the article (except for some short term fuckery perhaps). poisoning this problem otoh is probably important
deleted by creator
anywhere shit gets cliquey it gets toxic real fast - and that goes for ANY and ALL organisations.
safe-space concepts often inherently deals with an “us/them” dichotomy, which is unfortunately fertile ground for things getting cliquey.
it’s not that one must lead to the other, its just that the foundation is there so the risk is higher if it’s not managed properly.
this is why safe-spaces need to be protected from within and without. regardless of whether you’re in the clique or out of it, it hurts everyone in the end.
where/how/what are you eating copper which permits you to taste it?
without further explanations of OP’s intent i’m inclined to think this is perhaps the best approach