Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad words filter (and bad commands) #211

Open
cquencer opened this issue Apr 7, 2012 · 0 comments
Open

Bad words filter (and bad commands) #211

cquencer opened this issue Apr 7, 2012 · 0 comments

Comments

@cquencer
Copy link
Contributor

cquencer commented Apr 7, 2012

Reported by Svein W.

When setting up a forum, we need to think about the fact that practically everyone with an internet connection can reach it, and cultures varies greatly.

Also, discussion can become a bit more heated on the internet than in real life. So a bad words filter can be a good thing to have.

But there are also other uses for it.

In support forums, you will get questions from people that do not know much about computers, and some of them trust blindly on the answers they get in forums. Sadly, there are people that give dangerous suggestions on purpose - a different kind of malware! Something like this is not unthinkable:

  • Open a console window by clicking on the Start-menu, choose "Run...", type cmd and press enter
  • Type format c:
  • Press enter

Luckily, most people will catch this particular one, but in Linux, you have a lot more situations that could be potentially dangerous. It would be nice to add these to a filter that would either replace them with ***** or replace with the same text in red and add *** DANGEROUS COMMAND *** after it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant