Shouldn’t that be
Microsoft Windows is now 100% secure after Total Recall of all copie
?
Shouldn’t that be
Microsoft Windows is now 100% secure after Total Recall of all copie
?
Mostly it is dealing with the fact that these tools tend to be language/build tool specific and most of them implement the spec badly. Then there is the part where you actually need to have something like Dependency Track setup which compares the versions in the SBOMs with the versions in security reports (such as CVEs, GHSAs,…) but most of those don’t really take into account distro level patches. I suspect the latter will be the largest part of the work for something distro-like such as FreeBSD.
I assume you meant PII?
From what I recall Kerberos didn’t work all that well in environments with NAT so it is unlikely to replace modern single sign on systems like OpenID Connect.
Please stop recommending people disable IPv6 as if that is an optional feature. This only further delays the much needed transition away from IPv4 where we ran out of addresses years ago at this point.
Restarting a system gets it into a known state making debugging easier.
And what are you going to debug when the problem does not occur and you do not know how to reproduce it? There is a lot of information you can only gather while the problem occurs. And yes, this is from the software developer and sysadmin perspective, not from the layman perspective. I would rather spend a little bit more time on the problem now instead of having it occur again and again without getting any closer to an actual solution.
It is also a good idea for computing devices in general since not restarting means effectively restarting and finding out that the restart didn’t work properly or that you do not have all the information needed to log back in at the worst possible time, one you didn’t choose yourself. And if you do it often enough the number of updates/changes that could be the cause is significantly lower than if you keep things running for a long time before a restart.
It solves virtually none of them, it is pretty good at destroying all the evidence needed to actually fix the problem for good though.
Those are not VPS specs, that is more the kind where you would get a dedicated hardware server at a hoster. Hosting your own becomes much more viable the larger your operation becomes.
IPv6 binds on wildcard addresses include binding to the IPv4 addresses.
What does ss -tlnp
return? Does the process listen on any ports?
That should only affect ports below 1024.
I made it to about episode 5 with Discovery (the one with the security officer getting mauled because she walked into that cage with the wild animal unarmed) by actively giving it more chances than it deserved, not sure how you managed to watch a whole two seasons of it.
Your two bind addresses might be in conflict with each other since [::]:5234
includes binding to the first one.
Which is why I said “on price”. Obviously that is only one of the factors but don’t kid yourself into thinking that your local server will ever be cheaper. It might have many other advantages but price just won’t be one of them.
Electricity isn’t free and nor is your time, you are never going to beat commercial VPS hosters on price.
Or, you know, not that crazy after all if germ can survive that process.
Python packaging and stability is a total mess. It has gotten to the point where I just look for alternative tools when I find out something new I found is written in Python.
Even humans couldn’t do that. How would AI know that that API documentation for the standard library I am looking at is something I am looking at because I need it for code in a specific project. That information just isn’t there unless you can also read my mind at the time.
As long as the success rate seems to be that low I am not sure I would consider it wide-spread. A few thousand servers could literally just be a few dozens admin organizations each running a couple of hundred servers badly.