Get best of the week

A thousand and one reasons not to use (fix: Russian) search on the Internet to solve at least some problems

The first action. habr.com/en/post/499146
It turns out that forward probing 3389 can be improved and secured. And 5060 to the outside is also possible, but if with portknocking, then for sure. There is even a file2ban for Windows, and the use of this design without passing through RAW, some commentators consider the height of unprofessionalism. I cannot but notice that according to the conditions of the task, a person already has a microtic, but for some reason the built-in security tools do not seem worthy of attention to him.

The second action. habr.com/ru/post/499152
The author writes that the standard strcat functions accept, they say, two pointers. Let us rather put them together into one, using the Python wrapper.
We import crt, we saw two Python lines and boldly pass pointers to them in strkat. Allocate memory? Why, we have a python, he will do everything himself.
Well, that is one more time - an article with a positive rating about something there in C was written by a person who is not aware of how strcat works.


The third action . habr.com/ru/company/ruvds/blog/498924
The author categorically states - Ike2 is better than other vpn, because login, password and client built into Windows. Some commentators note that far from any Windows it is built-in, and some even pay attention that login and password are not an additional security factor, because for sure it is simply forwarded domain loans through the local radius. Commentators actively argue that PPTP is unsafe (but they don’t even try to break the terribly-terribly unsafe RC4). In the discussion, IKEv1 (in a variation of l2tp-ipsec) is actively doused for the extreme ease of configuration, but at the same time, the author of the post on the server responsible for corporate security suggests verbatim
wget https://raw.githubusercontent.com/jawj/IKEv2-setup/master/setup.sh
chmod u+x setup.sh
./setup.sh

Needless to say, the author would have had enough of the trivial TLS. But articles from this, of course, would not come out.

Epilogue. www.youtube.com/watch?v=jb3NBZ8axT0
Not everyone launches rockets into space, or they engage in diverse bioengineering. Someone has a fleet of 10 cars, and someone has 10 thousand. Someone ci / cd, and someone wget / chmod. People have different business, different needs, different opportunities, budgets and staffing. But cancer of content for the sake of content has already hit YouTube and is now approaching your infrastructure. Another one-liner breaks NPM, and your cluster or localhost will hit another supposedly reliable docker pull or chmod u + x setup.sh. But these will be your personal problems, and the authors of proven and polished manuals will continue to produce 30 tons of content per quarter.

And while someone after a successful docker image prune is looking for another manual for recovering data from XFS - the content forge continues to forge pans and rakes from the fittings.

More articles:


All Articles