Debian User Forums

Still going at it I see.
Sometimes there are reasons why they post, "Do not feed the animals" at zoos.

If asking you to present data that backs up some of the claims you have made is harassing you, that says quite a bit about you in general.

You continue to dance around presenting actual data backing your claims. Simply asking someone to simply trust you and do your own research, is NOT backing your claims in any way.

You seem to be making a lot of claims about things that seem to fly in the face of what is normal and acceptable yet you never back your claims up with any examples, benchmarks, or process. Nothing. How can anyone take you seriously? It's always easy to say things like, it failed me before, or, well...

Post your benchmarks on how it compares to a standard kernel and others.

wizard10000 wrote: ↑2024-04-21 17:59

Linuxgaming1824 wrote: ↑2024-04-21 17:49I think I've seen bad behaviour with the ampersands before where commands run into each other...

I find that hard to believe considering the purpose of the double ampersand. The double ampersand will not execute a subsequent command unless the previous command exited successfully.

+1

It's not really a tutorial, it's really just my personal journal going over every aspect of my base installation that I decided to share here as a "guide" Forums, in general - are not to be treated as a personal journal. A link stating what you did can be viewed at such and such link (bar...

This may give you a hint.
Additionally, if the dependencies (gnucobol3) were installed, then it appears the binary is located /usr/bin/cobc and/or /usr/bin/cobcrun

If all else fails, use OWA. Bypass using the actual application.

Can't you just use .link files?

Linuxgaming1824 wrote: ↑2024-04-20 17:14 I personally develop unique or new security mitigations, so it's not off-topic for me, but it is clearly off-topic to others that frequent the forums currently.

Why not post what you have developed

Ignore them...

If you don't have any unique ideas, or ideas pertinent to the subject at hand you don't have to add anything... I am specifically referring to unique ideas for securing a system generally, but as well as a system that lacks the default kernel hardening and has a high performance kernel as well, tha...

If we're talking real world, the ordinary recommendations are plenty. Loading up the list is counterproductive. Stick to what ordinary people can understand and remember. Use a password manager. Failing that, put passwords in a password-protected text file. Don't use the same password in more than ...

In a world that is governed by humans, made for humans and with humans being inherently flawed beings, the things we make (including AI) will always be flawed. You will never come up with a "system" that is perfect. Oh, it may work for a while, but eventually it will succumb to the flaws t...

You can't dictate what a remote system should do (if its not owned by you) All you can do is protect the perimeter and what's inside. If the remotes belong to you or the company, there are things you must do that include much of what was discussed using either Mac or Windows variations of the apps a...

That hypothetical story I threw together in a minute 30 seconds, is a constant daily affair actually, and doesn't have a simple solution such as "employee training" In part, the security incident didn't actually occur on the local system, apart from the overwhelming misinformation they ar...

Ah - in your example, it comes down to employee training. You can develop a plan yourself based on your own real-world experiences OR, you can search the interwebs for security training and scrape what you feel is important and build your own OR employ an entity to actually have online tutorials. Ma...

Yea no... I'm talking about developing real security solutions, not going over all the trivial nonsense that fails to achieve anything in the real world. Cmon guys, unique ideas do not involve sudo apt get or the debian wiki. Part of any practical security mitigation plan ought to include (but not ...

I don't recall it being mentioned, there are several packages you should install as part of the base. debsecan - Debian Security Analyzer debsums - tool for verification of installed package files against MD5 checksums checksecurity - Debian Security Analyzer Others to consider: chkrootkit - rootkit...