I'm thinking about making a "secure your Fedora" script

Originally Posted by droidhacker

Don't waste your time writing scripts. Unless the script is validated and included in Fedora itself, it will be useless. The NUMBER ONE WORST possible thing that ANYONE can do, is running some script they downloaded from the internet as root. Even if you make it with the best of intentions, it would be SO ABSOLUTELY STUPID for anyone to actually run it without understanding EVERY SINGLE LINE OF IT, that it should be CRIMINAL.

If somebody is going to go to the trouble of learning every single line of your code, they would be far better off just securing everything themselves.

FOCUS ON DOCUMENTATION AND RECOMMENDATIONS. Give people suggestions about what they can do to secure their systems. Don't give them code to run, since their acceptance of that code would prove that they are complete retards.

I.e., how can they possibly know that you are trustworthy? Maybe you're a hacker and built a rootkit and are passing it off for the complete opposite. I'm not saying that you are, but how do "they" know?

Its just silly CAT, ECHO, SED, GEDIT commands added in a line in a very silly way (since I thought this would have no need for codereuse, or advanced logic that can mess things up)..

But I get the point. I was doing some Improvments to this but I guess I just keep it as my own then and have it to make deloyment faster (after messing up and stuff like that).

[jpollard]

The documentation is actually more important than the script itself. The documentation can show something that is nearly always overlooked - WHY did you mess up?

Such warnings can also be clues to where improvements are needed.

Originally Posted by jpollard

The documentation is actually more important than the script itself. The documentation can show something that is nearly always overlooked - WHY did you mess up?

Such warnings can also be clues to where improvements are needed.

I know documentation is important (to any organisation) but I wasn't planning on targeting the top of the top professionals.

I just wanted to bring a easy to use tool for home users mostly to make some quick basic changes, but nm I keep the silly thing to myself so no one has to worry about my bad documenting skills.

[jpollard]

Originally Posted by birdwatcher

I know documentation is important (to any organisation) but I wasn't planning on targeting the top of the top professionals.

That is exactly WHY the documentation on mistakes are so necessary. Educating the inexperienced is the only way they can beome "top professionals".

I just wanted to bring a easy to use tool for home users mostly to make some quick basic changes, but nm I keep the silly thing to myself so no one has to worry about my bad documenting skills.

You can always get help with documenting skills, but it has to be written before it can be critiqued and suggestions returned.